November 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 955428] New: Installation of xmlcharent-0.3-427.1 shows error
by bugzilla_noreply＠novell.com 08 Dec '17

08 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=955428 Bug ID: 955428 Summary: Installation of xmlcharent-0.3-427.1 shows error Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: freek(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Installation of xmlcharent-0.3-427.1 shows the following error: Additional rpm output: I/O error : Attempt to load network entity http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd /etc/xml/catalog:2: warning: failed to load external entity "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd" V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd" ^ sgml-register-catalog: addition of /usr/share/xmlcharent/xmlcharent.sgml in /etc/sgml/catalog -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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 954588] New: After upgrade to kernel-default 4.3.0 rotation and ambient brightness sensors stopped working
by bugzilla_noreply＠novell.com 06 Dec '17

06 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=954588 Bug ID: 954588 Summary: After upgrade to kernel-default 4.3.0 rotation and ambient brightness sensors stopped working Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since TW recently got the kernel 4.3.0 update, the rotation and brightness sensors on my laptop stopped working. Until kernel 4.2.4, using the software from https://github.com/hadess/iio-sensor-proxy allowed the screen to automatically rotate depending on the panel orientation and allowed the brightness of the screen to be automatically adjusted depending on ambient light. All this stopped as soon as the update to kernel 4.3.0 was done. In fact if I boot into the 4.2.4 kernel, the sensors still work. It seems like there was a regression in the iio subsystem going from 4.2.x to 4.3.0. Happy to provide logs as required. For now, an initial discussion is also available at the iio-sensor-proxy upstream: https://github.com/hadess/iio-sensor-proxy/issues/55 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[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

[Bug 932003] New: wrong system language
by bugzilla_noreply＠novell.com 18 Nov '17

18 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=932003 Bug ID: 932003 Summary: wrong system language Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: g.bluehut(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Last night I installed two times like this using openSUSE 13.2 DVD iso: Selecting: Language: English Keyboard: German Location: Germany DE: XFCE When the installation was finished, XFCE and many programs (except yast, maybe there are not translations?) where in german, instead of english. # echo $LANG de_DE.utf8 RC_LANG in /etc/sysconfig: en_US.UTF-8 Kind of confusing, hope someone can shed some light on this. Not sure whether it is a problem of yast, XFCE or me :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 912584] New: WWAN broken after upgrade 13.1 to 13.2
by bugzilla_noreply＠novell.com 17 Nov '17

17 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=912584 Bug ID: 912584 Summary: WWAN broken after upgrade 13.1 to 13.2 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: richard(a)nod.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I can no longer use my WWAN connection. Networkmanager logs: --- 2015-01-10T10:09:48.094382+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... 2015-01-10T10:09:48.095054+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... 2015-01-10T10:09:48.095615+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: need-auth -> prepare (reason 'none') [60 40 0] 2015-01-10T10:09:48.096162+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. 2015-01-10T10:09:48.103749+01:00 sandpuppy NetworkManager[1600]: <warn> (ttyUSB2) failed to connect modem: PolicyKit authorization error: 'authority not found' 2015-01-10T10:09:48.104445+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: prepare -> failed (reason '(null)') [40 120 1] 2015-01-10T10:09:48.105036+01:00 sandpuppy NetworkManager[1600]: <info> NetworkManager state is now CONNECTED_LOCAL 2015-01-10T10:09:48.106073+01:00 sandpuppy NetworkManager[1600]: <info> Disabling autoconnect for connection 'A1/Telekom Austria - A1 Breitband'. 2015-01-10T10:09:48.106571+01:00 sandpuppy NetworkManager[1600]: <warn> Activation (ttyUSB2) failed for connection 'A1/Telekom Austria - A1 Breitband' 2015-01-10T10:09:48.107030+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: failed -> disconnected (reason 'none') [120 30 0] 2015-01-10T10:09:48.107482+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): deactivating device (reason 'none') [0] 2015-01-10T10:10:25.290151+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) starting connection 'A1/Telekom Austria - A1 Breitband' 2015-01-10T10:10:25.291302+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... 2015-01-10T10:10:25.292154+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... 2015-01-10T10:10:25.292931+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0] 2015-01-10T10:10:25.293724+01:00 sandpuppy NetworkManager[1600]: <info> NetworkManager state is now CONNECTING 2015-01-10T10:10:25.294449+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: prepare -> need-auth (reason 'none') [40 60 0] 2015-01-10T10:10:25.295167+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. 2015-01-10T10:10:25.318331+01:00 sandpuppy NetworkManager[1600]: (NetworkManager:1600): libnm-util-CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed 2015-01-10T10:10:25.393312+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... 2015-01-10T10:10:25.393994+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... 2015-01-10T10:10:25.394531+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: need-auth -> prepare (reason 'none') [60 40 0] 2015-01-10T10:10:25.395268+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. 2015-01-10T10:10:25.402549+01:00 sandpuppy NetworkManager[1600]: <warn> (ttyUSB2) failed to connect modem: PolicyKit authorization error: 'authority not found' 2015-01-10T10:10:25.403277+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: prepare -> failed (reason '(null)') [40 120 1] 2015-01-10T10:10:25.404311+01:00 sandpuppy NetworkManager[1600]: <info> NetworkManager state is now CONNECTED_LOCAL 2015-01-10T10:10:25.404927+01:00 sandpuppy NetworkManager[1600]: <info> Disabling autoconnect for connection 'A1/Telekom Austria - A1 Breitband'. 2015-01-10T10:10:25.405455+01:00 sandpuppy NetworkManager[1600]: <warn> Activation (ttyUSB2) failed for connection 'A1/Telekom Austria - A1 Breitband' 2015-01-10T10:10:25.405993+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: failed -> disconnected (reason 'none') [120 30 0] 2015-01-10T10:10:25.406506+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): deactivating device (reason 'none') [0] --- Any ideas? -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 910933] New: Canna can not start
by bugzilla_noreply＠novell.com 17 Nov '17

