July 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 976955] New: devel:libraries:c_c /libunwind: Build fail for armv7
by bugzilla_noreply＠novell.com 18 May '18

18 May '18

http://bugzilla.opensuse.org/show_bug.cgi?id=976955 Bug ID: 976955 Summary: devel:libraries:c_c /libunwind: Build fail for armv7 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: tchvatal(a)suse.com Reporter: matwey.kornilov(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: crrodriguez(a)opensuse.org Found By: --- Blocker: --- Created attachment 674308 --> http://bugzilla.opensuse.org/attachment.cgi?id=674308&action=edit core for test-async-sig Hello, Currently, libunwind build is failed for openSUSE:Factory:ARM armv7 There is a segfaults like the following: [ 1141s] PASS: Gtest-trace [ 1141s] PASS: Ltest-trace [ 1142s] ../config/test-driver: line 95: 13934 Segmentation fault (core dumped) "$@" > $log_file 2>&1 [ 1142s] FAIL: test-async-sig I was able to reproduce the issue and obtain coredump file. Backtrace is the following: (gdb) set solib-absolute-prefix ~/lab/libunwind-armv7/ports-armv7l (gdb) file tests/.libs/test-async-sig Reading symbols from tests/.libs/test-async-sig...done. (gdb) core-file ../../../../../../core.test-async-sig.399.100ba13edb05428490b7895fa4732d39.13934.1461495932000000 [New LWP 13934] Core was generated by `/home/abuild/rpmbuild/BUILD/libunwind-1.1/tests/.libs/test-async-sig'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xb6f977c8 in _ULarm_step () from /home/matwey/lab/libunwind-armv7/ports-armv7l/home/abuild/rpmbuild/BUILD/libunwind-1.1/src/.libs/libunwind.so.8 (gdb) bt #0 0xb6f977c8 in _ULarm_step () from /home/matwey/lab/libunwind-armv7/ports-armv7l/home/abuild/rpmbuild/BUILD/libunwind-1.1/src/.libs/libunwind.so.8 #1 0x00010e50 in do_backtrace () #2 0x00011004 in sighandler () #3 <signal handler called> #4 0xb6f968c8 in _Uarm_get_accessors () from /home/matwey/lab/libunwind-armv7/ports-armv7l/home/abuild/rpmbuild/BUILD/libunwind-1.1/src/.libs/libunwind.so.8 #5 0xb6f971d4 in _ULarm_is_signal_frame () from /home/matwey/lab/libunwind-armv7/ports-armv7l/home/abuild/rpmbuild/BUILD/libunwind-1.1/src/.libs/libunwind.so.8 #6 0xb6f97670 in _ULarm_step () from /home/matwey/lab/libunwind-armv7/ports-armv7l/home/abuild/rpmbuild/BUILD/libunwind-1.1/src/.libs/libunwind.so.8 #7 0x00010e50 in do_backtrace () #8 0x00010b20 in main () Corefile is attached here. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 971832] New: vsftpd leads to unexpected message while install
by bugzilla_noreply＠novell.com 16 May '18

16 May '18

http://bugzilla.opensuse.org/show_bug.cgi?id=971832 Bug ID: 971832 Summary: vsftpd leads to unexpected message while install Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: tchvatal(a)suse.com Reporter: lmuelle(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: No (1240/2414) Installieren: vsftpd-3.0.3-3.1.x86_64 ......................[FERTIG] Zusätzliche RPM-Ausgabe: Failed to try-restart vsftpd@.service: Unit name vsftpd@.service is not valid. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 682920] New: strange defaults in mailman
by bugzilla_noreply＠novell.com 15 May '18

15 May '18

