|
Bugzilla – Full Text Bug Listing |
| Summary: | The module YaST isn´t a valid configuration module | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Rastislav Krupansky <rastislav.krupansky> |
| Component: | YaST2 | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P3 - Medium | CC: | kde-maintainers, sourtooth |
| Version: | Milestone 1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
screenshot
(maybe) fixed .desktop file screenshot |
||
Change X-KDE-ServiceTypes= to SystemSettingsExternalApp and add kdesu to the Exec= call, that should do. Created attachment 340524 [details]
(maybe) fixed .desktop file
Ra100, can you please copy attached file to /usr/share/kde4/services/, rename it to YaST-systemsettings.desktop and see if it resolves the problem?
I'd like to try myself, but I can't reproduce with Factory
Yes, seems to be fixed, but on the background in systemsettings is note: YaST is an external application and has been automatically launched. Relaunch YaST. I think it is confusing a little bit. Attached screenshot Created attachment 340574 [details]
screenshot
Well I guess it's a feature of KDE CC then. submitreq 34612 The rest (comment #4) is KDE CC feature, it does this for all external apps (In reply to comment #7) > submitreq 34612 > The rest (comment #4) is KDE CC feature, it does this for all external apps A strange feature, i think. I can´t see any meaning in that. What´s is a benefit of this behaviour? Reopening and passing to KDE team then The benefit of this behaviour is to avoid launching multiple applications if the item clicked on is a category, and thus has child objects. I fail to see how it is confusing.... - KDE System Settings maintainer @Katarina: You can remove the X-KDE-RootOnly line from that *.desktop file also... (In reply to comment #10) > I fail to see how it is confusing.... Especially "Relaunch YaST" button is confusing. Why should i relaunch YaST, if YaST is launched and correctly? This button stir up feeling that YaST wasn´t launched correctly and i have to relaunch it again. Unfortunately it is either a choice of having the button, or being forced to go back to the overview or restarting System Settings before being able to launch YaST again. This is undesirable in the case of having external apps as part of a sub-category to not have the button. It isn't possible to monitor the process either, since that would tie the life of YaST to System Settings due to Qt limitations ( at least as far as I can see ) Ideas for better texts would likely be the solution in this case. Ideas? Seems to be fixed in factory build 0602. No additional windows appears on the background. Just YaST is launched. Closing as fixed. This is an autogenerated message for OBS integration: This bug (574864) was mentioned in https://build.opensuse.org/request/show/34612 Factory / yast2-control-center |
Created attachment 339471 [details] screenshot User-Agent: Opera/9.80 (Windows NT 5.1; U; sk) Presto/2.2.15 Version/10.10 Unable to open YaST from KDE´s system settings. When i click on YaST icon in system settings, i obtain: The module YaST isn´t a valid configuration module The diagnosis is: The desktop file YaST-systemsettings.desktop does not specify a library. Attached screenshot Reproducible: Always Steps to Reproduce: 1. 2. 3.