December 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 908597] New: freshplayerplugin is unsecure, also the newest version!
by bugzilla_noreply＠novell.com 07 Dec '14

07 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=908597 Bug ID: 908597 Summary: freshplayerplugin is unsecure, also the newest version! Classification: openSUSE Product: openSUSE Factory Version: 201411* Hardware: x86-64 OS: SUSE Other Status: NEW Keywords: security_vulnerability Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: w.pelser(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed freshplayerplugin from obs://build.opensuse.org/home:scalpel4 and chromium-pepper-flash from obs://build.opensuse.org/home:mik34020. Then I tested with Firefox 34.0.5 in "extras" my plugin, wheter it is actual or not. The result was, that the detected version of shockwaveflash was old and unsecure! "version": "11.9.900.152", in /usr/share/chromium/PepperFlash/manifest.json. So I extracted from google-chrome-stable-39.0.2171.71-1.x86_64.rpm to /opt/google/chrome/Pepperflash the newest version and kopied it into /usr/lib64/chromium. Then I tested again with Firefox 34.0.5 in "extras" my plugin, wheter it is actual or not. The result was again, that the detected version of shockwaveflash was old and unsecure! "version": "11.9.900.152". But in /usr/share/chromium/PepperFlash/manifest.json was now version "version": "15.0.0.239". The Test-side run by adobe showed that the newest version of shockwave-flas was installed. So I tried to compile a new libfreshwrapper-pepperflash.so with git clone https://github.com/i-rinat/freshplayerplugin.git The compilation was easy and brought a new plugin and i copied it into /usr/lib64/browser-plugins. Then I tested again with Firefox 34.0.5 in "extras" my plugin, wheter they are actual or not. The result now was "15.0.0.239"! If there should be an alternative to adobe's old linux-flashplayer it should be a secure one! I'm interested in Your reaction. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 907907] Selecting "Only root" to define KDM behavior for restart/shutdown does not work
by bugzilla_noreply＠novell.com 06 Dec '14

06 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=907907 --- Comment #8 from Alberto Passalacqua <apcfd(a)outlook.com> --- @Wolfgang: It seems to work fine using KDE Control Center. Thank you! I don't mind if I cannot insert the password. I just want to prevent others from rebooting/shutting down. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 908674] Fan does not follow temperature after resuming from suspend to RAM (Thinkpad T410)
by bugzilla_noreply＠novell.com 06 Dec '14

06 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=908674 --- Comment #9 from Duncan Mac-Vicar <dmacvicar(a)suse.com> --- Bah!, now the fan works with 3.17.1 after resume. The upstream bug says, it depends on when the values are restored. May be is not depending on the version but something else. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 908674] Fan does not follow temperature after resuming from suspend to RAM (Thinkpad T410)
by bugzilla_noreply＠novell.com 06 Dec '14

06 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=908674 Duncan Mac-Vicar <dmacvicar(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dmacvicar(a)suse.co | |m) | --- Comment #8 from Duncan Mac-Vicar <dmacvicar(a)suse.com> --- With openSUSE 13.2 kernel (3.16.6) I can not even resume (black screen). I tried the new 3.17.4 available for Tumbleweed and the fan seems to work fine. I hitted https://bugzilla.suse.com/show_bug.cgi?id=908675 when resuming so X11 crashed and I went back to the login screen, but the fan seems to work ok. I will boot again with 3.17.2 to double check the fan breaks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 907391] Yast cannot set Finnish keyboard layout for console
by bugzilla_noreply＠novell.com 06 Dec '14

06 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=907391 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:3295:low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903514] wrong text in drbd.de.po
by bugzilla_noreply＠novell.com 06 Dec '14

06 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=903514 --- Comment #9 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2014:1578-1: An update that has four recommended fixes can now be installed. Category: recommended (moderate) Bug References: 898448,901554,901833,903514 CVE References: Sources used: SUSE Linux Enterprise High Availability 12 (src): yast2-drbd-3.1.9-8.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 908707] New: Education/Mnemosyne: Bug version 2.3 from education repo
by bugzilla_noreply＠novell.com 06 Dec '14

06 Dec '14

http://bugzilla.opensuse.org/show_bug.cgi?id=908707 Bug ID: 908707 Summary: Education/Mnemosyne: Bug version 2.3 from education repo Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: lrupp(a)suse.com Reporter: stakanov(a)freenet.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- the program terminates with unexpected error It calls to deliver this error message: Traceback (innermost last): File "/usr/bin/mnemosyne", line 191, in <module> debug_file=options.debug_file) File "/usr/lib/python2.7/site-packages/mnemosyne/libmnemosyne/__init__.py", line 172, in initialise self.register_components() File "/usr/lib/python2.7/site-packages/mnemosyne/libmnemosyne/__init__.py", line 237, in register_components exec("from %s import %s" % (module_name, class_name)) File "<string>", line 1, in <module> File "/usr/lib/python2.7/site-packages/mnemosyne/pyqt_ui/statistics_wdgts_plotting.py", line 9, in <module> from matplotlib.backends.backend_qt4agg import FigureCanvasQTAgg as FigureCanvas ImportError: No module named backend_qt4agg -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 905952] yast2-firstboot root-password dialog only shown after triggering error message
by bugzilla_noreply＠novell.com 06 Dec '14

06 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=905952 --- Comment #15 from Josua Mayer <josua.m(a)t-online.de> --- As on using the qt gui, what do I have to do to make that happen? install a specific package? change some configuration? All I currently do is touch /var/lib/YaST2/reconfig_system, and it uses textmode yast. Xorg works fine on the device, so the qt ui should just work. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 897774] [Kernel:HEAD] btrfs issue (kernel crash) changes root filesystem to ro mount
by bugzilla_noreply＠novell.com 06 Dec '14

06 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=897774 --- Comment #6 from Johannes Obermayr <johannesobermayr(a)gmx.de> --- # rpm -q kernel-desktop kernel-desktop-3.18.rc7-2.1.g088d59b.x86_64 # rpm -q btrfsprogs btrfsprogs-3.17.2-1.1.x86_64 # btrfsck --repair /dev/sdc2 ## not /dev/sdb2 since I added another device ... enabling repair mode Error: could not find extent items for root 256 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 898882] 13.2B1: Automount of USB devices fails under KDE4
by bugzilla_noreply＠novell.com 06 Dec '14

06 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=898882 Volker Barth <novell(a)nethub-barth.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(novell@nethub-bar | |th.de) | --- Comment #12 from Volker Barth <novell(a)nethub-barth.de> --- Mounting did work for the USB stick and it did not work for the USB HDD. So it's no improvement. See my description in #8 > Yes, it is always the same two devices which do not work properly (USB > stick, takes about a minute to be available), respectively do not work at > all (USB HDD). The behaviour is the same if I pass the delay_use parameter. The USB stick still takes a minute until it is mounted, the USB HDD gets not mounted at all. -- You are receiving this mail because: You are on the CC list for the bug.

1 0