17 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=910933 Bug ID: 910933 Summary: Canna can not start Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bkbin005(a)rinku.zaq.ne.jp QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed canna-devel in openSUSE 13.2. But I can not start Canna. Steps to Reproduce: 1) install openSUSE 13.2 2) sudo zypper install canna-devel 3) sudo systemctl status canna.service Actual Results: mitsutoshi@linux-rvvx:~> sudo systemctl start canna.service root's password: Job for canna.service failed. See "systemctl status canna.service" and "journalctl -xn" for details. mitsutoshi@linux-rvvx:~> sudo systemctl status canna.service canna.service - Canna Japanese Conversion Engine Loaded: loaded (/usr/lib/systemd/system/canna.service; disabled) Active: failed (Result: exit-code) since Sun 2014-12-21 09:57:54 JST; 32s ago Process: 6362 ExecStart=/usr/sbin/cannaserver -syslog (code=exited, status=1/FAILURE) Dec 21 09:57:54 linux-rvvx cannaserver[6362]: /usr/sbin/cannaserver: invalid option -- 'y' Dec 21 09:57:54 linux-rvvx cannaserver[6362]: Usage: cannaserver [-p num] [-l num] [-u us...e] Hint: Some lines were ellipsized, use -l to show in full. mitsutoshi@linux-rvvx:~> sudo systemctl -l status canna.service canna.service - Canna Japanese Conversion Engine Loaded: loaded (/usr/lib/systemd/system/canna.service; disabled) Active: failed (Result: exit-code) since Sun 2014-12-21 09:57:54 JST; 50s ago Process: 6362 ExecStart=/usr/sbin/cannaserver -syslog (code=exited, status=1/FAILURE) Dec 21 09:57:54 linux-rvvx cannaserver[6362]: /usr/sbin/cannaserver: invalid option -- 'y' Dec 21 09:57:54 linux-rvvx cannaserver[6362]: Usage: cannaserver [-p num] [-l num] [-u userid] [-syslog] [-inet] [-d] [dichome] mitsutoshi@linux-rvvx:~> sudo journalctl -xn -- Logs begin at Sat 2014-12-13 16:32:42 JST, end at Sun 2014-12-21 09:59:12 JST. -- Dec 21 09:57:54 linux-rvvx cannaserver[6362]: Usage: cannaserver [-p num] [-l num] [-u userid] Dec 21 09:57:54 linux-rvvx sudo[6359]: pam_unix(sudo:session): session closed for user root Dec 21 09:58:27 linux-rvvx sudo[6367]: mitsutoshi : TTY=pts/1 ; PWD=/home/mitsutoshi ; USER=ro Dec 21 09:58:27 linux-rvvx sudo[6367]: pam_unix(sudo:session): session opened for user root by Dec 21 09:58:27 linux-rvvx sudo[6367]: pam_unix(sudo:session): session closed for user root Dec 21 09:58:45 linux-rvvx sudo[6371]: mitsutoshi : TTY=pts/1 ; PWD=/home/mitsutoshi ; USER=ro Dec 21 09:58:45 linux-rvvx sudo[6371]: pam_unix(sudo:session): session opened for user root by Dec 21 09:58:45 linux-rvvx sudo[6371]: pam_unix(sudo:session): session closed for user root Dec 21 09:59:12 linux-rvvx sudo[6375]: mitsutoshi : TTY=pts/1 ; PWD=/home/mitsutoshi ; USER=ro Dec 21 09:59:12 linux-rvvx sudo[6375]: pam_unix(sudo:session): session opened for user root by I can reproduce this issue every time. Expected Results: Canna should start. Build Date & Hardware: Installed 2014-12-13 on VirtualBox 4.3.20 r96996 in Windows 7 Ultimate SP1. Please see also: http://lists.opensuse.org/opensuse-ja/2014-12/msg00017.html http://lists.opensuse.org/opensuse-ja/2014-12/msg00022.html -- You are receiving this mail because: You are on the CC list for the bug.

1 11