June 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 934256] New: Passwords maintained by Filezilla are easily recovered in some cases
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=934256 Bug ID: 934256 Summary: Passwords maintained by Filezilla are easily recovered in some cases Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: Greg.Freemyer(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm testing with LaZagne: http://www.kitploit.com/2015/02/the-lazagne-project-recover-most-common.html Or in OBS @ home:gregfreemyer:Tools-for-forensic-boot-cd LaZagne Running LaZagne under my normal user account recovered one filezilla stored passwd. The amount of time taken was near instantaneous so I believe the password was simply decoded, not cracked in the sense of "John the ripper". The password was associated with a SFTP account, so it is a password I consider needing to be kept securely. I don't know if Filezilla simply handles passwords poorly or if it can be compiled differently to store passwords securely. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 918028] New: no Grub Legacy shell history
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=918028 Bug ID: 918028 Summary: no Grub Legacy shell history Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- To reproduce: 1-login root on tty[1-6] on en_US installation 2-grub 3-find /boot/grub/stage1 4-keystroke <UP> Actual behavior: 1-^[[A appears at prompt Expected behavior: 1-find /boot/grub/stage1 appears at prompt Comments: 1-Shell cmdline history works as expected in 13.1, as in all previous openSUSE releases. 2-I recognized this problem many months ago, maybe as much as a year ago, but only just surmised it was almost certainly 13.2 and up Grub Legacy post-0.97-194.1.2 itself rather than having anything to do with kernel, framebuffer configuration, video mode, or files contained in target /boot/grub/. "Downgrading" to 13.1's 0.97-194.1.2 fixes 13.2 and Tumbleweed. 3-Nearly all my Grub stanzas include "splash=verbose vga=791 video=1024x768@60 3 " on cmdline. 4-All my openSUSE installations are on multiboot hardware (no VMs), with keyboards on PS/2 ports. 5-Plymouth is not installed in any of my openSUSE installations. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 981271] New: KTTSMgr cannot use festival 2.4 in 13.1 or 13.2 or 42.1
by bugzilla_noreply＠novell.com 19 Feb '21

19 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=981271 Bug ID: 981271 Summary: KTTSMgr cannot use festival 2.4 in 13.1 or 13.2 or 42.1 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 URL: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2657 OS: Other Status: NEW Keywords: accessibility Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: anixx(a)opensuse.org Found By: --- Blocker: --- To reproduce: 1.ensure sound system works reliably 2.install festival and kdeaccessibility3 or trinity-tdeaccessibility from standard repos 3.enable festival with chkconfig (no systemd service for it exists) 4.open a KDE3 or TDE session 5.open KTTSMgr 6.try to add or edit a talker (talker tab) Actual behavior: 1.voice query fails 2.Enable on General tab cannot be selected 3.TTS cannot produce sound Expected behavior: 1.voice query succeeds 2.enabling on General tab is possible 3.TTS works as expected (e.g. speak clipboard) Notes: 1-KDE3's KTTSMgr on 13.1 on host Easystreet made sound until most recent updating, which replaced festival 2.1 with 2.4. Reverting to festival 2.1 from OSS repo restored sound. 2.KDE3' KTTSMgr on 13.2 had never been made to find voices or make sound on host Easystreet. I was only able to make it find voices and make sound after replacing its installed festival 2.4 from KDE3 repo with 2.1 from OSS repo. 3.TDE's KTTSMgr on 42.1 on hosts Easystreet and gx62b would not find voices or make sound until I replaced their festival 2.4 with the 2.1 version from 13.2's OSS repo. 4.TDE's KTTSMgr on Debian stretch on host Easystreet works as expected with its own festival 2.4. Yet to do is figure out why same OS/KTTSMgr/festival on host big41 does not output sound, though it does claim to find voices and appear fully configured to output sound, and other apps do output sound. 5.mailing list thread: http://trinity-users.pearsoncomputing.net/?0::10248 -- You are receiving this mail because: You are on the CC list for the bug.

2 22

[Bug 912059] New: networkmanager plasmoid shows nearly everybody connected (although it seems that only one wpa2 is correctly connected
by bugzilla_noreply＠novell.com 11 Feb '21

11 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=912059 Bug ID: 912059 Summary: networkmanager plasmoid shows nearly everybody connected (although it seems that only one wpa2 is correctly connected Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 618858 --> http://bugzilla.opensuse.org/attachment.cgi?id=618858&action=edit wrong connection info of networkmanager plugin Create several users. Create in user A a connection with wpa2 encryption, choose: only this user can connect. Save and connect. Look at the list of the plasmoid: it shows all available wlan as not connected and the one you created as connected. Now change to user B or C. As you are still up with user A and you are connected, now in user B or C it should show the same as in user A. Only it should not be possible to end simply this connection or to start it. But you will be able to use it. What happens: in B or C respectively, the list of all available stations shows up as "connected". So in theory you are connected to all wireless of the area. All? No, some do show up correctly as "not connected" but the list here is so long that I can show only the beginning of the screen-shot. The output of ifconfig and netstat seem normal. So this seems to be more an apparent than a real bug. I join a screenshot. What should have done the program: show the correct connection information. Screen-shot: the only "real" connection iw the one with the button disconnect. The other ssids are from the neighborhood. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 980313] New: /usr/lib/zypp/plugins/commit/susemanager should be moved to susemanager related package and not be part of base salt-minion
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=980313 Bug ID: 980313 Summary: /usr/lib/zypp/plugins/commit/susemanager should be moved to susemanager related package and not be part of base salt-minion Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- seen with salt-minion-2015.8.8-68.1.x86_64 from systemsmanagement:saltstack the salt setup on the machine was turned off atm and this noticably slows down all zypp operations. if this plugin is mostly for susemanager it shouldnt be part of the normal salt-minion package. if it is meant to be used with normal salt, i would recommend renaming it. -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 978833] New: systemsmanagement:saltstack/salt broken pkgrepo.managed priority atribute
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=978833 Bug ID: 978833 Summary: systemsmanagement:saltstack/salt broken pkgrepo.managed priority atribute Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bmaryniuk(a)suse.com Reporter: tchatzimichos(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- pkgrepo.managed priority attribute shows the following error: Failed to configure repo 'NON_Public:Infrastructure': zypper command failed: Invalid priority ''102''. Use a positive integer number. The greater the number, the lower the priority. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 980577] New: "cobbler get-loaders" doesn't resolve www.clobberd.org
by bugzilla_noreply＠novell.com 14 Jan '21

14 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=980577 Bug ID: 980577 Summary: "cobbler get-loaders" doesn't resolve www.clobberd.org Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pablo.suarezhernandez(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ferruja:~ # cobbler get-loaders task started: 2016-05-18_154111_get_loaders task started (id=Download Bootloader Content, time=Wed May 18 15:41:11 2016) downloading http://www.cobblerd.org/loaders/README to /var/lib/cobbler/loaders/README Exception occured: <class 'urlgrabber.grabber.URLGrabError'> Exception value: [Errno 14] PYCURL ERROR 6 - "Could not resolve host: www.cobblerd.org" Exception Info: File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line 87, in run rc = self._run(self) File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line 181, in runner return self.remote.api.dlcontent(self.options.get("force",False), self.logger) File "/usr/lib/python2.7/site-packages/cobbler/api.py", line 751, in dlcontent return grabber.run(force) File "/usr/lib/python2.7/site-packages/cobbler/action_dlcontent.py", line 72, in run urlgrabber.grabber.urlgrab(src, filename=dst, proxies=proxies) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 618, in urlgrab return default_grabber.urlgrab(url, filename, **kwargs) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 982, in urlgrab return self._retry(opts, retryfunc, url, filename) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 886, in _retry r = apply(func, (opts,) + args, {}) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 968, in retryfunc fo = PyCurlFileObject(url, filename, opts) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1063, in __init__ self._do_open() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1352, in _do_open self._do_grab() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1482, in _do_grab self._do_perform() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1339, in _do_perform raise err !!! TASK FAILED !!! -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 956264] New: cobbler_web apache config uses old syntax
by bugzilla_noreply＠novell.com 14 Jan '21

14 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=956264 Bug ID: 956264 Summary: cobbler_web apache config uses old syntax Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: osynge(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Please set up cobbler and cobbler_web to use new syntax. Require all granted instead of Order allow,deny Allow from all See http://httpd.apache.org/docs/2.4/upgrading.html. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 956153] New: Software Update Error "License Agreement Failed" But A License Agreement Is Never Presented
by bugzilla_noreply＠novell.com 08 Jan '21

08 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=956153 Bug ID: 956153 Summary: Software Update Error "License Agreement Failed" But A License Agreement Is Never Presented Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bill_wayson(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 656868 --> http://bugzilla.opensuse.org/attachment.cgi?id=656868&action=edit Zip file with error message screenshot, zypper.log, and pk_backend_zypp files On Saturday morning (11/21/2015 PST) I am presented with 246 updates by the software updater. I press the "Install Updates" button, and the update begins. But it quickly stops with a message dialog "Update Error The license agreement failed. The license agreement was not agreed to. To use this software you have to accept the license." The problems are that a license agreement dialog is never presented, and there is no indication of which of the 246 updates require the license agreement (so that I can, say, deselect it). I have attached a zip file that contains a screenshot of the message along with the zypper.log and pk_backend_zypp files. The latter file appears to be the log updated by the software updater. My tumbleweed is currently at 20151113. I hope I chose the correct component. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 954603] New: Leap lacks tomcat
by bugzilla_noreply＠novell.com 07 Jan '21

07 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=954603 Bug ID: 954603 Summary: Leap lacks tomcat Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Leap lacks tomcat as it didn't build. I will submit fixed dbcp that should go later as maint-update to SLE12 directly and for tomcat we can grab 1:1 the SLE-12:SP1 counterpart. -- You are receiving this mail because: You are on the CC list for the bug.

2 11