December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 933032] New: KDE Breeze Dark theme in new Plasma workspace no longer renders correctly
by bugzilla_noreply＠novell.com 20 Oct '18

20 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=933032 Bug ID: 933032 Summary: KDE Breeze Dark theme in new Plasma workspace no longer renders correctly Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace Assignee: kde-maintainers(a)suse.de Reporter: jrhodes(a)redpointsoftware.com.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36 Build Identifier: After performing "zypper up" today, the Breeze Dark theme in the Plasma workspace no longer renders correctly, as per the attached screenshot. Reproducible: Always Steps to Reproduce: 1. Select the "Breeze Dark" theme on KDE 5 / Plasma. Actual Results: The panel at the bottom of the screen still has a white background. Expected Results: The panel at the bottom should be themed correctly (have a dark background). -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 820566] New: wireshark security updates to 1.8.7 and 1.6.15
by bugzilla_noreply＠novell.com 19 Oct '18

19 Oct '18

https://bugzilla.novell.com/show_bug.cgi?id=820566 https://bugzilla.novell.com/show_bug.cgi?id=820566#c0 Summary: wireshark security updates to 1.8.7 and 1.6.15 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: Andreas.Stieger(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0 https://www.wireshark.org/docs/relnotes/wireshark-1.8.7.html wnpa-sec-2013-23 CVE-2013-2486 CVE-2013-2487 The RELOAD dissector could go into an infinite loop. wnpa-sec-2013-24 The GTPv2 dissector could crash. wnpa-sec-2013-25 The ASN.1 BER dissector could crash. wnpa-sec-2013-26 The PPP CCP dissector could crash. wnpa-sec-2013-27 The DCP ETSI dissector could crash. wnpa-sec-2013-28 The MPEG DSM-CC dissector could crash. wnpa-sec-2013-29 The Websocket dissector could crash. wnpa-sec-2013-30 The MySQL dissector could go into an infinite loop. wnpa-sec-2013-31 The ETCH dissector could go into a large loop. https://www.wireshark.org/docs/relnotes/wireshark-1.6.15.html 1.6.15 wnpa-sec-2013-25 The ASN.1 BER dissector could crash Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 15

[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 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 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 944302] New: php5 and openhpi fails to build if MD5 and DES support disabled in net-snmp
by bugzilla_noreply＠novell.com 02 Oct '18

02 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=944302 Bug ID: 944302 Summary: php5 and openhpi fails to build if MD5 and DES support disabled in net-snmp Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: meissner(a)suse.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The latest net-snmp SR https://build.opensuse.org/request/show/323040 has disabled md5 and des support, however php5 and openhpi fails to build then. The same issue also effected Leap as https://build.opensuse.org/request/show/325654 which has the similar changes and pending in Leap for same reason. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 911587] New: Message at shutdown: "kernel: watchdog watchdog0: watchdog did not stop!"
by bugzilla_noreply＠novell.com 30 Sep '18

30 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=911587 Bug ID: 911587 Summary: Message at shutdown: "kernel: watchdog watchdog0: watchdog did not stop!" Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Each shutdown seems to hang for a while, then the message "kernel: watchdog watchdog0: watchdog did not stop!" appears. I guess this is not expected. (Next log message is "dmeventd[945]: dmeventd shutting down."; maybe this helps) -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 957071] New: Blueberry OFF toggle does not actually turn off bluetooth
by bugzilla_noreply＠novell.com 09 Sep '18

09 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 Bug ID: 957071 Summary: Blueberry OFF toggle does not actually turn off bluetooth Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, the current Tumbleweed version of the Blueberry bluetooth management GUI (1.1.0) has a big ON/OFF toggle. However, this toggle does nothing. After toggling it OFF and re-opening Bluberry, it is again shown as ON. I am using the integrated bluetooth device of a Lenovo Thinkpad T530 laptop. -- You are receiving this mail because: You are on the CC list for the bug.

1 38

[Bug 904303] New: gnome-keyring hijacked the GPG socket
by bugzilla_noreply＠novell.com 07 Sep '18

07 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=904303 Bug ID: 904303 Summary: gnome-keyring hijacked the GPG socket Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: All Status: NEW Severity: Minor Priority: P5 - None Component: Xfce Assignee: gber(a)opensuse.org Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gpg starts throwing new warnings since openSUSE 13.2. $ gpg -ab blah.txt You need a passphrase to unlock the secret key for user: "Jan Engelhardt <jengelh(a)gmx.de>" 4096-bit RSA key, ID 19FC338D, created 2011-05-09 gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system! $ env GPG_AGENT_INFO=/run/user/25121/keyring/gpg:0:1 $ lsof|grep keyring/gpg gnome-key 3799 jengelh 11u unix 0x0000000000000000 0t0 32398 /run/user/25121/keyring/gpg ... (started by xfce or so) -- You are receiving this mail because: You are on the CC list for the bug.

1 8