|
Bugzilla – Full Text Bug Listing |
| Summary: | libpy2UI.so.2: undefined symbol | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Markus Elfring <Markus.Elfring> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | Markus.Elfring |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Markus Elfring
2015-07-10 14:16:02 UTC
YSettings::setProgDir() is defined in libyui so please ensure that new versions of that library and its sub-libraries are also installed. Tumbleweed switched to gcc 5 and there have been ABI changes to some STL classes, e.g. string, so maybe the standard library dependencies alone does not work. (In reply to Arvin Schnell from comment #1) > YSettings::setProgDir() is defined in libyui so please ensure that new > versions of that library and its sub-libraries are also installed. I started another software update a moment ago. Component: libyui 3.1.5-1.4 Installed: Fr 10 Jul 2015 16:53:15 CEST The management GUI works again now. > Tumbleweed switched to gcc 5 and there have been ABI changes to some STL > classes, e.g. string, so maybe the standard library dependencies alone > does not work. How are the chances that such application binary interface adjustments will trigger appropriate updates for YaST2 modules automatically? Do descriptions need any more fine-tuning for corresponding RPM specifications? (In reply to Markus Elfring from comment #2) > I started another software update a moment ago. > > Component: libyui 3.1.5-1.4 > Installed: Fr 10 Jul 2015 16:53:15 CEST > The management GUI works again now. Fine, so we can close this particular bug. > > Tumbleweed switched to gcc 5 and there have been ABI changes to some STL > > classes, e.g. string, so maybe the standard library dependencies alone > > does not work. > > How are the chances that such application binary interface adjustments will > trigger appropriate updates for YaST2 modules automatically? > > Do descriptions need any more fine-tuning for corresponding RPM > specifications? You could ask that question on opensuse-factory. |