August 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 984088] interface config, IP_OPTIONS does not work anymore
by bugzilla_noreply＠novell.com 02 Aug '16

02 Aug '16

http://bugzilla.novell.com/show_bug.cgi?id=984088 http://bugzilla.novell.com/show_bug.cgi?id=984088#c11 Nirmoy Das <nirmoy.das(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nirmoy.das(a)suse.com --- Comment #11 from Nirmoy Das <nirmoy.das(a)suse.com> --- We have done auto6 clean up, can you please let us know whether this recent fix works better for you ? packages can be found in below link http://download.opensuse.org/repositories/network:/wicked:/testing/openSUSE… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 991677] New: auth-server: Impossible to reactivate "use Common Server Certificate"
by bugzilla_noreply＠novell.com 02 Aug '16

02 Aug '16

http://bugzilla.novell.com/show_bug.cgi?id=991677 Bug ID: 991677 Summary: auth-server: Impossible to reactivate "use Common Server Certificate" Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: ralf.habacker(a)freenet.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Entered into CA Management, Created a Root CA, Added server Certificate. Exported as a Common server Certificate. Opened Yast Common server Certificate and confirmed that certificate is exported. Opened Yast Authentication server, Under TLS settings, enabled TLS, Enabled "use Common server certificate" and finished server setup. Reopened Yast Authentication server, goto TLS setting, uncheck "use Common server certificate" and enable "use Common server certificate" again Yast complained that there is no "Common server certificate" available and disables the checkbox. running Y2DEBUG=1 yast2 auth-server shows that the Ca file is searched at /etc/ssl/certs/YaST-CA.pem. In truth the file is located at /usr/share/pki/trust/anchors/YaST-CA.pem. 2016-08-02 13:11:18 <0> linux-t0qd(23365) [Ruby] binary/Yast.cc(ycp_module_call_ycp_function):191 Dynamic Proxy: [AuthServer::HaveCommonServerCertificate] with [4] params 2016-08-02 13:11:18 <0> linux-t0qd(23365) [Ruby] binary/Yast.cc(ycp_module_call_ycp_function):200 Namespace created from .../AuthServer 2016-08-02 13:11:18 <0> linux-t0qd(23365) [Y2Perl] YPerlNamespace.cc(createFunctionCall):522 Creating function call for HaveCommonServerCertificate 2016-08-02 13:11:18 <0> linux-t0qd(23365) [Ruby] binary/Yast.cc(ycp_module_call_ycp_function):235 Call HaveCommonServerCertificate 2016-08-02 13:11:18 <1> linux-t0qd(23365) [-e] HaveCommonServerCertificate 2016-08-02 13:11:18 <0> linux-t0qd(23365) [Perl] YCP.cc(YCP_call_SCR):361 Perl is calling builtin SCR::Read 2016-08-02 13:11:18 <0> linux-t0qd(23365) [scr] ScriptingAgent.cc(Read):194 This is ScriptingAgent(0x1391d90)::Read 2016-08-02 13:11:18 <0> linux-t0qd(23365) [scr] ScriptingAgent.cc(Read):195 opt: null 2016-08-02 13:11:18 <0> linux-t0qd(23365) [scr] ScriptingAgent.cc(executeSubagentCommand):589 ScriptingAgent::executeSubagentCommand: Read 2016-08-02 13:11:18 <0> linux-t0qd(23365) [scr] ScriptingAgent.cc(executeSubagentCommand):590 path: .target.size 2016-08-02 13:11:18 <0> linux-t0qd(23365) [scr] ScriptingAgent.cc(executeSubagentCommand):591 arg: "/etc/ssl/certs/YaST-CA.pem" 2016-08-02 13:11:18 <0> linux-t0qd(23365) [scr] ScriptingAgent.cc(executeSubagentCommand):592 opt: null 2016-08-02 13:11:18 <0> linux-t0qd(23365) [agent-system] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):94 evaluate (`Read (.size, "/etc/ssl/certs/YaST-CA.pem")) 2016-08-02 13:11:18 <0> linux-t0qd(23365) [agent-system] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):99 Going to evaluate `Read (.size, "/etc/ssl/certs/YaST-CA.pem") 2016-08-02 13:11:18 <0> linux-t0qd(23365) [agent-system] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):120 After code evaluation: `Read (.size, "/etc/ssl/certs/YaST-CA.pem") 2016-08-02 13:11:18 <0> linux-t0qd(23365) [agent-system] SystemAgent.cc(Read):306 Read (.size) 2016-08-02 13:11:18 <0> linux-t0qd(23365) [Perl] YCP.cc(XS_YCP_call_ycp):228 YCP returned -1 2016-08-02 13:11:18 <0> linux-t0qd(23365) [Perl] YCP.cc(XS_YCP_call_ycp):257 returning a scalar 2016-08-02 13:11:18 <1> linux-t0qd(23365) [-e] YaST-CA.pem does not exists A workaround is to create the following symbolic link ln -s /etc/pki/trust/anchors/YaST-CA.pem /etc/ssl/certs -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 905622] New: Common Server Certificate Location error
by bugzilla_noreply＠novell.com 02 Aug '16

