|
Bugzilla – Full Text Bug Listing |
| Summary: | the "Encrypt Volume Group" checkbox is uncheckable when lvm proposed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Max Lin <mlin> |
| Component: | YaST2 | Assignee: | Martin Vidner <mvidner> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P2 - High | CC: | aschnell, coolo, hvdheuvel, jreidinger, kukuk, locilka, lslezak, mpluskal, tiwai, w.pelser, whdu, yfjiang |
| Version: | 13.2 Milestone 0 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Max Lin
2014-03-14 07:43:36 UTC
There's a error from libyui-qt in the logs: [qt-ui] YQUI.cc(qMessageHandler):716 <libqt-warning> QObject::connect: signal not found in YQCheckBox Martin, is that a known issue? BTW: The same Ruby code works on SLES12 Beta 2. It is because I switched to a new signal connection method, advertised as type-safe :-/ A similar problem is described in http://qt-project.org/forums/viewthread/24855 which points to a Qt bug, apparently already fixed: https://codereview.qt-project.org/#change,55606 *** Bug 868649 has been marked as a duplicate of this bug. *** *** Bug 869363 has been marked as a duplicate of this bug. *** The warning to look for in the logs is "<libqt-warning> QObject::connect: signal not found in Foo" where Foo is a class name. We should screen for all "<libqt-warning>" and <libqt-critical> *** Bug 869389 has been marked as a duplicate of this bug. *** Proposed fix: RPM: libyui-qt-2.46.3 Git: https://github.com/libyui/libyui-qt/pull/27 fix submitted to IBS: https://build.suse.de/request/show/34709 OBS: https://build.opensuse.org/request/show/227026 (accepted) *** Bug 869862 has been marked as a duplicate of this bug. *** *** Bug 870401 has been marked as a duplicate of this bug. *** *** Bug 869572 has been marked as a duplicate of this bug. *** It looks like bnc #869572 still not fixed. Please confirm if it is the same problem. *** Bug 898984 has been marked as a duplicate of this bug. *** |