[opensuse-kde] Qt5 → libproxy1(-config-kde4) → Qt4 = segfault
Hello! Recently I've maid Qt5 build of leechcraft package and found interesting runtime issue. Leechcraft loads Qt5Network library (linking) that loads libproxy1 (linking) that loads libproxy1-config-kde4 if it is installed (plugin) that loads kde4 libs and finally Qt4 libs that leads to a segmentation fault. Fuh =) Any ideas? Does every Qt5Network linked package have to conflict against libproxy1-config-kde4 package? -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 27 of February 2015 16:46:03 Dmitriy Perlow wrote:
Hello!
Recently I've maid Qt5 build of leechcraft package and found interesting runtime issue. Leechcraft loads Qt5Network library (linking) that loads libproxy1 (linking) that loads libproxy1-config-kde4 if it is installed (plugin) that loads kde4 libs and finally Qt4 libs that leads to a segmentation fault. Fuh =) Any ideas? Does every Qt5Network linked package have to conflict against libproxy1-config-kde4 package?
See https://code.google.com/p/libproxy/issues/detail?id=197 and https://bugzilla.novell.com/show_bug.cgi?id=866692 Our YaST people have workarounded this by injecting empty PX_MODULE_PATH into enviroment: https://github.com/yast/yast-installation/pull/242/files Cheers, Hrvoje
šumski
On Friday 27 of February 2015 16:46:03 Dmitriy Perlow wrote:
Hello!
Recently I've maid Qt5 build of leechcraft package and found interesting runtime issue. Leechcraft loads Qt5Network library (linking) that loads libproxy1 (linking) that loads libproxy1-config-kde4 if it is installed (plugin) that loads kde4 libs and finally Qt4 libs that leads to a segmentation fault. Fuh =) Any ideas? Does every Qt5Network linked package have to conflict against libproxy1-config-kde4 package?
See https://code.google.com/p/libproxy/issues/detail?id=197 and https://bugzilla.novell.com/show_bug.cgi?id=866692 Our YaST people have workarounded this by injecting empty PX_MODULE_PATH into enviroment: https://github.com/yast/yast-installation/pull/242/files
Nice, thanks! Anyway imho it would be fine to add a conflict to the Qt5Network package. -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (2)
-
Dmitriy Perlow -
šumski