May 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 972668] New: XServer and raspberrypi-userland don't work together on openSUSE-Tumbleweed-ARM
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=972668 Bug ID: 972668 Summary: XServer and raspberrypi-userland don't work together on openSUSE-Tumbleweed-ARM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: notavailable(a)posteo.de QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 670514 --> http://bugzilla.suse.com/attachment.cgi?id=670514&action=edit Xorg.0.log When you install raspberrypi-userland on TW ARM images with a desktop environment, XServer doesn't start anymore. I could not use any of the latest images (2016.03.24) with E20, LXQt and Xfce. These are the errors I get with Xfce. Instead Xorg.0.log simply shows the following message at the end: "Server terminated successfully (0). Closing log file." Starting programs from the command-line gives the output: "nohostname:~ # yast2 /usr/lib/YaST2/bin/y2controlcenter: error while loading shared libraries: libGLESv2.so.2: cannot open shared object file: No such file or directory" "nohostname:~ # firefox XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so: libEGL.so.1: cannot open shared object file: No such file or directory Couldn't load XPCOM." During the installation process of raspberrypi-userland there are two messages: "/sbin/ldconfig: /usr/lib/libEGL.so is not a symbolic link" "/sbin/ldconfig: /usr/lib/libGLESv2.so is not a symbolic link" When you reinstall raspberrypi-userland with the -f option, you get this output: nohostname:~ # yast2 Unable to find an X11 visual which matches EGL config 20 Could not initialize OpenGL for RasterGLSurface, reverting to RasterSurface. /sbin/yast2: line 440: 1382 Speicherzugriffsfehler (core dumped) $y2ccbin $Y2UI_ARGS "$@" nohostname:~ # firefox XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so: /usr/lib/libEGL.so.1: undefined symbol: glDiscardFramebufferEXT Couldn't load XPCOM. The second installation creates two symlinks in /usr/lib/: libEGL.so.1 and libGLESv2.so.2 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 974800] New: unable to run go-5 on armv7
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=974800 Bug ID: 974800 Summary: unable to run go-5 on armv7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- running go-5 on tumbleweed/armv7hl gives an endless hang, e.g. as seen on "go-5 version". gdb gives: Program received signal SIGINT, Interrupt. 0xb639b750 in __pthread_mutex_unlock_usercnt ( mutex=0xb6fff4dc <_rtld_local+1244>, decr=1) at pthread_mutex_unlock.c:73 73 pthread_mutex_unlock.c: No such file or directory. (gdb) p i No symbol "i" in current context. (gdb) bt #0 0xb639b750 in __pthread_mutex_unlock_usercnt ( mutex=0xb6fff4dc <_rtld_local+1244>, decr=1) at pthread_mutex_unlock.c:73 #1 0xb64cb4ec in __GI___dl_iterate_phdr ( callback=0xb64cb4ec <__GI___dl_iterate_phdr+436>, data=0x10415c54, data@entry=0x10415c4c) at dl-iteratephdr.c:83 #2 0xb64cc3b0 in __gnu_Unwind_Find_exidx (pc=pc@entry=3057612094, pcount=0x10415c74, pcount@entry=0x10415c6c) at ../sysdeps/arm/find_exidx.c:74 #3 0xb637c4f0 in get_eit_entry (ucbp=ucbp@entry=0x10415c88, return_address=3057612094) at ../../../libgcc/unwind-arm-common.inc:210 #4 0xb637cc50 in __gnu_Unwind_Backtrace (trace=0xb6cef380 <unwind>, trace_argument=0x10415f28, entry_vrs=<optimized out>) at ../../../libgcc/unwind-arm-common.inc:567 #5 0xb637d700 in _Unwind_Backtrace () at ../../../libgcc/config/arm/libunwind.S:360 #6 0xb6cef440 in backtrace_full (state=<optimized out>, skip=skip@entry=0, callback=<optimized out>, error_callback=<optimized out>, data=0x10415f54, data@entry=0x10415f4c) at ../../../libbacktrace/backtrace.c:106 #7 0xb69d92d4 in runtime_callers (skip=skip@entry=1, locbuf=locbuf@entry=0x10418074, m=m@entry=32, keep_thunks=keep_thunks@entry=0 '\000') at ../../../libgo/runtime/go-callers.c:168 #8 0xb69e8adc in mcommoninit (mp=mp@entry=0x10418000) ---Type <return> to continue, or q <return> to quit---c at ../../../libgo/runtime/proc.c:808 #9 0xb69eb3d4 in runtime_allocm (p=p@entry=0x0, stacksize=stacksize@entry=-1, ret_g0_stack=ret_g0_stack@entry=0x0, ret_g0_stacksize=ret_g0_stacksize@entry=0x0) at ../../../libgo/runtime/proc.c:1146 #10 0xb69eb47c in newm (fn=0xb69ede60 <sysmon>, p=p@entry=0x0) at ../../../libgo/runtime/proc.c:1433 #11 0xb69ed3ec in runtime_main (dummy=<optimized out>) at ../../../libgo/runtime/proc.c:575 #12 0xb69eaf60 in kickoff () at ../../../libgo/runtime/proc.c:235 #13 0xb63f7540 in setcontext () at ../sysdeps/unix/sysv/linux/arm/setcontext.S:82 Backtrace stopped: previous frame identical to this frame (corrupt stack?) -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[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 980866] New: update-scripts leave ton of leftovers
by bugzilla_noreply＠novell.com 15 May '20

