December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 906727] New: mass rename all openSUSE_Factory targets that refer to the snapshot repository to openSUSE_Tumbleweed
by bugzilla_noreply＠novell.com 22 Feb '18

22 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=906727 Bug ID: 906727 Summary: mass rename all openSUSE_Factory targets that refer to the snapshot repository to openSUSE_Tumbleweed 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: cobexer(a)gmail.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- Now that openSUSE_Tumbleweed has backing of the openSUSE project OBS should be cleaned up to make sure that Tumbleweed users never have the need to add a openSUSE_Factory repository to their machines that isn't actually meant to be added to a Tumbleweed system. Adding an openSUSE_Factory repository should never be suggested for anyone that uses Tumbleweed - it's too hard to tell if this is correct or not (one needs to read and understand the Meta xml of the repo config to figure out if that openSUSE_Factory refers to standard or snapshot). I believe this should be done at least to all repos outside of the home: namespace to save every repository maintainers to do this manually. The patching should also remove a openSUSE_Factory target if a Tumbleweed one already exists and the Factory one refers to snapshot to avoid wasting build cycles. Currently using Tumbleweed is a bit annoying as lots of repos aren't available for it yet and one has to use Factory repos for those. Example: https://build.opensuse.org/project/show/server:php:extensions Even worse are repos where the maintainers are ignorant or unwilling to do the renaming / adding of the Tumbleweed repo: https://build.opensuse.org/project/show/devel:tools:building please solve this on the project level thanks in advance -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 911505] New: YaST partitioner is mounting a NTFS drive with a dmask=022 it should be dmask=002
by bugzilla_noreply＠novell.com 22 Feb '18

22 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=911505 Bug ID: 911505 Summary: YaST partitioner is mounting a NTFS drive with a dmask=022 it should be dmask=002 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pereira1819(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Mounted NTFS drive through YaST->Partitioner it's setting an incorrect dmask value of 022. this should be set to 002. >From Partitioner UUID=AT443R$145D3AF4X /home/pictures ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 908472] New: Network manager can't forget WiFi networks.
by bugzilla_noreply＠novell.com 22 Feb '18

22 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=908472 Bug ID: 908472 Summary: Network manager can't forget WiFi networks. Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace Assignee: kde-maintainers(a)suse.de Reporter: darren(a)freemaninstruments.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Going from 12.2 to 13.2, I am no longer able to make the NetworkManager application forget a WiFi network. (Under KDE.) Here is my problem. At a conference, the venue has a flaky free wireless with no password but a proxy server that forces you to view their web-page before you can access anything else. It's terrible, I tried it once, never again. I also have a phone with portable hot-spot. I want to connect to this every time. But the NetworkManager always connects to the free network. I can't make it forget this network. Maybe there is an option, but it's not obvious. I gave up. Either this is a missing feature, or terrible UI design. Either way it's not up to standard; please fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 935445] New: Firefox becomes unresponsive when going to youtube.com
by bugzilla_noreply＠novell.com 22 Feb '18

22 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=935445 Bug ID: 935445 Summary: Firefox becomes unresponsive when going to youtube.com Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: thomas(a)mitterfellner.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tried FF38.0.1 from the distribution repos and 38.0.6 from the community repo. With both versions, when I tried to go to youtube.com, the site loaded (the front page was completely rendered) but the cursor currently active (i.e. the hand cursor when hovering a link) doesn't change anymore while in the firefox window. No other tabs can be opened, the window is unusable. This does not happen with the firefox I downloaded from the mozilla site as a tar.gz package. Notice that I don't even try to play a video but I only visit the front page. I also tried this with a blank account (i.e. mv ~/.mozilla ~/.mozilla.bak and start ff afterwards). -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 901949] New: Valgrind does not support recent Intel instructions
by bugzilla_noreply＠novell.com 22 Feb '18

