February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[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 974835] New: bluetooth conflict between 2 users
by bugzilla_noreply＠novell.com 05 Jun '20

05 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=974835 Bug ID: 974835 Summary: bluetooth conflict between 2 users Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- i open a kde session for user1 i enable bluetooth with bluedevil. i need this permanently for user1. then i open a kde session for users2 i disable bluetooth with bluedevil. i don't need this for user2. i close the session for user2 then i return to user1 kde session. i tried to connect my bluetooth headset to see a video. this fails. i search in the systray. no more bluetooth icon. bluetooth is disabled ! -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[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 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 1000507] New: cannot boot encrypted disk installed on one PC on another
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1000507 Bug ID: 1000507 Summary: cannot boot encrypted disk installed on one PC on another Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 693700 --> http://bugzilla.suse.com/attachment.cgi?id=693700&action=edit initrd log I installed a system with disk encryption in one PC. Tried to move it to another PC and it would not boot. It asks for the passphrase, waits a long time, and then prints Failed to start Cryptography Setup for cr_ata_<disk manufacturer and model>_part2. I suspect it may be trying to use a crypto accelerator that does not exist. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[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 1011815] New: [Build 20161121] Console messages writes over YaST configuration page in terminal
by bugzilla_noreply＠novell.com 03 Jun '20

03 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1011815 Bug ID: 1011815 Summary: [Build 20161121] Console messages writes over YaST configuration page in terminal Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: http://openqa.opensuse.org/tests/309124/modules/yast2_ samba/steps/37 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: zluo(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ui_gnome@64bit fails in [yast2_samba](http://openqa.opensuse.org/tests/309124/modules/yast2_samba/st… dmesg messages writes over YaST configuration screen and breaks needle match. ## Reproducible Fails since (at least) Build [20161121](http://openqa.opensuse.org/tests/308999) ## Expected result The message should not show up at all to screen. Last good: [20161120](http://openqa.opensuse.org/tests/308402) (or more recent) ## Further details Always latest result in this scenario: [latest](http://openqa.opensuse.org/tests/latest?arch=x86_64&version=Tumblew… -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[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