August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 906067] New: Totem SEGFAULT with .avi movies
by bugzilla_noreply＠novell.com 13 Dec '17

13 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=906067 Bug ID: 906067 Summary: Totem SEGFAULT with .avi movies Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: roger.luedecke(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Originally Totem would play .avi withoug video; audio only. I then installed the Fluendo Codec Pack. Now thumbnails display in Totem and Nautilus. Both Nautilus preview and Totem instantly crash when attempting to play video in .avi. When run from CLI Totem reports a SEGFAULT. Likely related bug reports: https://bugzilla.opensuse.org/show_bug.cgi?id=887781 https://bugzilla.opensuse.org/show_bug.cgi?id=848833 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 904551] New: Totem could not startup
by bugzilla_noreply＠novell.com 12 Dec '17

12 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904551 Bug ID: 904551 Summary: Totem could not startup Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: whoknows2012(a)myopera.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Totem vserion: 3.10.1 Error message: Some necessary plug-ins are missing. Make sure that the program is correctly installed. Nothing that I found in the Internet is working. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 509945] New: Enforce packaging of static libraries by rpmlint check
by bugzilla_noreply＠novell.com 09 Dec '17

09 Dec '17

http://bugzilla.novell.com/show_bug.cgi?id=509945 Summary: Enforce packaging of static libraries by rpmlint check Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: dmueller(a)novell.com ReportedBy: prusnak(a)novell.com QAContact: qa(a)suse.de CC: ro(a)novell.com, mrueckert(a)novell.com, crrodriguez(a)novell.com Found By: Development We are trying to adopt the static libraries packaging scheme described on http://en.opensuse.org/Packaging/Guidelines#Packaging_Static_Libraries By adding rpmlint check we will enforce the correct packaging. rpmlint should check whether the package contains *.{a,la} files and perform these steps: a) package contains *.la files, does not contain *.a files -> throw error suggesting the packager to remove *.la files in %install phase b) package contains only *.la and *.a files -> check if the name ends with "-devel-static", throw error otherwise, suggesting the rename c) package contains *.la, *.a files AND *.so files (and probably some includes) -> check if the name ends with "-devel" AND package also provides "-devel-static" symbol, throw error otherwise, suggesting the addition of symbol -> also point out that packager has to be sure that static libraries are absolutely needed in the system. If not the package should be built with --disable-static and *.la files removed in %install phase -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 884004] New: bzip2 -dcf skips the first block if fed uncompressed data
by bugzilla_noreply＠novell.com 09 Dec '17

09 Dec '17

https://bugzilla.novell.com/show_bug.cgi?id=884004 https://bugzilla.novell.com/show_bug.cgi?id=884004#c0 Summary: bzip2 -dcf skips the first block if fed uncompressed data Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnweiger(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- $ echo hello world | bzip2 -dcf returns nothing. I'd expect to see 'hello world'. According to the manual, the effects of -f include: "bzip2 normally declines to decompress files which don't have the correct magic header bytes. If forced (-f), however, it will pass such files through unmodified. This is how GNU gzip behaves. strace includes: read(0, "hello world\n", 4096) = 12 read(0, "", 4096) = 0 lseek(0, 0, SEEK_SET) = -1 ESPIPE (Illegal seek) read(0, "", 4096) = 0 close(0) = 0 I assume, the failing lseek() should be acted on. Possibly already an upstream issue? -- 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 7

[Bug 709260] New: package bzip2 missing documentation
by bugzilla_noreply＠novell.com 09 Dec '17

09 Dec '17

https://bugzilla.novell.com/show_bug.cgi?id=709260 https://bugzilla.novell.com/show_bug.cgi?id=709260#c0 Summary: package bzip2 missing documentation Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB7.1) The documentation for package bzip2 is not installed. Reproducible: Always Steps to Reproduce: 1. Read /usr/share/doc/packages/bzip2/README. 2. Find the referenced documentation. Actual Results: 1. Complete documentation is available in Postscript form (manual.ps), PDF (manual.pdf) or html (manual.html). A plain-text version of the manual page is available as bzip2.txt. 2. Nope. Expected Results: 2. /usr/share/doc/packages/bzip2/manual.html -- 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 4

[Bug 907873] New: bash tab completion is erratic in opensuse 13.2
by bugzilla_noreply＠novell.com 06 Dec '17

