September 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306733] Add KDE3 buildservice repository to community list
by fate_noreply＠suse.de 02 Sep '09

02 Sep '09

Feature added by: Karsten König (remur) Feature #306733, revision 1 Title: Add KDE3 buildservice repository to community list openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Karsten König (remur) Description: As openSUSE 11.2 will drop KDE3 from main repositories we should make adding the KDE3 repository as easy as possible, adding KDE3 to the community repository list would be an easy way to do this and will point out the unsupported state of the repository. Use Case: * Elmar wants to keep using KDE3 as KDE4 still isn't ready for him, he doesn't mind using a seperate inofficial repository though. This will make it easy for him to add the repository at install time and select KDE3 * Karsten hangs around #opensuse-kde and after 11.2 release a lot of people come and ask how to get KDE3 and start bitching about the decission to drop it, he can now point out this easy way to add the repository and help restore order in the channel -- openSUSE Feature: https://features.opensuse.org/306733

1 28

[openFATE 300689] TabletPC: Support Touchscreen and Wacom decives during installation
by fate_noreply＠suse.de 02 Sep '09

02 Sep '09

Feature changed by: Jose Ricardo De Leon Solis (derhundchen) Feature #300689, revision 39 Title: TabletPC: Support Touchscreen and Wacom decives during installation openSUSE-10.3: Rejected by Stephan Kulow (coolo) reject date: 2007-08-03 09:39:40 reject reason: installation is frozen Priority Requester: Desirable Projectmanager: Desirable openSUSE-11.1: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-07-16 09:02:38 reject reason: Postponing. Out of resources. Priority Requester: Important Projectmanager: Important openSUSE-11.2: Rejected by Michael Löffler (michl19) reject date: 2009-04-16 12:28:26 reject reason: out of scope for 11.2 Priority Requester: Important Projectmanager: Important + openSUSE-11.3: Unconfirmed + Priority + Requester: Mandatory Requested by: Stefan Behlert (sbehlert) Description: Tablet PCs are normally produced in two kinds of flavours: Convertibles, which have a keyboard, and Slates, which have none (only pens or touchscreens). If a user installs a Slate, he has no keyboard and no (pohysical) mouse device, only the touchscreen. We should on TabletPCs automatically recognize that it is a TabletPC and configure the Wacom or other Touchscreen device where possible. Thus would enhance the usability of the product on TabletPCs. Discussion: #1: Gary Ekker (gekker) (2007-07-17 11:24:05) Stefan, do you see this as work that your team would do, something that needs to be done by the YaST installer, or both? #6: Matthias Nagorni (mnagorni) (2009-08-24 13:17:30) As long as there is a different way to install it, this appears only like a "nice to have". -- openSUSE Feature: https://features.opensuse.org/300689

1 0

[openFATE 307591] Cannot remove hyperlink in share mode
by fate_noreply＠suse.de 01 Sep '09

01 Sep '09

Feature added by: Tomas Juraska (tjuraska) Feature #307591, revision 1 Title: Cannot remove hyperlink in share mode Requested by: Tomas Juraska (tjuraska) Description: Cannot remove a hyperlink while in share mode, from right click > hyperlink. In normal mode, we have remove hyperlink option in right click, it's disabled in sharemode. -- openSUSE Feature: https://features.opensuse.org/307591

1 0

[openFATE 307590] test
by fate_noreply＠suse.de 01 Sep '09

01 Sep '09

Feature added by: Thomas Schmidt (digitaltomm) Feature #307590, revision 1 Title: test Buildservice: Unconfirmed Priority Requester: Important Requested by: Thomas Schmidt (digitaltomm) Description: test -- openSUSE Feature: https://features.opensuse.org/307590

1 0

[openFATE 307589] Rename sheet in share mode
by fate_noreply＠suse.de 01 Sep '09

01 Sep '09

Feature added by: Tomas Juraska (tjuraska) Feature #307589, revision 1 Title: Rename sheet in share mode Requested by: Tomas Juraska (tjuraska) Description: We would like to be able to rename a sheet in Spreadsheat shared document. -- openSUSE Feature: https://features.opensuse.org/307589

1 0

[openFATE 305657] finer grained PolicyKit support for Networkmanager
by fate_noreply＠suse.de 01 Sep '09

01 Sep '09

