Hi All,

I’ve made some SAINT scans during PCI Audit preparation. It found one critical problem on my openSUSE 13.2 Server:

vulnerable PHP version: 5.6.1

and the resolution is:

PHP should be upgraded to version 5.4.43 for 5.4.x, or 5.5.27 for 5.5.x, or 5.6.11 for 5.6.x, or higher when
available, or 7.0 Beta 2 dev for development.

I updated my SUSE and the version of PHP is 5.6.1-33. Has SUSE 13.2 PHP 5.6.11 version or higher to update? If so, how can I achieve it?


I was just chatting with someone on Pidgin when I decided to restart Google Chrome. So I simply closed the window and clicked the Chrome icon again.

Nothing – the chrome icon was just jumping for a few seconds.

Loged out, restarted X – no change.
Reboot the machine – no change.

Running from console:



[4908:4908:0826/120714:ERROR:nss_util.cc(856)] After loading Root Certs, loaded==false: NSS error code: -8018
Created new window in existing browser session.

Any idea what might be happening?
(KDE is what I use)


I’m not sure where to put this; I’ve never been able to install 13.2, I’ve wasted a TON of bandwidth (I have to pay for it after a certain amount) and dozens of hours of time; I’ve checked the MD5 sums & have re-downloaded the ISO countless of times, all to no avail. I was using SLED 11.x but couldn’t stomach all the changes I was making to the base system; I felt, I might as well be running Opensuse; however, I could not get it to work. So, after installing Windows, I was hoping to find the next release of Opensuse and found it was 42.1!?!

I must have missed something and I cannot find any clear explanation about 42.1. Will it install similar to 13.2? Personally, I hope not.

Why "42.1" and not "14.1"? If it’s a rolling release, why have any numbers at all? Will there be a charge if it’s based on SLE? If not, how does SuSE see itself surviving (and thus, Opensuse) if I can get the same OS without paying? I paid for 3 years of SLED, so I’m not afraid of paying; however, when I converted a friend’s or customer’s system from Windows to Linux, I normally put them on Opensuse, since it is free and I like its ease-of-use.

The Portal site for Leap really doesn’t contain a whole heck of a lot of information.

I was wondering if anyone has noticed on their install of Tumbleweed that the numbers for the time on the lock screen are not completely visible. Not really noticeable at a glance, but at just at the edges. Example, the Number 2, might have a bit of the top curve missing and the tip of the bottom straight line. It’s kind of hard to explain.

I’ve noticed this as well on the live usb I created on two different machines. One with Intel graphics and the other with an old AMD card. I’ve even tried differently dated .iso (s).

I have not seen this with 13.2 or 13.1.

Does anyone know of a way to fix it?


I have an older system running 11.3 which has been out of use and I now want to upgrade or install to 13.2. /home is a separate mount so i have no problem with a install. This older pc cannot boot from usb or dvd. So I made the network installation CD as show and fired it up. I set the network settings: node ip, gw ip, nanmeserver ips. But when I say install. it pops up the download points ‘download.opensuse.org’ and ‘.13.2/repo/oss’ but It returns a few seconds later saying it cannot find. But I can go there from my browser with no problem. Any suggestions

I recently updated Tumbleweed to the 20150821 snapshot and with the 4.1.6-1 kernel, it hangs up on boot. Here are the errors:


[OK] Started D-Bus System Message Bus.
[41.5593341] Failed to register name: Connection timed out.
[41.578319] Failed to set up API bus: Connection timed out

It stays there hanging for a bit on the above services, then hangs up permanently at:


A start job is running for WPA Supplicant daemon.

At this point I have to hit the reset button, as nothing else short of cutting the power will allow me to reboot. The strange thing, is that after it hangs up as I wrote above, my PC will then boot normally after pressing the reset button on my case. Then, when restarting from within KDE, it will hang up again. The behavior is very strange. I went back to the 4.1.5-1 kernel and things are back to normal.