https://bugzilla.novell.com/show_bug.cgi?id=682920 https://bugzilla.novell.com/show_bug.cgi?id=682920#c0 Summary: strange defaults in mailman Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: jmatejek(a)novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- (partly copied from http://mail.python.org/pipermail/mailman-users/2007-November/058954.html after seeing the same problem on 11.3) I called "/usr/lib/mailman/bin/newlist mailman" to create the master mailing list. Doing so resulted in the error Bad owner email address: mailman@(unused) The openSUSE Mailman package sets DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST to '(unused)' in Defaults.py, which causes this problem. Please use a default without parenthesis - according to the mail I linked above, this should display the "correct" error message about an invalid list address. Of course it would be even better to have an error message that says DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST need to be set - but that's probably something for upstream. -- 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 3

[Bug 896009] New: ghc-* and pandoc packages pulled in for no reason
by bugzilla_noreply＠novell.com 15 May '18

15 May '18

https://bugzilla.novell.com/show_bug.cgi?id=896009 https://bugzilla.novell.com/show_bug.cgi?id=896009#c0 Summary: ghc-* and pandoc packages pulled in for no reason Classification: openSUSE Product: openSUSE Factory Version: 201409* Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pat(a)indy.rr.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 zypper dup to "20140904 (Harlequin)" pulled in 60 packages of ghc-* and pandoc which had no installed dependency or recommends, ie: should not have been installed. Reproducible: Always Steps to Reproduce: 1.zypper dup 2. 3. Actual Results: installed 60 packages not required, recommended or desired Expected Results: no installation of packages w/o requirements or recommends re: Peter Trommler <peter.trommler(a)ohm-hochschule.de> see thread in opensuse-factory, New Factory snapshot 20140904 -- 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 6

[Bug 959230] New: Ralink 5370 wifi connection stalls
by bugzilla_noreply＠novell.com 15 May '18

15 May '18

http://bugzilla.opensuse.org/show_bug.cgi?id=959230 Bug ID: 959230 Summary: Ralink 5370 wifi connection stalls Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: toomas.aas(a)raad.tartu.ee QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I use an USB wifi adapter based on Ralink RT5370 chip: $ lsusb Bus 001 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter Immediately after boot, network works fine, but after some time all network communication ceases and an endless stream of messages like this keeps filling dmesg: kernel: ieee80211 phy0: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -110 kernel: ieee80211 phy0: rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x7010 with error -110 kernel: ieee80211 phy0: rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x0404 with error -110 After rebooting, I can again use the network for some time, but soon the problem reappears. Interesting thing is that this only happens if the system has 10 GB RAM. My system has 2x1GB plus 2x4GB DIMMs, and when I remove one of the 4 GB DIMMs (thus reducing the amount of memory to 6 GB) the problem does not appear. To rule out the possibility of bad DIMM I have run memtest86 for several hours without finding any problems, also the system is rock solid with 10 GB RAM when I remove the USB wireless adapter and use wired Ethernet. Version information: $ uname -a Linux susa 4.1.13-5-default #1 SMP PREEMPT Thu Nov 26 16:35:17 UTC 2015 (49475c3) x86_64 x86_64 x86_64 GNU/Linux $ /usr/sbin/modinfo rt2x00usb filename: /lib/modules/4.1.13-5-default/kernel/drivers/net/wireless/rt2x00/rt2x00usb.ko license: GPL description: rt2x00 usb library version: 2.3.0 author: http://rt2x00.serialmonkey.com srcversion: 3F336708588FABE8A5041C1 depends: usbcore,rt2x00lib,mac80211 intree: Y vermagic: 4.1.13-5-default SMP preempt mod_unload modversions signer: openSUSE Secure Boot Signkey sig_key: 03:32:FA:9C:BF:0D:88:BF:21:92:4B:0D:E8:2A:09:A5:4D:5D:EF:C8 sig_hashalgo: sha256 -- You are receiving this mail because: You are on the CC list for the bug.

1 35

[Bug 914661] New: Mgetty - no way to start mgetty service
by bugzilla_noreply＠novell.com 15 May '18

15 May '18