02 Aug '16

http://bugzilla.opensuse.org/show_bug.cgi?id=905622 Bug ID: 905622 Summary: Common Server Certificate Location error Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: srivathsaacharya(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Entered into CA Management, Created a Root CA, Added server Certificate & a client Certificate. Exported as a Common server Certificate. Opened Yast Common server Certificate and confirmed that certificate is exported. Opened Yast Authentication server (open LDAP), Under TLS settings, enabled TLS, Enabled use Common server certificate. I get Error as, Yast-CA.pem is not available. reason, default search location : /usr/share/pki/trust/anchors/YaST-CA.pem Actual saved location, /etc/pki/trust/anchors/Yast-CA.pem Request you to kindly correct this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 988737] New: PolKit blocks NetworkManager from doing anything useful
by bugzilla_noreply＠novell.com 02 Aug '16

02 Aug '16

http://bugzilla.suse.com/show_bug.cgi?id=988737 Bug ID: 988737 Summary: PolKit blocks NetworkManager from doing anything useful Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: mfilka(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I did an upgrade from OS 13.2 to 42.1 When I login to 42.1 and NetworkManager tries to connect to known Wi-Fi I get root authentication request. Moreover, NetworkManager is unable to connect to VPN (Not authorized to control networking) or create new connections. All this worked with no problem in 13.2 polkit-0.113-9.1.x86_64 # pkaction --action-id org.freedesktop.NetworkManager.network-control --verbose org.freedesktop.NetworkManager.network-control: description: Allow control of network connections message: System policy prevents control of network connections vendor: NetworkManager vendor_url: http://www.gnome.org/projects/NetworkManager icon: nm-icon implicit any: auth_admin implicit inactive: yes implicit active: yes What is proper polkit setup for using NetworkManager as a non-root user? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 990374] linuxrc: comparision of buildid vs initrd id makes TW installers only valid for 24 hours
by bugzilla_noreply＠novell.com 02 Aug '16

02 Aug '16

http://bugzilla.suse.com/show_bug.cgi?id=990374 http://bugzilla.suse.com/show_bug.cgi?id=990374#c23 --- Comment #23 from Ludwig Nussel <lnussel(a)suse.com> --- Would give a hint what do do at least. Couldn't linuxrc just enable kexec itself then? There are only two safe choices at this point anyways, abort or give kexec a try. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 934162] qt5 application indicators have a blank icon in xfce4-panel systray
by bugzilla_noreply＠novell.com 02 Aug '16

02 Aug '16

http://bugzilla.opensuse.org/show_bug.cgi?id=934162 Emilio Recio <emrecio(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emrecio(a)gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 955146] New: plasma 5 system tray auto / show / hide settings are not saved across reboots
by bugzilla_noreply＠novell.com 02 Aug '16

02 Aug '16

http://bugzilla.opensuse.org/show_bug.cgi?id=955146 Bug ID: 955146 Summary: plasma 5 system tray auto / show / hide settings are not saved across reboots Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: kde-maintainers(a)suse.de Reporter: farcusnz(a)gmail.com 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/46.0.2490.71 Safari/537.36 Build Identifier: Leap 42.1 running plasma 5.4.2 In system tray set Dropbox icon to always "hide". After system reboot this setting has reset itself to "Auto" Have not yet checked if problem occurs with other icons. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 963924] Icons under xembedsniproxy are extremely tiny
by bugzilla_noreply＠novell.com 02 Aug '16

02 Aug '16

http://bugzilla.opensuse.org/show_bug.cgi?id=963924 Emilio Recio <emrecio(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emrecio(a)gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 990374] linuxrc: comparision of buildid vs initrd id makes TW installers only valid for 24 hours
by bugzilla_noreply＠novell.com 02 Aug '16

02 Aug '16

http://bugzilla.suse.com/show_bug.cgi?id=990374 http://bugzilla.suse.com/show_bug.cgi?id=990374#c22 --- Comment #22 from Steffen Winterfeldt <snwint(a)suse.com> --- And what should it say? 'add kexec=1 boot option and try again'? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 954623] New: fcitx prevents dropbox system tray loading in KDE Plasma 5
by bugzilla_noreply＠novell.com 02 Aug '16

02 Aug '16

http://bugzilla.opensuse.org/show_bug.cgi?id=954623 Bug ID: 954623 Summary: fcitx prevents dropbox system tray loading in KDE Plasma 5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: kde-maintainers(a)suse.de Reporter: farcusnz(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 Build Identifier: openSUSE leap 42.1 installing fcitx as ime prevents the dropbox system tray from loading Reproducible: Always Steps to Reproduce: 1.install dropbox > run > system tray icon for dropbox loads 2. install fcitx/mozc > run > reboot > fcitx icon tray loads, dropbox icon does not. 3.uninstall fcitx > reboot > dropbox systray icon loads -- You are receiving this mail because: You are on the CC list for the bug.

1 17