August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 940924] VUL-0: CVE-2015-5957: remind: Buffer overflow in DumpSysVar
by bugzilla_noreply＠novell.com 07 Aug '15

07 Aug '15

http://bugzilla.novell.com/show_bug.cgi?id=940924 http://bugzilla.novell.com/show_bug.cgi?id=940924#c1 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium --- Comment #1 from Swamp Workflow Management <swamp(a)suse.de> --- bugbot adjusting priority -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 931377] Virtualbox Integration not working correctly with 20150515 NET iso and after install
by bugzilla_noreply＠novell.com 07 Aug '15

07 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=931377 http://bugzilla.suse.com/show_bug.cgi?id=931377#c8 Larry Finger <Larry.Finger(a)lwfinger.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jon(a)grossart.net, | |Larry.Finger(a)lwfinger.net Flags| |needinfo?(jon(a)grossart.net) --- Comment #8 from Larry Finger <Larry.Finger(a)lwfinger.net> --- I will be the maintainer of the VirtualBox components in the near future. I do not have any Windows 8.1 installations to act as host. I do have Windows 7, but it is 32 bit. I'm not sure if that makes a difference. I installed the Aug. 7 snapshot of the Factory NET ISO in a new VM using VB 5.0.0 with 3D acceleration enabled. All defaults were taken in the KDE installation. Installation was normal. Upon rebooting, there was a very long time before the GRUB menu appeared. The VM appeared to be booting and ran for some time, then crashed with an illegal memory reference. I then turned off 3D Acceleration, and the VM booted normally. The process was slow, but that may be due to my host system (Core Duo 2.53 GHz) and that I gave the VM a single CPU and 1GB RAM. At this point, I installed the Guest Additions from the ISO image. After that, the system booted OK with 3D Acceleration turned on. Does this behavior match what you see? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 940554] New: *PROXY* No Clear way to add proxy during install
by bugzilla_noreply＠novell.com 07 Aug '15

07 Aug '15

http://bugzilla.opensuse.org/show_bug.cgi?id=940554 Bug ID: 940554 Summary: *PROXY* No Clear way to add proxy during install Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: 64bit OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: wgre0111(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 642895 --> http://bugzilla.opensuse.org/attachment.cgi?id=642895&action=edit Picture of the error During Install of Leap 42.1 I clicked a option add Online Repositories during the install. After moving forward I receive the attached screenshot that advises: Unable to download list of repositories or no repositories defined This occurs because i'm behind a proxy.. behind the popup i see what looks like a way to potentially add proxy options, but there is no way to get to it... Having the ability to setup network connection/proxy information BEFORE a process attempts to utilize the internet would be a nice feature? or giving the option to validate network/proxy settings after a failure like my attachment would be awesome. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 940273] libpoppler-devel: missing runtime dependency
by bugzilla_noreply＠novell.com 07 Aug '15

07 Aug '15

http://bugzilla.novell.com/show_bug.cgi?id=940273 http://bugzilla.novell.com/show_bug.cgi?id=940273#c7 --- Comment #7 from Kyrill Detinov <lazy.kent(a)opensuse.org> --- (In reply to Petr Gajdos from comment #5) > 12.3? This is out of maintenance for half a year, isn't it? > > 13.1 and 13.2 and factory seems not to be affected as far as I can see. > Petr, ignore 12.3 and 13.1. I've cloned the bug and forgot to remove the outdated versions. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 940731] New: osc doesn't identify maintenance-requests to supersede
by bugzilla_noreply＠novell.com 07 Aug '15

07 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=940731 Bug ID: 940731 Summary: osc doesn't identify maintenance-requests to supersede Classification: Internal Novell Products Product: openSUSE Build Service Version: master Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: osc Assignee: adrian(a)suse.com Reporter: lchiquitto(a)suse.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- When I submit multiple submit-requests against the same target project/package, osc will identify the previous SR and ask if I want to supersede it. With maintenance-requests this is not happening. Is it possible to implement the same feature for this type of requests? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 940857] digikam crashes in keyword editor
by bugzilla_noreply＠novell.com 07 Aug '15