22 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=901949 Bug ID: 901949 Summary: Valgrind does not support recent Intel instructions Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mjr19(a)cam.ac.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Valgrind does not support the new Haswell instructions. Valgrind is 3.8.1, and 3.9.0 (October 2013) added support for the AVX2 instruction set, as found in Intel's Haswell (released June 2013). OpenSuSE 13.1 (released November 2013) might be expected to support this. pc71:/tmp> cat test.c #include "immintrin.h" #include <stdio.h> int main(){ unsigned int value=1234; unsigned char c; c=_pext_u32(value, 0x11111111); printf("%d\n",(int)c); } pc71:/tmp> g++ -mbmi2 test.c pc71:/tmp> ./a.out 2 pc71:/tmp> valgrind ./a.out [...] vex amd64->IR: unhandled instruction bytes: 0xC4 0xE2 0x7A 0xF5 0xC2 0x88 0x45 0xFB vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=1 VEX.L=0 VEX.nVVVV=0x0 ESC=0F38 vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=1 [...] ==23452== valgrind: Unrecognised instruction at address 0x400642. ==23452== at 0x400642: main (in /tmp/a.out) ==23452== Your program just tried to execute an instruction that Valgrind ==23452== did not recognise. Of course, the above test make sense only when run on a Haswell. Given that 13.1 is an evergreen release, Valgrind probably ought to support fully Intel CPUs released in 2013. Intel's MKL uses some AVX2 instructions unrecognised by the shipped version of Valgrind. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 911289] New: hg-fast-export doesn't work
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=911289 Bug ID: 911289 Summary: hg-fast-export doesn't work Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mikachiari(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Application version is too old and contains an error. ➜ hg-fast-export -r ../dvl.basetech-dev.local/ Traceback (most recent call last): File "/usr/share/hg-fast-export/hg-fast-export.py", line 5, in <module> from mercurial import repo,hg,cmdutil,util,ui,revlog,node ImportError: cannot import name repo Maybe it will be better to update application version to newer. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 918051] New: After latest Glib update, KDE applications crash often
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=918051 Bug ID: 918051 Summary: After latest Glib update, KDE applications crash often Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: ivan.topolsky(a)isb-sib.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 Build Identifier: Recently, lots of KDE applications have started to crash randomly. (Most often hadden with Plasma Workspace, and a few daemons like Bluetooth, etc.) After reading the dumps in KDE's crash reporter, it seems to me that most of the time, the crashed thread is either running in GLib, or some other function in the call stack further down called from within GLib. It seems to happens most often: - after resume from "Suspend-to-RAM" - after closing a KDE application (it crashes instead of closing) - after logging out (nearly always a KDE application or a few will crash. Workspace and daemon are the most popular, but other KDE apps might crash too). I've already filled one crash report with KDE's reporter. see KDE bug 344024 : https://bugs.kde.org/show_bug.cgi?id=344024 I can keep filing such crash dumps if it helps. Reproducible: Sometimes Steps to Reproduce: 1. Just wait. (very rare) Or: resume from "suspend-to-ram" (sometimes) Or: close an application (rarer, that only crashes the application itself) Or: log out (very oftern) Actual Results: One or several applications will crash, KDE crash handler appears, showing a dump, and offering to upload a crash report at bugs.kde.org When looking at the dump, the offending thread is a few calls down from glib. Expected Results: (system should be working crash free) Running KDE & co from stock openSUSE repository. (The 3rd party repo I use is Packman, but that's mostly used for media and should not crash basic KDE application). Everything started following latest glib update from "opensuse 13.2 updates" repo. Luckily I haven't lost any data to it. As mentionned, I can keep filing the crash dumps at bugs.kde.org if it helps. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 905844] New: lxde control center: no text visible under the program icons
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=905844 Bug ID: 905844 Summary: lxde control center: no text visible under the program icons Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: PC OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: LXDE Assignee: andrea(a)opensuse.org Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a fresh 13.2 installation, usign LXDE, the window of LXDE control center only shows the program icons but there is no text under the icons. The only icon with text is the Install Software icon but the text under it is not "Install Software" but "Installed Size:". Clicking on the different icons starts the corresponding programs except for Install Software: the program that is supposed to run (package-manager) included in 13.1 in the package libzypp, does not exist in 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 927219] New: seccheck does not work without /var/log/messages (default Systemd Journal configuration)
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=927219 Bug ID: 927219 Summary: seccheck does not work without /var/log/messages (default Systemd Journal configuration) Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- If openSUSE 13.2 is installed with default packages (logging with Systemd Journal, but without Syslog), the "seccheck" package does not work, because /var/log/messages is missing. cat /etc/cron.d/seccheck RUN_FROM_CRON=yes # # SuSE Security Checks # 0 0 * * * root test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 0 1 * * 1 root test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh weekly & 0 4 1 * * root test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh monthly & # LANG=C /usr/lib/secchk/security-control.sh daily grep: /var/log/messages: No such file or directory grep: /var/log/messages: No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 927637] New: VUL-0: CVE-2015-3138: tcpdump: denial of service in print-wb.c
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=927637 Bug ID: 927637 Summary: VUL-0: CVE-2015-3138: tcpdump: denial of service in print-wb.c Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other URL: https://smash.suse.de/issue/115973/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Network Assignee: vcizek(a)suse.com Reporter: astieger(a)suse.com QA Contact: qa-bugs(a)suse.de CC: puzel(a)suse.com, smash_bz(a)suse.de Found By: Security Response Team Blocker: --- Via RH: Recently an independent researcher had discovered a vulnerability in tcpdump, which would be a segmentation fault triggered through feeding into tcpdump a crafted packet, either from a live network interface or from a .pcap file. It has been assigned CVE-2015-3138 and you can find the steps to reproduce it here: https://github.com/the-tcpdump-group/tcpdump/issues/446 Subsequent analysis made it clear that the vulnerability was introduced into one of tcpdump functions by an accident not long before the 4.7.0 release. It remained in tcpdump releases 4.7.2 and 4.7.3 (4.7.1 was never released). The next release, 4.7.4, will have it fixed, but it is likely to be delayed. Since the vulnerability has been public for a few weeks, meanwhile you might want to fix it in an update to the tcpdump package. The fix is in the following commit: https://github.com/the-tcpdump-group/tcpdump/commit/3ed82f4ed0095768529afc2… openSUSE 13.1: 4.4.0 not affected openSUSE 13.2: 4.6.2 not affected network:utilities: 4.7.3 affected openSUSE:Factory: 4.7.3 affected References: https://bugzilla.redhat.com/show_bug.cgi?id=1212342 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3138 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3138 -- You are receiving this mail because: You are on the CC list for the bug.

1 5