http://bugzilla.opensuse.org/show_bug.cgi?id=914661 Bug ID: 914661 Summary: Mgetty - no way to start mgetty service Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: wharms(a)bfs.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Fungus/8.0 (X11; U; C64 6510; de; 8bit) Build Identifier: I use mgetty as modem getty to start pppd on dial-in after the installation of mgetty there seems no way of making this service available. with SysV-init added a line into inittab but i could not find a working way with systemd (or a documentation) the yast2 modem module seems to allow dialout only. Reproducible: Always Expected Results: After installation the should be something that tell one what do to next -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 978973] New: Removing vga option breaks plymouth after installing Nvidia blob and now shows three questions
by bugzilla_noreply＠novell.com 12 May '18

12 May '18

http://bugzilla.opensuse.org/show_bug.cgi?id=978973 Bug ID: 978973 Summary: Removing vga option breaks plymouth after installing Nvidia blob and now shows three questions 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: rb03884(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Tumbleweed Removing the very useful vga selection now breaks plymouth as it now shows three question marks. We've been using it for years why the sudden change? It seems to work fine with the nouveau driver but when I install an Nvidia blob I get three question marks. Plymouth requires a ie. vga=795 so that it can show the boot splash. -- You are receiving this mail because: You are on the CC list for the bug.

1 65

[Bug 982962] New: Hard dependency on NetworkManager breaks managed environment
by bugzilla_noreply＠novell.com 09 May '18

09 May '18

http://bugzilla.opensuse.org/show_bug.cgi?id=982962 Bug ID: 982962 Summary: Hard dependency on NetworkManager breaks managed environment Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: itsbo(a)fz-juelich.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package "plasma5-session" has a hard dependency on "plasma-nm5" (Requires: plasma-nm5). "plasma-nm5" requires "NetworkManager" NetworkManager is deeply undesireable in a managed environment. Deinstalling NetworkManager results in a complete deinstall of KDE in this case due to the dependency. Please demote the dependency from "Requires" to "Recommends", so NetworkManager can be deinstalled in a managed environment. With this change NetworkManager would still be installed in a normal setup but would be removable in a managed network environment. Thank you for your help. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 975118] New: lsyncd systemd service file points to wrong location of configuration file
by bugzilla_noreply＠novell.com 26 Apr '18

26 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=975118 Bug ID: 975118 Summary: lsyncd systemd service file points to wrong location of configuration file Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: kilgus(a)fuenfsieben.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rpm package of lsyncd (lsyncd-2.1.5-5.2.x86_64) contains configuration file at this location: /etc/lsyncd/lsyncd.conf The corresponding service file /usr/lib/systemd/system/lsyncd.service in the same rpm package expects the configuration to be found elsewhere: ExecStart=/usr/bin/sh -c 'eval `/usr/bin/lsyncd -nodaemon $LSYNCD_OPTIONS /etc/lsyncd.conf`' -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 971397] New: https://software.opensuse.org/ should link to most annoying bugs
by bugzilla_noreply＠novell.com 23 Apr '18

23 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=971397 Bug ID: 971397 Summary: https://software.opensuse.org/ should link to most annoying bugs Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other URL: https://software.opensuse.org/421/en OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Software Portal Assignee: benji(a)opensuse.org Reporter: aspiers(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Development Blocker: --- Since https://software.opensuse.org/421/en or similar are linked to from https://www.opensuse.org/, it is the main page users will refer to when installing openSUSE. Therefore it is important that any known bugs with the installation process are prominently accessible. However I found it quite hard (i.e. multiple hops) to navigate to this page: https://en.opensuse.org/openSUSE:Most_annoying_bugs_42.1 This seems to be confirmed by: https://en.opensuse.org/Special:WhatLinksHere/openSUSE:Most_annoying_bugs_4… On the positive side, I see it's linked from here at least: https://en.opensuse.org/Portal:42.1 Maybe that's a better portal. -- You are receiving this mail because: You are on the CC list for the bug.

1 5