Feature changed by: Li Bin (BinLi) Feature #305657, revision 25 Title: finer grained PolicyKit support for Networkmanager openSUSE-11.2: Evaluation Priority Requester: Important Projectmanager: Desirable Requested by: Ludwig Nussel (lnussel) Description: NetworkManager currently only supports one PolicyKit privilege. That is whether a user is allowed to modify administrator defined connections or not. There is no way to disallow users to define their own network configurations. NetworkManager should at least support one additional PolicyKit privilege that defines whether or not users are allowed to bring their own network configuration or whether they mere are allowed to use administrator defined ones. Use Case: - disallow workers on centrally administered machines to configure different network settings - protect home users that only ever connect to a few well known nets from accidently changing their setup Discussion: #1: Matthias Nagorni (mnagorni) (2009-08-21 14:26:22) If this can be done with little effort I would be even tempted to rate it Mandatory. #2: Stefan Behlert (sbehlert) (2009-08-25 16:37:57) Alex, is there soemone on your team who could look at that? MAybe with some support form Tambet? #3: Li Bin (binli) (2009-08-26 05:58:01) I and lance wang would like to take care of it. We still don't know the requirement clearly. 1. disallow workers on centrally administered machines to configure different network settings The workers mean the users in administered machines? Does it right that when workers configure network settings it prompt they are no permission? If so I thought we could change the PolicyKit's configuration file to complete it. 2. protect home users that only ever connect to a few well known nets from accidently changing their setup How to distinguish home users from workers? Does it mean don't allow the user to configure the other users connections? #4: Ludwig Nussel (lnussel) (2009-08-26 08:40:53) (reply to #3) Currently there's only org.freedesktop.network-manager-settings.system. modify, introduce something like org.freedesktop.network-manager- settings.user.modify so NM can determine whether it should accept user settings. #5: JP Rosevear (jproseve) (2009-08-26 17:06:51) (reply to #3) My suggestion would be to look at something like the following: org. freedesktop.network-manager-settings.system.modify org.freedesktop. network-manager-settings.system.add org.freedesktop.network-manager- settings.system.delete and the same for .user - you may even want to specifically allow or disallow adding for specific network types like wired, wireless, etc. You probably also want to have the ability to enable/disable wireless in general and enable/disable networking covered. You can default all of these to the current settings, but adding these would allow more lockdown opportunities. #6: Li Bin (binli) (2009-08-31 11:22:12) Well, We'll works on this feature in this week, know about the PolicyKit and NetworkManager, write the patch if time is okay. Tambet, Do you have any idea about this feature? #7: Luis Medinas (lmedinas) (2009-08-31 18:40:51) (reply to #6) Might worth looking at NM 0.8 (git master), it supports the latest polkit-1 and it should be released before 11.2. Maybe some of this features were introduced. #8: Tambet Ingo (tambet) (2009-09-01 09:40:05) (reply to #7) NM 0.8 will not be out before 11.2, it'll be out for the next Fedora release which will happen after 11.2. Also, current git master does not have any work for this feature, it's just been converted to use the newer, incompatible polkit API. #9: Tambet Ingo (tambet) (2009-09-01 09:43:56) (reply to #6) The upstream has been planning on having similar feature for a while now, but no work has been done on it yet. I strongly suggest to have a discussion with the upstream maintainer before any work gets done, otherwise our effort might end up thrown away as soon as upstream implements it. + #10: Li Bin (binli) (2009-09-01 09:14:24) + Yes, I talk with the upstream today, just wait for response. You can + follow it from below link. Thanks! + http://mail.gnome.org/archives/networkmanager-list/2009-September/date.html -- openSUSE Feature: https://features.opensuse.org/305657

1 0

[openFATE 305657] finer grained PolicyKit support for Networkmanager
by fate_noreply＠suse.de 01 Sep '09

01 Sep '09