06 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=907873 Bug ID: 907873 Summary: bash tab completion is erratic in opensuse 13.2 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jimoe(a)sohnen-moe.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The shell (bash) tab completion is now erratic in opensuse v13.2. For instance: ----[ example ]---- The directory name is "1 rk forms-front folder". LS_OPTIONS="--literal --color --tabsize=0 --classify" alias ls="/bin/ls $LS_OPTIONS" alias ll="ls -lh" $ ls 1\ r<TAB> yields $ ls 1\ rk\ forms-front\ folder/ $ ll 1\ r<TAB> yields $ ll 1 rk forms-front folder ----[ end ]---- I never know which completion will happen when I enter a <TAB>. There does not seem to be any obvious pattern to command usage or alias-ing. If I "mv /etc/profile.d/bash_completion.sh /etc/profile.d/bash_completion.sh-bak" and restart the session, this problem does not occur. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 912316] New: fail2ban failed to start after install but.. jail.local have errors
by bugzilla_noreply＠novell.com 30 Nov '17

30 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=912316 Bug ID: 912316 Summary: fail2ban failed to start after install but.. jail.local have errors Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: jonte1(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 619018 --> http://bugzilla.opensuse.org/attachment.cgi?id=619018&action=edit error messages fail2ban is in the repos. Easy as baking a cake. Zypper in.. No. Refuse to start after install. Had a look with yast(not yast2)/software and I was recommended 2 additional packages (firewall2 integration). But no. See attached file(fail2ban) over errors. The solution is to adjust the package writing the etc/fail2ban/jail.local in the 4th row. Before: # test [DEFAULT] # a space delimited list of IP addresses, CIDR prefixes, or DNS hostnames # to bypass fail2ban protection .... Should be: # test [DEFAULT] # a space delimited list of IP addresses, CIDR prefixes, or DNS #hostnames # to bypass fail2ban protection .... regards -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 934507] New: VUL-0: CVE-2015-4165: elasticsearch: unspecified arbitrary files modification vulnerability
by bugzilla_noreply＠novell.com 28 Nov '17

28 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=934507 Bug ID: 934507 Summary: VUL-0: CVE-2015-4165: elasticsearch: unspecified arbitrary files modification vulnerability Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other URL: https://smash.suse.de/issue/117585/ OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: heinemannj66(a)gmail.com Reporter: astieger(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: security-team(a)suse.de Found By: Security Response Team Blocker: --- Courtesy bug for elasticsearch, as found in devel:languages:python and /security:logging:elma:devel. Not in any openSUSE distribution. All Elasticsearch versions from 1.0.0 to 1.5.2 are vulnerable to an attack that uses Elasticsearch to modify files read and executed by certain other applications. Upstream bug/commit unknown at the time of writing. Mitigation: =========== Users should upgrade to 1.6.0. Alternately, ensure that other applications are not present on the system, or that Elasticsearch cannot write into areas where these applications would read. External References: https://www.elastic.co/community/security/ References: https://bugzilla.redhat.com/show_bug.cgi?id=1230761 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-4165 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4165 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 941046] New: e.g. not i.e. in a dialog
by bugzilla_noreply＠novell.com 26 Nov '17

26 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=941046 Bug ID: 941046 Summary: e.g. not i.e. in a dialog Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Nick_Levinson(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The abbreviation "i.e." is wrong in context. It means '_id est_' or 'in other words', so that "the management of . . . media" is only about "how cameras should be handled", when it's really about much more. It should be replaced with "e.g.," (including the comma), because "e.g." means '_exempli gratia_' or 'for example'. This is on AMD hardware and in IceWM desktop > SUSE > Utilities > Desktop > File Manager > File Manager Preferences > Advanced > Volume Management. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 937061] New: perl-qt4 badly broken: loading QtCore4 crashes
by bugzilla_noreply＠novell.com 19 Nov '17

19 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=937061 Bug ID: 937061 Summary: perl-qt4 badly broken: loading QtCore4 crashes Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: novell(a)vertone.co.uk QA Contact: qa-bugs(a)suse.de CC: daxim(a)cpan.org Depends on: 757200 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #757200 +++ This is a duplicate of Bug #757200 but since 12.1 has reached its end-of-life I've created a new bug report. perl-qt4 is broken. Any attempt to use it results in a failed to load QtCore4.so message: -$ perl -e 'use QtCore4; ' Can't load '/usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/auto/QtCore4/QtCore4.so' for module QtCore4: libperl.so: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.20.1/XSLoader.pm line 68. at /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/QtCore4.pm line 1643. Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1. Running strace reveals that QtCore4.so is successfully loaded. The problem is that after loading QtCore4.so it then searches in the wrong place for libperl.so. It searches under the /lib64 and /usr/lib64 directory trees when libperl.so is located under the /usr/lib/perl5 tree. As a temporary fix, adding the following soflink resolves the problem: ln -s /usr/lib/perl5/5.20.1/x86_64-linux-thread-multi/CORE/libperl.so /usr/lib64/libperl.so -- You are receiving this mail because: You are on the CC list for the bug.

1 4