15 May '20

http://bugzilla.suse.com/show_bug.cgi?id=980866 Bug ID: 980866 Summary: update-scripts leave ton of leftovers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While we now have leftover mechanism to run scripts on posttrans of packages just once instead of for all invocations we keep the scripts that were not executed in /var/adm/update-scripts/ Most visible it is on update scripts for font scriptlets. One of the leftovers: dreamcrawler:/var/adm/update-scripts # cat ghostscript-fonts-9.06-7.4-reconfigure-fonts if [ -e /var/run/fontpackages/reconfigure-fonts ]; then if [ -x /usr/sbin/fonts-config ]; then /usr/sbin/fonts-config --quiet fi rm /var/run/fontpackages/reconfigure-fonts fi rm /var/adm/update-scripts/ghostscript-fonts-9.06-7.4-reconfigure-fonts I suppose proper solution would be to run just one of the scripts, but then delete them all and not keep any? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[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 976102] New: JavaFX/OpenJFX is not yet packaged
by bugzilla_noreply＠novell.com 16 Apr '20

16 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=976102 Bug ID: 976102 Summary: JavaFX/OpenJFX is not yet packaged Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: matthias(a)mailaender.name QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I was trying to compile OpenChrom according to https://wiki.openchrom.net/index.php/Development using the Eclipse IDE. A major pain was the JavaFX dependency, which just doesn't exist in openSUSE at all. Purging SUSE's OpenJDK and installing Oracle Java was ultimately the only solution. For Fedora/Mageia and Debian/Ubuntu you can simply install openjfx packages from the repositories. I tried packaging it myself: https://build.opensuse.org/package/show/home:Mailaender:branches:Java:packa… but pretty much failed early as openSUSE is missing the gradle and the whole xmvn infrastructure so dependencies can't get packaged and resolved. I would like to fill this gap for SUSE to scratch my own itch, but I need some help here. -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[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

[Bug 959025] New: mate-tweak completely broken
by bugzilla_noreply＠novell.com 05 Apr '20

05 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=959025 Bug ID: 959025 Summary: mate-tweak completely broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- "/usr/lib/python2.7/site-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You have imported the Gtk 2.0 module. Because Gtk 2.0 was not designed for use with introspection some of the interfaces and API will fail. As such this is not supported by the pygobject development team and we encourage you to port your app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 2.0" Possibly related reports: https://forum.antergos.com/topic/1898/mintmenu-is-broken-again/6 https://github.com/linuxmint/mintmenu/issues/130 https://bugs.launchpad.net/linuxmint/+bug/1261862 -- You are receiving this mail because: You are on the CC list for the bug.

1 8