07 Aug '15

http://bugzilla.novell.com/show_bug.cgi?id=940857 http://bugzilla.novell.com/show_bug.cgi?id=940857#c5 --- Comment #5 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (940857) was mentioned in https://build.opensuse.org/request/show/321265 13.2 / digikam -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 938958] Yast Software Management (sw_single) crashes when not on primary display
by bugzilla_noreply＠novell.com 07 Aug '15

07 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=938958 http://bugzilla.suse.com/show_bug.cgi?id=938958#c6 --- Comment #6 from Martin Vidner <mvidner(a)suse.com> --- I tried to reproduce it but so far haven't succeeded on my two-screen workstation running 13.2, or using this DISPLAY from a Tumbleweed installed in May, sorry. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 938951] New: YaST installer tries to enable ntp even if it is not installed.
by bugzilla_noreply＠novell.com 07 Aug '15

07 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=938951 Bug ID: 938951 Summary: YaST installer tries to enable ntp even if it is not installed. Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: cwh(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 641569 --> http://bugzilla.suse.com/attachment.cgi?id=641569&action=edit NTP config error When enabling the option not to install recommended packages, an error pops up at the end of the package installation: Cannot adjust NTP service. (See screenshot) Checking t he logs shows, that ntp is not installed although in the installation workflow the enablement of NTP is a hardcoded step in the workflow. Since a user might want to not install NTP we should consider to check if ntp is there before we try to enable it. OR Require NTP to be installed even in the minimal pattern. A requirement for the yast2 package might not be sufficient since maybe not even yast2 is installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 940274] OneClickInstallCLI showing only empy ncurses window
by bugzilla_noreply＠novell.com 07 Aug '15

07 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=940274 http://bugzilla.suse.com/show_bug.cgi?id=940274#c2 Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |igonzalezsosa(a)suse.com --- Comment #2 from Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> --- It looks like using latest versions (from YaST:Head repository) the empty ncurses window does not appear. However, when you have to accept a PGP key, for example, a ncurses dialog is shown. Is it intentional? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 940357] RSH-Server Daemon Fails With Great Frequency
by bugzilla_noreply＠novell.com 07 Aug '15

07 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=940357 http://bugzilla.suse.com/show_bug.cgi?id=940357#c2 --- Comment #2 from David Richards <drichard(a)largo.com> --- Understood completely, and I have more information. I think that this software is really absolutely broken and possibly should be considered for removal. I built an Ubuntu server to match our OpenSuse server and enabled RSH and now Ubuntu is doing the same thing. It works initially, but after a good while of may users hammering it with RSH requests, it hangs and stops accepting connections. Here is what else I found out in my testing: I ran xinetd in the foreground and when it fails, the RSH request is not even getting to xinetd at all. I enabled pam debugging for "rsh" and then touched pam_debug and was able to get logging information. When the requests are working, you can clearly see all of the interaction with pam. When it stops working, pam completely stops logging....these requests are not even getting anywhere near PAM. Ubuntu offers rsh-redone-server and I installed that package for testing and it did the same thing. When RSH stops accepting connections, rlogin and ssh continue to work. So it appears not be some kind of load or user threshold. I tried bumping up the limits.conf file to allow more maxusers and maxsysusers, neither of which helped. I tried kicking off some users when it stopped working, and it didn't allow more connections for a while, so that wasn't the issue. When it fails, rsh requests are being accepted from other servers, but not from one particular server. So it's almost like there might be a throttle or tuning parameter that is not exposed anywhere and we are just hitting the defaults. I considered looking at the source code itself. Previously this would be tuned in the old xinetd.d scripts for each service. So I really was at the end of the road with this thing, It's not xinetd nor pam that is causing this issue...but I don't see any tuning files beyond that. RSH is a child of xinetd, and it's just not getting that far. I moved our infrastructure over to SSH in this use case, because it's taking so long to get this working. If you want to explore resolving this as a back burner issue, I would be happy to help. But it might be time just to retire this package, it's really not working very well. -- You are receiving this mail because: You are on the CC list for the bug.

1 0