https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c2 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|wbauer@tmo.at | --- Comment #2 from Wolfgang Bauer 2014-03-04 12:12:19 UTC --- Created an attachment (id=580859) --> (http://bugzilla.novell.com/attachment.cgi?id=580859) full YaST logs Sorry, I thought the y2log was sufficient, as it contained the backtrace. Here is the full log as created by save_y2logs. I renamed the /var/log/YaST2 directory before running "yast2 sw_single" and reproducing the crash. Hope that helps. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c4 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |NEEDINFO CC| |dimstar@opensuse.org InfoProvider| |wbauer@tmo.at --- Comment #4 from Martin Vidner 2014-03-04 16:24:50 CET --- Please try the action also in the ncurses UI (/sbin/yast sw_single) or with zypper. Most likely Qt5 is not involved. Instead, libproxy seems to be: === 2014-03-04 12:34:21 +0100 === YaST got signal 11 at YCP file /usr/share/YaST2/modules/SlideShow.rb:385 Liberating suppressed debugging messages: End of suppressed debugging messages Backtrace: (use c++filt to demangle) /usr/lib/liby2.so.4(signal_log_backtrace()+0x29)[0xb75d4b19] /usr/lib/liby2.so.4(signal_handler(int)+0x17f)[0xb75d4d3f] linux-gate.so.1(__kernel_sigreturn+0x0)[0xb777c400] /usr/lib/libkdecore.so.5(+0x73dab)[0xac4b7dab] /lib/ld-linux.so.2(+0xf22e)[0xb778c22e] /lib/ld-linux.so.2(+0xf324)[0xb778c324] /lib/ld-linux.so.2(+0x1332e)[0xb779032e] /lib/ld-linux.so.2(+0xf0d6)[0xb778c0d6] /lib/ld-linux.so.2(+0x12b24)[0xb778fb24] /lib/libdl.so.2(+0xcbc)[0xb74e5cbc] /lib/ld-linux.so.2(+0xf0d6)[0xb778c0d6] /lib/libdl.so.2(+0x137c)[0xb74e637c] /lib/libdl.so.2(dlopen+0x41)[0xb74e5d71] /usr/lib/libmodman.so.1(libmodman::module_manager::load_file(std::basic_string, bool)+0x313)[0xb5ca2603] /usr/lib/libmodman.so.1(libmodman::module_manager::load_dir(std::basic_string, bool)+0x274)[0xb5ca2ac4] /usr/lib/libproxy.so.1(+0xabaf)[0xb5f0bbaf] /usr/lib/libproxy.so.1(px_proxy_factory_new+0x27)[0xb5f0c6e7] /usr/lib/libzypp.so.1416(zypp::media::ProxyInfoLibproxy::ProxyInfoLibproxy()+0x2ae)[0xb65ae65e] -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c6 --- Comment #6 from Dominique Leuenberger 2014-03-04 15:47:35 UTC --- I assume this is a result of Qt4 and Qt5 ending up on the same process space and having symbol clashes... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c8 --- Comment #8 from Robert Kaiser 2014-03-04 17:06:47 UTC --- I didn't have libqdialogsolver1 installed in the first place. My crash happens when starting to analyze/update the repos, so I only see the window for a second or so and never see the actual package list etc. UI in the window. But what I'm seeing might be different than the original comment #0 here: Run command: /sbin/yast2 sw_single & YaST got signal 11 at YCP file /usr/share/YaST2/modules/PackageCallbacks.rb:2159/sbin/yast2: line 429: 10430 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c10 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|wbauer@tmo.at | --- Comment #10 from Wolfgang Bauer 2014-03-04 18:02:03 UTC --- (In reply to comment #4)

Please try the action also in the ncurses UI (/sbin/yast sw_single) or with zypper.

I cannot reproduce the crash in the ncurses UI. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c12 --- Comment #12 from Hrvoje Senjan 2014-03-04 18:37:20 UTC --- And it is reported upstream even, https://code.google.com/p/libproxy/issues/detail?id=197 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c14 --- Comment #14 from Robert Kaiser 2014-03-05 13:39:03 UTC --- Just FTR, I can confirm that it works again for me after uninstalling libproxy1-config-kde4. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c16 Alin M Elena changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alinm.elena@gmail.com --- Comment #16 from Alin M Elena 2014-03-18 11:38:28 UTC --- *** Bug 868894 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=868894 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c18 dale ritchey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mergan14846@gmail.com --- Comment #18 from dale ritchey 2014-03-22 10:51:55 UTC --- (In reply to comment #17)

