March 2016 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 961913] New: security/ecryptfs-utils: Bug %post execution of pam-config fails on 64bit because 32bit package is not installed
by bugzilla_noreply＠novell.com 27 Sep '18

27 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=961913 Bug ID: 961913 Summary: security/ecryptfs-utils: Bug %post execution of pam-config fails on 64bit because 32bit package is not installed Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: meissner(a)suse.com Reporter: darin(a)darins.net QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- The execution of 'pam-config -a --ecryptfs' in %post fails on 64bit systems when 32bit pam libraries are installed, unless ecryptfs-utils-32bit is installed first. This failure causes the requisite pam configuration for ecryptfs to not be set, rendering it unusable until someone executes 'pam-config -a --ecryptfs'. # 2016-01-14 08:57:15 ecryptfs-utils-103-1.2.x86_64.rpm installed ok # Additional rpm output: # setting /sbin/mount.ecryptfs_private to root:root 4755. (wrong permissions 0755) # ERROR: module /lib/security/pam_ecryptfs.so is not installed. # warning: %post(ecryptfs-utils-103-1.2.x86_64) scriptlet failed, exit status 1 2016-01-14 08:57:15|install|ecryptfs-utils|103-1.2|x86_64|root@alpinist.athenex.com|repo-oss|89a0849166ef2c6382150534cc22166a6a4c6263| 2016-01-14 08:57:15|install|gnome-keyring-32bit|3.16.0-7.1|x86_64||repo-update|be9d8a3fb5b34ab38b848ed17f7b7a6b032cafd81a27b3e5c470d132b858baf5| 2016-01-14 08:57:15|install|libfreebl3-32bit|3.20.2-6.1|x86_64||repo-update|231b3bc9e17a5ce06b89e624340144157ef9f6908c321a7fe1c7e99bd430ba8f| 2016-01-14 08:57:15|install|mozilla-nspr-32bit|4.10.10-4.1|x86_64||repo-update|80d1c4c057c01ee579810038b726c74d85370eff3abe439e228810f27d6e4380| 2016-01-14 08:57:15|install|mozilla-nss-certs-32bit|3.20.2-6.1|x86_64||repo-update|7feacc18276f36d6711102568f0703fb55f0fe05a10f84019dd454d8feb8aa64| 2016-01-14 08:57:15|install|mozilla-nss-32bit|3.20.2-6.1|x86_64||repo-update|5e21bacb982e68e8ad02c1625fc04f272b81a9594dcf024d1e8cfbd53b60c4f4| 2016-01-14 08:57:16|install|libsoftokn3-32bit|3.20.2-6.1|x86_64||repo-update|ac71df84df77c5cd41f4c61dd9cd149fab9163bdd26f900f87b619496ae4c13e| 2016-01-14 08:57:16|install|libpkcs11-helper1-32bit|1.11-2.2|x86_64||repo-oss|77649250d1d56c1431454cfbdfa5463a0ca42ed1| 2016-01-14 08:57:16|install|ecryptfs-utils-32bit|103-1.2|x86_64||repo-oss|99c66f34c97fa274b0fcb044a3bfcd30b227f660| -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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

[Bug 941862] New: GNOME Software won't open RPM files
by bugzilla_noreply＠novell.com 03 Sep '18

03 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=941862 Bug ID: 941862 Summary: GNOME Software won't open RPM files Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: castar(a)cipelli.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0 Build Identifier: When downloading RPMs from the internet, the option is given to open them with GNOME Software (presumably to install them). However, when doing so, Software opens with an error: "GetDetailsLocal not supported by backend". Reproducible: Always Steps to Reproduce: 1. Download an RPM for openSUSE. 2. Open it using GNOME Software. Actual Results: Gave error "GetDetailsLocal not supported by backend" Expected Results: Given details about the package. This happened on my old laptop and my new computer (HP G56 with AMD V140 and custom-built with AMD A10-7700K respectively). -- You are receiving this mail because: You are on the CC list for the bug.

1 11