[New: openFATE 308964] Network Services in Yasts Conflict with KDE Configure Desktop
Feature added by: Scott Couston - Resigned No Confidence (zczc2311) Feature #308964, revision 1 Title: Network Services in Yasts Conflict with KDE Configure Desktop openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Scott Couston - Resigned No Confidence (zczc2311) Description: <!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } --> Network Services and their ability to function is often in conflict between KDE's Configure Desktop and Yast. In 11.2 a user cannot configure a Samba server using Yast and Configure Desktop with an MS Workgroup. The Yast>Network Services>Samba Server Interface will simply not work on its own to provide a New or existing shared RW Directory or Publish an Existing Printer. There is conflict between the Interfaces Configure Desktop/Yast Samba Server/The (Dolfin) Directory Properties Rights/The (Dolfin) Directories Properties> Shared Configuration. The Interface in Configure Desktop >Advanced>Samba cannot add a Shared Printer where the Printer is configured by HPLIP. Using ANY or all 3 Interfaces in 11.2 is just NOT possible to create a functional Samba Server By itself HPLIP DOES seamlessly interfaces with Yast>Printer its great. Many Network Service type Interfaces from KDE's Configure Desktop are in conflict. Desktop Search conflicts with Beagle. Configure Desktop Hardware conflicts with Yast Network Connections and others particularly with IFUP. Task Scheduler conflicts with Auto-Start. We need to test out own Interface conflicts between Yast and Configure Desktop settings before we release our integrated KDE Software/Yast Package. Auto-Spell just failed in this text box of FATE. KDE Server and Desktop software needs to work out of the box. (The Fate Error " There were errors: * The description is not valid richtext: Error: Element p is not declared in p list of possible children at :0." does not help anyone -- openSUSE Feature: https://features.opensuse.org/308964
Feature changed by: Scott Couston (zczc2311) Feature #308964, revision 2 Title: Network Services in Yasts Conflict with KDE Configure Desktop openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Scott Couston (zczc2311) Partner organization: openSUSE.org Description: - <!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } --> Network Services and their ability to function is often in conflict between KDE's Configure Desktop and Yast. In 11.2 a user cannot configure a Samba server using Yast and Configure Desktop with an MS Workgroup. The Yast>Network Services>Samba Server Interface will simply not work on its own to provide a New or existing shared RW Directory or Publish an Existing Printer. - There is conflict between the Interfaces Configure Desktop/Yast Samba Server/The (Dolfin) Directory Properties Rights/The (Dolfin) Directories Properties> Shared Configuration. The Interface in Configure Desktop >Advanced>Samba cannot add a Shared Printer where the Printer is configured by HPLIP. Using ANY or all 3 Interfaces in 11.2 is just NOT possible to create a functional Samba Server By itself HPLIP DOES seamlessly interfaces with Yast>Printer its great. Many Network Service type Interfaces from KDE's Configure Desktop are in conflict. Desktop Search conflicts with Beagle. Configure Desktop Hardware conflicts with Yast Network Connections and others particularly with IFUP. Task Scheduler conflicts with Auto- Start. We need to test out own Interface conflicts between Yast and Configure Desktop settings before we release our integrated KDE Software/Yast Package. Auto-Spell just failed in this text box of FATE. KDE Server and Desktop software needs to work out of the box. - - (The Fate Error " - There were errors: - * The description is not valid richtext: Error: Element p is not - declared in p list of possible children at :0." does not help anyone - -- openSUSE Feature: https://features.opensuse.org/308964
Feature changed by: Scott Couston (zczc2311) Feature #308964, revision 3 Title: Network Services in Yasts Conflict with KDE Configure Desktop openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Scott Couston (zczc2311) Partner organization: openSUSE.org Description: Network Services and their ability to function is often in conflict between KDE's Configure Desktop and Yast. In 11.2 a user cannot configure a Samba server using Yast and Configure Desktop with an MS Workgroup. The Yast>Network Services>Samba Server Interface will simply not work on its own to provide a New or existing shared RW Directory or Publish an Existing Printer. There is conflict between the Interfaces Configure Desktop/Yast Samba Server/The (Dolfin) Directory Properties Rights/The (Dolfin) Directories Properties> Shared Configuration. The Interface in Configure Desktop >Advanced>Samba cannot add a Shared Printer where the Printer is configured by HPLIP. Using ANY or all 3 Interfaces in 11.2 is just NOT possible to create a functional Samba Server By itself HPLIP DOES seamlessly interfaces with Yast>Printer its great. Many Network Service type Interfaces from KDE's Configure Desktop are in conflict. Desktop Search conflicts with Beagle. Configure Desktop Hardware conflicts with Yast Network Connections and others particularly with IFUP. Task Scheduler conflicts with Auto- Start. We need to test out own Interface conflicts between Yast and Configure Desktop settings before we release our integrated KDE Software/Yast Package. Auto-Spell just failed in this text box of FATE. KDE Server and Desktop software needs to work out of the box. + Discussion: + #1: Scott Couston (zczc2311) (2011-02-04 00:05:45) + QA - Please close/cancel this request as it has already be put into + action by another source -- openSUSE Feature: https://features.opensuse.org/308964
Feature changed by: Scott Couston (zczc2311) Feature #308964, revision 4 Title: Network Services in Yasts Conflict with KDE Configure Desktop openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Scott Couston (zczc2311) Partner organization: openSUSE.org Description: Network Services and their ability to function is often in conflict between KDE's Configure Desktop and Yast. In 11.2 a user cannot configure a Samba server using Yast and Configure Desktop with an MS Workgroup. The Yast>Network Services>Samba Server Interface will simply not work on its own to provide a New or existing shared RW Directory or Publish an Existing Printer. There is conflict between the Interfaces Configure Desktop/Yast Samba Server/The (Dolfin) Directory Properties Rights/The (Dolfin) Directories Properties> Shared Configuration. The Interface in Configure Desktop >Advanced>Samba cannot add a Shared Printer where the Printer is configured by HPLIP. Using ANY or all 3 Interfaces in 11.2 is just NOT possible to create a functional Samba Server By itself HPLIP DOES seamlessly interfaces with Yast>Printer its great. Many Network Service type Interfaces from KDE's Configure Desktop are in conflict. Desktop Search conflicts with Beagle. Configure Desktop Hardware conflicts with Yast Network Connections and others particularly with IFUP. Task Scheduler conflicts with Auto- Start. We need to test out own Interface conflicts between Yast and Configure Desktop settings before we release our integrated KDE Software/Yast Package. Auto-Spell just failed in this text box of FATE. KDE Server and Desktop software needs to work out of the box. Discussion: #1: Scott Couston (zczc2311) (2011-02-04 00:05:45) QA - Please close/cancel this request as it has already be put into action by another source + #2: Scott Couston (zczc2311) (2011-04-13 03:43:48) + I am happy to learn the there are plans to merge KDE Configure Desktop + into YAST - This feature request was made about the very same issue + back in the release of 11.2 when OpenFATE was just made available and + as an enhancement request when 11.0 was released...does anyone ever + read these feature requests??? -- openSUSE Feature: https://features.opensuse.org/308964
participants (1)
-
fate_noreply＠suse.de