Just been pointed to this bug report and agree that removing libproxy1-config-kde4 solves the problem but, sadly, only once. Problem is that YaST insists on re-installing everything I've deleted, including the above module, as soon as I use it again. This is only true for the GUI version; it doesn't happen when I run YaST in the console.

Taboo libproxy1-config-kde4 -- 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.

I have never had libproxy1-config-kde4 installed. And yast2 sw_single crashes any way. Do you have libqdialogsolver1 installed? That causes yast2 sw_single to crash as well, because it also (still) uses

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c20 --- Comment #20 from Wolfgang Bauer 2014-03-22 13:38:34 UTC --- (In reply to comment #19) libqt4. See bnc#866622 as mentioned in comment#0. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c22 --- Comment #22 from Kyrill Detinov 2014-03-25 16:39:19 MSK --- (In reply to comment #20)

Do you have libqdialogsolver1 installed? That causes yast2 sw_single to crash as well, because it also (still) uses libqt4.

After removing libqdialogsolver1 yast2 sw_single doesn't crash. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c24 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ingesvensson@bredband.net --- Comment #24 from Josef Reidinger 2014-05-05 09:11:33 UTC --- *** Bug 876245 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=876245 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c26 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |GeoBaltz@gmail.com --- Comment #26 from Martin Vidner 2014-05-15 15:14:16 CEST --- *** Bug 869426 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=869426 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c27 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Summary|YaST sw_single (QT) |[libyui-qt-pkg] YaST |crashwith |sw_single crashes with |libproxy1-config-kde4 |libproxy1-config-kde4 --- Comment #27 from Martin Vidner 2014-05-26 11:26:59 CEST --- Another duplicate is in bug 842567 comment 17. To summarize the problem: We have an application using Qt5 that, indirectly, via libzypp, libproxy1, libproxy1-config-kde4, loads Qt4, which results in a crash because of ...? YaST is AFAIK so far the only app in Factory ported to Qt5. What are our options? 1) Fix Qt symbol versioning. Clearly unrealistic across the whole of Qt, but perhaps possible for a smaller part involved?? 2) Make libproxy KDE plugin to Qt5. Note that KDE is in between and I have no idea how far KDE5 is and whether it (or parts of it) can be used. The relevant part of libproxy source is https://code.google.com/p/libproxy/source/browse/trunk/libproxy/modules/conf... 3) Make libyui-qt conflict with libproxy-config-kde4 which is suggested in https://github.com/libyui/libyui-qt/pull/28 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c29 --- Comment #29 from Martin Vidner 2014-05-26 16:13:44 CEST --- Thanks! note to myself, kconfig is here: https://build.opensuse.org/package/show/KDE:Frameworks5/kconfig -- 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.

