Tag Info

New answers tagged

0

Why would you need that? I would recommend to mask the wicked service and rely on NetworkManager: systemctl mask wicked systemctl mask wickedd Then, enable NetworkManager systemctl start NetworkManager


0

Go to KDE System Settings > Application Appearence > Colours, on the Scheme tab select openSUSE and click in Save Scheme and give a new name, such as "openSUSE-Green". Now select "openSUSE-Green" on the list and click on the tab Colours, there you need to change the colour of the following items, put the according colour in the HTML code area, so just ...


0

I believe this can be fixed by setting CONFIG_FW_LOADER_USER_HELPER=n and recompiling the kernel. Later kernels have this set to n by default. If this is not an option for you, try adding to /etc/udev/rules.d/50-firmware: SUBSYSTEM=="firmware", ACTION=="add", ATTR{loading}="-1" (create the file if it does not exist) and reboot. It helped for my case. ...


0

openSUSE 11.2 is not supported any more, see https://en.opensuse.org/Lifetime Using it is not secure as security updates are not available anymore. I'd suggest you to upgrade to current version 13.2.


0

The Message of the Day file (/etc/motd) had the strange text in there. I wonder what put that there. I deleted the MOTD file and now my sessions no longer begin with the strange text.


0

I'd turn up the logging level for the SSH Daemon via the configuration file, /etc/ssh/sshd_config. Typically this section of the configuration file: # Logging # obsoletes QuietMode and FascistLogging #SyslogFacility AUTH SyslogFacility AUTHPRIV #LogLevel INFO Uncomment the LogLevel section and restart SSH service. This should show you where those messages ...


-1

you can use zypper se mysql And you will get all info with 'mysql', then you can find out what you really want!


1

First off, OpenSuSE 11.2 has been EOL'd so you probably want to upgrade. However, from the man page you can change the root directory with -R /path/to/new/root. This means if you do the following: zypper in foo And foo lives in /bin/ then: zypper -R /usr/local/ in foo Will put foo in /usr/local/bin/


1

Try to run systemd-analyze critical-chain. I think the output is easier to read than the log. Well, it might just confirm that wicked is the culprit. I have no experience with wicked yet, but I would try to start it under strace to see where it hangs/times out or to run tcpdump in parallel to see what it tries to do on the net. Edit: Oops, I had missed your ...


0

In case anybody has the same issue - you might want to checkout if you've got glibc-locale-32bit and perl-Text-Iconv installed on your machine. The issue has nothing to do with qt as some people have suggested on other topics on the net.



Top 50 recent answers are included