January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 916933] New: Tuxwordsmith crashes on automated turn
by bugzilla_noreply＠novell.com 17 Oct '18

17 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=916933 Bug ID: 916933 Summary: Tuxwordsmith crashes on automated turn Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ez2blost(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tuxwordsmith crashes when the computer animates the end of an automated move Traceback (most recent call last): File "/usr/bin/TuxWordSmith", line 51, in <module> x=TuxWordSmithAppWX() File "/usr/lib/python2.7/site-packages/TuxWordSmith/tws_wx.py", line 38, in __init__ mode,level=prog.run() File "/usr/lib/python2.7/site-packages/TuxWordSmith/tws.py", line 451, in run self.take_turn() File "/usr/lib/python2.7/site-packages/TuxWordSmith/tws.py", line 561, in take_turn if self.global_config['TILE_ANIMATIONS']['value']==1: KeyError: 'TILE_ANIMATIONS' (Also tuxwordsmith.sh has typos Tries to run TuxTuxWordSmith instead of TuxWordSmith -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1021578] New: Bug in the version of PyOpenSSL installed in OpenSUSE LEAP 42.2.
by bugzilla_noreply＠novell.com 16 Oct '18

16 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1021578 Bug ID: 1021578 Summary: Bug in the version of PyOpenSSL installed in OpenSUSE LEAP 42.2. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stuart.knock(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: There is an issue with the version of PyOpenSSL installed in OpenSUSE LEAP 42.2 The issue is known and fixed upstream. It was introduced and patched over a period of a few months last year. Unfortunately, the version in 42.2 is from that few month period. Relevant links to issues, and the pull request that was the main fix are below. The bug results in log spam (to the point of filling hard-drives) and seg-faults in applications that make use of these libraries in a certain way. The example I encountered is that Kodi's add-on system is completely broken for LEAP 42.2 as a result of this bug. Would it be possible to get either updated versions of PyOpenSSL (and possibly the cryptography package as well, see issue links below) made available or patches applied to fix the bug for LEAP 42.2? #Log spam issue https://github.com/pyca/pyopenssl/issues/551 #Issues caused on interaction with the python cryptography package https://github.com/pyca/pyopenssl/issues/520 https://github.com/pyca/cryptography/issues/2913 https://github.com/pyca/cryptography/issues/2299 #Kodi Plugin system doesn't work: https://github.com/pyca/pyopenssl/issues/542 https://github.com/Kolifanes/plugin.video.youtube/issues/60 http://trac.kodi.tv/ticket/16914 #The pyOpenSSL fix https://github.com/pyca/pyopenssl/pull/552 https://github.com/pyca/pyopenssl/pull/552/commits/a84a52ceeb8deb602515ebf7… Reproducible: Always Steps to Reproduce: 1.Install OpenSUSE 42.2 2.Add Packman repo 3.Install kodi 4.Try to use/install Kodi add-ons (eg youtube add-on) Actual Results: Results vary depending on add-on involved. The two main forms are seg-fault that causes Kodi to crash, or the logs are spammed with thousands of messages per second of the form: Jan 23 15:31:45 borg kodi.desktop[2458]: extern "Python": function Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. Jan 23 15:31:45 borg kodi.desktop[2458]: extern "Python": function Cryptography_rand_status() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. Jan 23 15:31:45 borg kodi.desktop[2458]: extern "Python": function Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. Jan 23 15:31:45 borg kodi.desktop[2458]: extern "Python": function Cryptography_rand_status() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. Jan 23 15:31:45 borg kodi.desktop[2458]: extern "Python": function Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. Jan 23 15:31:45 borg kodi.desktop[2458]: extern "Python": function Cryptography_rand_status() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. Expected Results: No seg-faults. No log-spam. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 978057] New: network:samba:TESTING/samba: Bug 'samba-tool' is still missing if Samba package is compiled with AD DC functions
by bugzilla_noreply＠novell.com 12 Oct '18

12 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=978057 Bug ID: 978057 Summary: network:samba:TESTING/samba: Bug 'samba-tool' is still missing if Samba package is compiled with AD DC functions Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: lmuelle(a)suse.com Reporter: bjoernv(a)arcor.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: ddiss(a)suse.com, jmcdonough(a)suse.com Found By: --- Blocker: --- The Samba 4 package network:samba:TESTING/samba has experimental support for Active Directory Domain Controller (AD DC) functionality. The AD DC function is deactivated by default. But even if the option is activated e.g. with rpmbuild -bb --with dc ~/rpmbuild/SPECS/samba.spec the AD DC setup tool 'samba-tool' is missing in binary packages. Reference: https://bugzilla.opensuse.org/show_bug.cgi?id=794744 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1012101] New: Kontact looses custom kmail shortcut definition after first use
by bugzilla_noreply＠novell.com 10 Oct '18

10 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1012101 Bug ID: 1012101 Summary: Kontact looses custom kmail shortcut definition after first use Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## observation On Leap 42.2 in kontact5 I configured a custom shortcut for kmail for the action "archive". The shortcut works once as expected but does not work afterwards anymore. Checking the shortcut in the configuration dialog shows that the key definition is gone again, i.e. the configuration is lost. On the terminal the following messages are shown: ``` js: Uncaught TypeError: qt.jQuery is not a function js: Uncaught TypeError: qt.jQuery is not a function js: Uncaught TypeError: qt.jQuery is not a function ``` ## steps to reproduce * Given kontact and kmail is configured and no shortcut set for 'archive' operation but an archive folder for emails has been configured * start kontact * configure shortcut for 'archive' operation within the kmail component * select any email * press the shortcut key and see that the email is moved into the archive folder * press shortcut again and see that nothing happens * check configuration of keys and see that the configuration for archive operation disappeared ## further details Versions: kontact5/kmail5: 16.08.2-1.1 ## workaround Starting kmail on its own and setting the shortcut there will keep it permanently. It also works in kontact afterwards. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 977812] New: sshd killed by SIGSYS on client connection
by bugzilla_noreply＠novell.com 10 Oct '18

10 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=977812 Bug ID: 977812 Summary: sshd killed by SIGSYS on client connection Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mkubecek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 675044 --> http://bugzilla.suse.com/attachment.cgi?id=675044&action=edit strace output for "/usr/sbin/sshd -ddd" After today's big update, I'm unable to connect to the machine using SSH. With debugging enabled, last things I see on the client are debug2: kex_parse_kexinit: none,zlib(a)openssh.com debug2: kex_parse_kexinit: none,zlib(a)openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-sha2-512-etm(a)openssh.com debug1: kex: server->client aes128-ctr hmac-sha2-512-etm(a)openssh.com none debug2: mac_setup: found hmac-sha2-512-etm(a)openssh.com debug1: kex: client->server aes128-ctr hmac-sha2-512-etm(a)openssh.com none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY Connection closed by 172.17.1.2 and on the server debug1: kex: client->server aes128-ctr hmac-sha2-512-etm(a)openssh.com none [preauth] debug3: mm_request_send entering: type 118 [preauth] debug3: mm_request_receive_expect entering: type 119 [preauth] debug3: mm_request_receive entering [preauth] debug3: mm_request_receive entering debug3: monitor_read: checking request 118 debug3: mm_request_send entering: type 119 debug2: mac_setup: setup hmac-sha2-512-etm(a)openssh.com [preauth] debug1: kex: server->client aes128-ctr hmac-sha2-512-etm(a)openssh.com none [preauth] debug3: mm_request_send entering: type 118 [preauth] debug3: mm_request_receive_expect entering: type 119 [preauth] debug3: mm_request_receive entering [preauth] debug3: mm_request_receive entering debug3: monitor_read: checking request 118 debug3: mm_request_send entering: type 119 debug1: monitor_read_log: child log fd closed debug3: mm_request_receive entering debug1: do_cleanup debug3: PAM: sshpam_thread_cleanup entering debug1: Killing privsep child 3537 strace says the child was killed by SIGSYS and so does gdb. However, so far I wasn't able to get a core dump or even find where does this happen. Output of strace output is attached, not much interesting in gdb output except Program terminated with signal SIGSYS, Bad system call. The program no longer exists. A little research indicates SIGSYS may have something to do with seccomp and indeed, commenting out the line UsePrivilegeSeparation sandbox # Default for new installations. in sshd_config makes sshd work again. Current openssh version is 6.6p1-11.2 and previous (working) version was 6.6p1-11.1, i.e. this is only a rebuild so that the issue might have been triggered by glibc update. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 942811] New: upgrade OpenSSH
by bugzilla_noreply＠novell.com 08 Oct '18

08 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=942811 Bug ID: 942811 Summary: upgrade OpenSSH Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Network Assignee: pcerny(a)suse.com Reporter: pcerny(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Upgrade OpenSSH in openSUSE including forward porting the patches for now not working only in SLE. Potentially upgrade 13.1/.2 as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 959854] New: plasmashell: High CPU load
by bugzilla_noreply＠novell.com 07 Oct '18

07 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=959854 Bug ID: 959854 Summary: plasmashell: High CPU load Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 660002 --> http://bugzilla.opensuse.org/attachment.cgi?id=660002&action=edit output of top Plasmashell creates 'suddenly' a high CPU load, see attachement. 'Suddenly' n this case means that I could not really determine the reason for this up to now. It mostly happens after a resume from S2RAM (but not always), after a switch to a different activity in plasma (but not always), and after a change in WIFI-network (but not always) Any idea how I could get to the root cause of this problem? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 960460] New: Error when adding a new repository
by bugzilla_noreply＠novell.com 04 Oct '18

04 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=960460 Bug ID: 960460 Summary: Error when adding a new repository Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: silviu_marin-caea(a)otpbank.ro QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 660604 --> http://bugzilla.suse.com/attachment.cgi?id=660604&action=edit YaST/Software Repositories Error Cannot add a new repository with YaST/Software Repositories. Gives error from the attached screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 943757] New: yast storage with ncurses does not due to nokogiri error message
by bugzilla_noreply＠novell.com 04 Oct '18

04 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=943757 Bug ID: 943757 Summary: yast storage with ncurses does not due to nokogiri error message Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- For various ruby programs I have installed a bunch of gems from different sources (which I have no overview of). Anyway, many ruby programs print an error during startup, this can be show using irb: aschnell@thalassa:~> irb irb(main):001:0> require "dbus" WARNING: Nokogiri was built against LibXML version 2.9.2, but has dynamically loaded 2.9.1 => true Unfortunately for yast ncurses this causes a program termination since stderr is in a bad state (I suppose closed): [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):25 cannot require yast:Bad file descriptor @ io_write - <STDERR> at /usr/lib64/ruby/gems/2.1.0/gems/nokogiri-1.6.6.2/lib/nokogiri/version.rb:94:in `write' The rest of y2log is very misleading, e.g. stating the Storage.rb does not provide the module Storage. But with the Qt frontend YaST does start. The system is openSUSE 13.2 with YaST:Head and various ruby gems. -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1006441] New: Grub detects Manjaro incorrectly
by bugzilla_noreply＠novell.com 03 Oct '18

03 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1006441 Bug ID: 1006441 Summary: Grub detects Manjaro incorrectly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: vlad(a)intpal.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 698816 --> http://bugzilla.opensuse.org/attachment.cgi?id=698816&action=edit os-prober logs I get "kernel panic-not syncing: VFS: unable to mount root fs on unknown block(0,0)" when booting Manjaro via the os-prober entry generated by openSUSE GRUB. I am attaching the os-prober logs. Note that Manjaro boots okay if I manually add the correct entry (taken from Manjaro GRUB). -- You are receiving this mail because: You are on the CC list for the bug.

1 9