https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c34
--- Comment #34 from Wolfgang Bauer
I had a look at the libproxy documentation.
Maybe YaST should just blacklist the config_kde module? As I said, I think it doesn't make sense anyway as YaST runs as root.
See http://code.google.com/p/libproxy/wiki/HowTo . I.e. just set the environment variable PX_MODULE_BLACKLIST=config_kde.
Haven't tried it yet, though.
I have tried it now, but unfortunately it doesn't help. The module is loaded (and causes the crash) even when it is not used. Setting the envvar PX_MODULE_PATH (so that the config_kde4 module cannot be found) would "fix" the crash though, so maybe this would be a possible workaround? I only have those modules on my 13.1 system anyway: config_gnome3.so network_networkmanager.so config_kde4.so pacrunner_webkit.so I think none of those make sense with YaST. gnome3 and kde4 not because YaST runs as root as already said, so doesn't respect the user settings anyway. And I just tried on 13.1 to verify: YaST DOES NOT respect my user's KDE settings, even with libproxy1-config-kde4 installed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.