March 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Kmail, conflict resolution
by Constant Brouerius van Nidek 01 Mar '13

01 Mar '13

Using kmail for years and are still a more or less happy user. One thing I do not like is the pop-up telling me that there is a "Conflict Resolution" to attend. This pop-up shows up at the most unexpected times and is not always visible. Does somebody know how to let this thingy do its job without human interference. As I over the time never found differences between the left and right one I standard pick the left one. If that could be done automatically it would be of great help. -- Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.2 (i586) Kernel: 3.4.28-2.20-default KDE Development Platform: 4.10.00 "release 550" 19:55pm up 8:13, 3 users, load average: 0.75, 0.48, 0.68 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Help with Static Routes
by Chris Arnold 01 Mar '13

01 Mar '13

I know what you all are going to say, "this is not the SLES forum" but i have meet a dead-end at the SLES11 forum so i thought i would ask here since opensuse and SLES are suse based. I have a SLES11 SP2 server with multi-nic's and i was having a problem described here: http://www.novell.com/support/kb/doc.php?id=7000318 So i followed this TID and everything is working the way i expect it to work. The problem is, these entries/routes do not survive a reboot and i have to manually type them in again. So is there any way to have these routes static? In other Linux distro's, you put these entries in a script located in /etc/sysconfig/networkXXX/XXXX. Where does one put static routes in a suse based OS? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] opensuse 12.3 RC | starting LSB... and freeze
by Luis González 01 Mar '13

01 Mar '13

Hello, I'm installing the opensuse 12.3 RC and I noticed an issue before the installation finished, and after reviewed several times I realized the error (laptop freeze completely) occurred when starting LSB. /var/log/messages not shown relevant info boot.log said Failed to start Network Manager, and of course I do no have network devices. When a launch yast and go to Network Devices, the error occurred again detecting devices... systemctl status NetworkManager.service said Active: failed status = 1/FAILURE What can I do to fix this issue? Can I look in other log files? Any suggestions? thank you! -- Luis González @ GMAIL -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1