Feature changed by: Tambet Ingo (tambet) Feature #305657, revision 24 Title: finer grained PolicyKit support for Networkmanager openSUSE-11.2: Evaluation Priority Requester: Important Projectmanager: Desirable Requested by: Ludwig Nussel (lnussel) Description: NetworkManager currently only supports one PolicyKit privilege. That is whether a user is allowed to modify administrator defined connections or not. There is no way to disallow users to define their own network configurations. NetworkManager should at least support one additional PolicyKit privilege that defines whether or not users are allowed to bring their own network configuration or whether they mere are allowed to use administrator defined ones. Use Case: - disallow workers on centrally administered machines to configure different network settings - protect home users that only ever connect to a few well known nets from accidently changing their setup Discussion: #1: Matthias Nagorni (mnagorni) (2009-08-21 14:26:22) If this can be done with little effort I would be even tempted to rate it Mandatory. #2: Stefan Behlert (sbehlert) (2009-08-25 16:37:57) Alex, is there soemone on your team who could look at that? MAybe with some support form Tambet? #3: Li Bin (binli) (2009-08-26 05:58:01) I and lance wang would like to take care of it. We still don't know the requirement clearly. 1. disallow workers on centrally administered machines to configure different network settings The workers mean the users in administered machines? Does it right that when workers configure network settings it prompt they are no permission? If so I thought we could change the PolicyKit's configuration file to complete it. 2. protect home users that only ever connect to a few well known nets from accidently changing their setup How to distinguish home users from workers? Does it mean don't allow the user to configure the other users connections? #4: Ludwig Nussel (lnussel) (2009-08-26 08:40:53) (reply to #3) Currently there's only org.freedesktop.network-manager-settings.system. modify, introduce something like org.freedesktop.network-manager- settings.user.modify so NM can determine whether it should accept user settings. #5: JP Rosevear (jproseve) (2009-08-26 17:06:51) (reply to #3) My suggestion would be to look at something like the following: org. freedesktop.network-manager-settings.system.modify org.freedesktop. network-manager-settings.system.add org.freedesktop.network-manager- settings.system.delete and the same for .user - you may even want to specifically allow or disallow adding for specific network types like wired, wireless, etc. You probably also want to have the ability to enable/disable wireless in general and enable/disable networking covered. You can default all of these to the current settings, but adding these would allow more lockdown opportunities. #6: Li Bin (binli) (2009-08-31 11:22:12) Well, We'll works on this feature in this week, know about the PolicyKit and NetworkManager, write the patch if time is okay. Tambet, Do you have any idea about this feature? #7: Luis Medinas (lmedinas) (2009-08-31 18:40:51) (reply to #6) Might worth looking at NM 0.8 (git master), it supports the latest polkit-1 and it should be released before 11.2. Maybe some of this features were introduced. + #8: Tambet Ingo (tambet) (2009-09-01 09:40:05) (reply to #7) + NM 0.8 will not be out before 11.2, it'll be out for the next Fedora + release which will happen after 11.2. Also, current git master does not + have any work for this feature, it's just been converted to use the + newer, incompatible polkit API. + #9: Tambet Ingo (tambet) (2009-09-01 09:43:56) (reply to #6) + The upstream has been planning on having similar feature for a while + now, but no work has been done on it yet. I strongly suggest to have a + discussion with the upstream maintainer before any work gets done, + otherwise our effort might end up thrown away as soon as upstream + implements it. -- openSUSE Feature: https://features.opensuse.org/305657

1 0

[openFATE 302311] Handle Bluetooth network in Networkmanager
by fate_noreply＠suse.de 01 Sep '09

01 Sep '09

Feature changed by: Tambet Ingo (tambet) Feature #302311, revision 33 Title: Handle Bluetooth network in Networkmanager openSUSE-11.2: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Stefan Behlert (sbehlert) Description: Networks created over Bluetooth should be handled in Networkmanager, too. This includes WiNet (UWB) References: http://bugzilla.gnome.org/show_bug.cgi?id=432774 Discussion: #1: JP Rosevear (jproseve) (2008-07-14 20:40:48) Bastien N. at RedHat has done some work here now after the somewhat failed initial upstream attempt. #2: JP Rosevear (jproseve) (2008-07-21 13:42:26) (reply to #1) Taking this only if upstream provides it. #3: JP Rosevear (jproseve) (2008-09-08 09:38:29) (reply to #2) Upstream has not provided it in time. #4: Luis Medinas (lmedinas) (2009-06-02 05:38:42) This feature has landed NetworkManager git. It should be available for 0.7.2. + #6: Tambet Ingo (tambet) (2009-09-01 09:32:28) (reply to #4) + This feature will never be added to 0.7.x tree. It's in the git master + branch and will be part of 0.8 version. -- openSUSE Feature: https://features.opensuse.org/302311

1 0