[Bug 866692] New: YaST sw_single (QT) crash
https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c0 Summary: YaST sw_single (QT) crash Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers@suse.de ReportedBy: wbauer@tmo.at QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=580839) --> (http://bugzilla.novell.com/attachment.cgi?id=580839) y2log after the crash (the old one was deleted before starting YaST) User-Agent: Mozilla/5.0 (X11; Linux) KHTML/4.12.2 (like Gecko) Konqueror/4.12 SUSE This is on a fresh Factory 32bit installation (inside VMWare). When trying to install packages, YaST Software Management just crashes with: YaST got signal 11 at YCP file /usr/share/YaST2/modules/SlideShow.rb:385 /sbin/yast2: line 429: 2825 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Attached is the y2log. Reproducible: Always Steps to Reproduce: 1. Enter YaST->Software Management 2. Select a package to install 3. Click on "Accept" Actual Results: YaST crashes Expected Results: YaST should install the package(s). Please note that this was without libqdialogsolver1 installed, so it is not related to 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#c1
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c2
Wolfgang Bauer
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c3
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c4
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c5
--- Comment #5 from Robert Kaiser
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c6
--- Comment #6 from Dominique Leuenberger
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c7
Hrvoje Senjan
I assume this is a result of Qt4 and Qt5 ending up on the same process space and having symbol clashes...
Yes, but should not happen w/o libqdialogsolver1. Neither YaST links to kdecore (thus Qt4), nor kdecore links to Qt5. FYI, i am using now YaST packager without issues post removal of the solver & reboot (also operations seems to work, e.g. removing packages, etc) -- 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
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c9
--- Comment #9 from Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c10
Wolfgang Bauer
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#c11
--- Comment #11 from Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c12
--- Comment #12 from Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c13
Martin Vidner
I assume this is a result of Qt4 and Qt5 ending up on the same process space and having symbol clashes...
I thought the linker took care of that not happening. Dominique, can you please explain how it fails? Any pointers to educate me? -- 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
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c15
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c16
Alin M Elena
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c17
Graham Davis
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c18
dale ritchey
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.
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c19
Kyrill Detinov
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
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c21
--- Comment #21 from Graham Davis
(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
That's done it. Thanks. -- 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
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#c23
Thomas Nielsen
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c24
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c25
--- Comment #25 from shimi m
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c26
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c27
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c28
--- Comment #28 from Hrvoje Senjan
YaST is AFAIK so far the only app in Factory ported to Qt5. Others are slowly comming (qupzilla, fctix, ...)
1) Fix Qt symbol versioning. Clearly unrealistic across the whole of Qt, but perhaps possible for a smaller part involved?? I don't think this is an option.
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.
3) Make libyui-qt conflict with libproxy-config-kde4 which is suggested in https://github.com/libyui/libyui-qt/pull/28 last resort
i however wasn't even aware of the libproxy library before i saw this bug, so can't say how many people are using it... -- 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
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c30
--- Comment #30 from Wolfgang Bauer
(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/). OTOH, this didn't work in practice anyway I think, as YaST runs as root and therefore doesn't see the KDE4 user's proxy settings, but root's (from /root/.kde4/share/config/kioslaverc). -- 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
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c32
--- Comment #32 from Wolfgang Bauer
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c33
--- Comment #33 from Wolfgang Bauer
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.
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c35
--- Comment #35 from Wolfgang Bauer
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c36
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c37
Michael Andres
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#c38
Michael Andres
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c45
--- Comment #45 from Dominique Leuenberger
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c46
Ladislav Slezak
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c47
Ladislav Slezak
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c48
--- Comment #48 from Kyrill Detinov
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c49
Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c50
Ladislav Slezak
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c51
Ladislav Slezak
https://bugzilla.novell.com/show_bug.cgi?id=866692
https://bugzilla.novell.com/show_bug.cgi?id=866692#c52
Ladislav Slezak
http://bugzilla.novell.com/show_bug.cgi?id=866692
Stefan Schubert
participants (1)
-
bugzilla_noreply@novell.com