(In reply to comment #28)

...

(In reply to comment #27)

...

2) Make libproxy KDE plugin to Qt5. Note that KDE is in between and I have no idea how far KDE5 is and whether it (or parts of it) can be used. More realistic. KConfig is tier 1 Framework (and only some qtbase modules are required) http://api.kde.org/frameworks-api/frameworks5-apidocs/kconfig/html/index.htm...

latest beta is in Factory, and final is scheduled in less than 2 months.

Just one note: As I see it, the whole point of libproxy1-config-kde4 is to get the proxy settings from KDE4 (kioslaverc) if the software is running inside KDE4. So IMHO it makes no sense to rewrite this to use FW5 (which stores the settings in ~/.config/ instead of ~/.kde4/share/config/).

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c31 --- Comment #31 from Hrvoje Senjan 2014-05-26 16:02:28 UTC --- (In reply to comment #30) true, i forgot about this detail :D well, it could be done so at least kde4 config is migrated to 'new' location http://api.kde.org/frameworks-api/frameworks5-apidocs/kcoreaddons/html/class... that wont do nothing though for future changes of kde4 config. otherwise, i am not sure how would lower level lib determine some of it's users load Qt5... or zypper would need to be in a separate process than YaST. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c33 --- Comment #33 from Wolfgang Bauer 2014-05-26 17:06:19 UTC --- And another thing: Don't forget KDE4/Qt4 applications. If you rewrite libproxy1-config-kde4 to use Qt5/FW5, KDE4/Qt4 applications using libproxy would crash I suppose. According to the package dependencies, that might even affect Firefox because of its KDE4 integration. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c35 --- Comment #35 from Wolfgang Bauer 2014-05-27 07:07:27 UTC --- Sorry for the "spam", but I had another idea which I think is the best solution: rewrite libproxy1-config-kde to _not_ use KConfig at all, but read and parse kioslaverc by hand. As it only wants the proxy settings, this should not be too hard to do: - read the file line-by-line until you get "[Proxy Settings]" - then read and interpret the following lines (option=value pairs) until the next "[xxx]" or end-of-file. This would avoid all libqt4/qt5 clashes. The proxy settings in kioslaverc look like this: [Proxy Settings] NoProxyFor= Proxy Config Script= ProxyType=0 ReversedException=false ftpProxy=xxxx httpProxy=xxxx httpsProxy=xxxx socksProxy=xxxx The only special entry there would be "NoProxyFor" which contains a list of strings, KConfig returns this as QStringList. The rest are just standard strings, except ProxyType (an integer) and ReversedException (boolean, i.e. "true" or "false"). Until this is done, comment#34 might be a workaround I think. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c37 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|ma@suse.com | --- Comment #37 from Michael Andres 2014-05-27 11:51:18 CEST ---

what its purpose in libzypp is

Reducing bugload. We didn't want to deal with all those potential sources of proxy definition and people complaining that their settings were not used. libproxy internally has a /etc/sysconfig/proxy reader module (with high priority if you are root) and if /etc/sysconfig/proxy exists. All the rest is up to libproxy. libproxy is disabled on SLE11, because PM insisted on staying with an outdated libzproxy0 and did not want to update to libproxy1. libzproxy0 does not work for us. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c45 --- Comment #45 from Dominique Leuenberger 2014-07-24 19:01:41 UTC --- *** Bug 871638 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=871638 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c47 Ladislav Slezak changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent CC| |lslezak@suse.com Component|YaST2 |KDE4 Workspace AssignedTo|yast2-maintainers@suse.de |kde-maintainers@suse.de QAContact|jsrain@suse.com |qa-bugs@suse.de --- Comment #47 from Ladislav Slezak 2014-07-29 10:03:12 UTC --- bnc#889329 contains some more details in the backtrace: #0 QHash (this=0x7fffd3680ab0 KAuth::s_watchers) at /usr/include/QtCore/qhash.h:281 #1 __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/src/debug/kdelibs-4.13.80/kdecore/auth/kauthactionwatcher.cpp:44 #2 _GLOBAL__sub_I_kauthactionwatcher.cpp(void) () at /usr/src/debug/kdelibs-4.13.80/build/kdecore/kauthactionwatcher.moc:155 #3 0x00007ffff7dea92a in call_init (l=<optimized out>, argc=argc@entry=5, argv=argv@entry=0x7fffffffddc8, env=env@entry=0x717ec50) at dl-init.c:78 #4 0x00007ffff7deaa13 in call_init (env=0x717ec50, argv=0x7fffffffddc8, argc=5, l=<optimized out>) at dl-init.c:36 #5 _dl_init (main_map=main_map@entry=0x69c62a0, argc=5, argv=0x7fffffffddc8, env=0x717ec50) at dl-init.c:126 #6 0x00007ffff7deeb48 in dl_open_worker (a=a@entry=0x7fffffff59d8) at dl-open.c:566 #7 0x00007ffff7dea7e4 in _dl_catch_error which tracks it down to kauthactionwatcher in KDE, so it does not look like a Yast bug. More over it has 10 duplicates so it's kind of urgent. We should really move here, reassigning to KDE maintainers to check the kauthactionwatcher KDE component. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c49 Hrvoje Senjan changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE4 Workspace |YaST2 AssignedTo|kde-maintainers@suse.de |yast2-maintainers@suse.de QAContact|qa-bugs@suse.de |jsrain@suse.com --- Comment #49 from Hrvoje Senjan 2014-07-29 19:25:24 UTC --- Ladislav, the bug is in libproxy, and it's usage within YaST and zypper. See comment #34 and comment #35 which contain possible solutions, and also Alexander hinted another one in bug 885752. See comment #12 for upstream report. @Kyrill, that's bug 866622. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c51 Ladislav Slezak changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED Summary|[libyui-qt-pkg] YaST |YaST sw_single crashes with |sw_single crashes with |libproxy1-config-kde4 |libproxy1-config-kde4 | --- Comment #51 from Ladislav Slezak 2014-07-30 08:31:44 UTC --- Fixed in yast2-3.1.92 (https://github.com/yast/yast-yast2/pull/278, SR#242961 to Factory) -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=866692 Stefan Schubert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |schubi@suse.com --- Comment #53 from Stefan Schubert --- Fixed in https://github.com/yast/yast-installation/pull/242 -- You are receiving this mail because: You are on the CC list for the bug.