January 2012 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 309721] Make forums.opensuse.org true international
by fate_noreply＠suse.de 27 Jan '12

27 Jan '12

Feature added by: Yuri Tsarev (xnull) Feature #309721, revision 1 Title: Make forums.opensuse.org true international Requested by: Yuri Tsarev (xnull) Description: Current situarion at forums.o.o is that newcomer non-english users have to find workaround of manual language switch before they can read forum branches in their native language. It is incovnenient, old-fashioned and just ugly. There is two ways to solve this problem. 1) Dirty hack with apache rewrite rules wich resolves user's browser language and makes automatic redirect to current language. The example part of apache config for russian users is here : RewriteEngine on RewriteBase / RewriteCond %{HTTP:Accept-Language} (^ru) [NC] # RU redirects RewriteRule ^$ /?langid=4 [L,R] 2) Convert all backend data to UTF-8. This will be the beautiful and correct solution. -- openSUSE Feature: https://features.opensuse.org/309721

1 5

[New: openFATE 313169] Allow ifup scripts for interfaces not managed by NetworkManager
by fate_noreply＠suse.de 25 Jan '12

25 Jan '12

Feature added by: Luiz Angelo Daros de Luca (luizluca) Feature #313169, revision 1 Title: Allow ifup scripts for interfaces not managed by NetworkManager openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Luiz Angelo Daros de Luca (luizluca) Partner organization: openSUSE.org Description: Hello, My main network connection is just a standard one: plug and DHCP. However, I have several other connections that use some unusual configurations. I have, for example, tap interfaces. Also, I have two other NIC that I asked NM to not managed it. The problem is that these not-managed-by-NM interfaces are also not configured with ifup scripts. If I run "ifup tap0", I get: Network interface is managed by the NetworkManager -> skipping However, it is not managed by NM. NM does not even support tap interfaces. The same goes to my other NIC, eth1 and eth2, which are listed in: /etc/NetworkManager/NetworkManager.conf: [keyfile] unmanaged-devices=xxxx Please, check if the device is not managed and allow ifup scripts to configure it and bring it up. This also applies to the startup scripts. This works with debian/ubuntu distributions, when a interface is configured in /etc/network/interfaces and so, NM does not touch it. -- openSUSE Feature: https://features.opensuse.org/313169

1 0

[New: openFATE 313012] EC2 support for openSUSE 12.1 in SUSE Studio
by fate_noreply＠suse.de 25 Jan '12

25 Jan '12

Feature added by: James Mason (bear454) Feature #313012, revision 1 Title: EC2 support for openSUSE 12.1 in SUSE Studio SUSE Studio: Unconfirmed Priority Requester: Neutral Requested by: James Mason (bear454) Partner organization: openSUSE.org Description: At the moment, SUSE Studio does not support instantiating openSUSE 12.1 on Amazon's Elastic Compute Cloud. If you would have interest in running openSUSE 12.1 on EC2, please let us know via this feature. -- openSUSE Feature: https://features.opensuse.org/313012

1 4

[openFATE 313143] YaST LDAP client refactor/cleanup
by fate_noreply＠suse.de 23 Jan '12

23 Jan '12

Feature changed by: Jiří Suchomel (jsuchome) Feature #313143, revision 6 Title: YaST LDAP client refactor/cleanup openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Ralf Haferkamp (rhafer) Partner organization: openSUSE.org Description: Jiri (jsuchome) an I recently discussed some cleanup work we'd like to see in the YaST ldap-client module. This feature lists the main items we'd like to see reworked to improve the Module: Remove no longer needed UI elements Candidates are: * The TLS/SSL checkbox (sssd has a hard requirement for SSL/TLS) * The "LDAP Version 2" checkbox in the advanced settings. (there is AFAIK no LDAPv2-only Server implementation left) * The "Use LDAP but Disable Login" Radio Button Restrict the UI to handle only really LDAP client related things Currently the UI contains quite some settings which are not strictly related to LDAP client (nss/pam) setup. Over the year ldap-client became a bit of a disposal site for all kinds of LDAP related things, which made the UI a bit hard to understand. We should move some things to YaST modules where make a better fit. This is mostly about the settings currently available in the "Administration Settings" Tab (in "Advanced Configuration") * The Password Policies settings seem to fit better into the ldap- server module which already contains some of this functionality * Default Configuration Objects for other YaST modules (e.g. mail, dns, dhcp). Where possible the need for those special configuration objects should be removed. When a specific service still requires those configuration objects the YaST module for that service should be able to handle those objects it self (we could still offer utils API for that in yast2-ldap/ldap-client). E.g. the user management related object should be configured from inside the yast2-users module. yast2- ldap-server could offer to create default objects during the initial LDAP server setup. * The Home Directories on This Machine checkbox seems to be better suite in the Users module as well. * The rest of the values which go to /etc/sysconfig/ldap could be written by yast2-ldap-servers. We still need to figure out how to setup /etc/sysconfig/ldap on machines which to not run the LDAP Server but need access to those settings. (yast2-mail, -dns-server, -dhcp-server) * Adapt the API: move the LDAP* functions from ldap-client (impact on other modules!) Relations: - related feature (feature/id: 313142) Discussion: #1: Jiří Suchomel (jsuchome) (2012-01-19 10:15:11) 1. Removing TLS/SSL is based on assumption that we configure SSSD only, which is feature 313142. 2. About The "Use LDAP but Disable Login" Radio Button: did we agree on some replacement of it? I cannot remember... + #2: Jiří Suchomel (jsuchome) (2012-01-23 16:25:33) + Added attachment proposal for simplified first screen (ldap-client- + redesign2.png) -- openSUSE Feature: https://features.opensuse.org/313143

1 0

[New: openFATE 313115] Automatically detect and configure printer once plugged
by fate_noreply＠suse.de 20 Jan '12

20 Jan '12

Feature added by: Flavio Castelli (flavio_castelli) Feature #313115, revision 1 Title: Automatically detect and configure printer once plugged openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Flavio Castelli (flavio_castelli) Partner organization: openSUSE.org Description: It would be nice to automatically install and configure all the printers that are plugged into the system. Right now the user has to manually add the printers using YaST. I noticed Ubuntu has this feature and I found it really useful for the average users. Use Case: User connects his new printer to the computer and turns it on. openSUSE will automatically detect the printer, install the required drivers, configure it and show a notification once the printer is ready to be used. -- openSUSE Feature: https://features.opensuse.org/313115

1 3

[New: openFATE 313159] Provide useful keybinds
by fate_noreply＠suse.de 19 Jan '12

19 Jan '12

Feature added by: Jimmy Berry (boombatower) Feature #313159, revision 1 Title: Provide useful keybinds openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jimmy Berry (boombatower) Partner organization: openSUSE.org Description: I use KDE and setup keybinds that I think many will find useful and I would assume gnome can replicate them in its own form. I am not sure if this would be better place upstream in as a KDE default. Some basic ones that I use all the time. - meta + e = dolphin to home dir (explore from windows [can easily be switched to meta + d for dolphin]) - meta + k = konsole - meta + w = kate (or kwrite [w for write]) Curious to see if anyone has thoughts on this. -- openSUSE Feature: https://features.opensuse.org/313159

1 1

[New: openFATE 313158] Alaki
by fate_noreply＠suse.de 19 Jan '12

19 Jan '12

Feature added by: Hamid Reza Jalali (HJalali) Feature #313158, revision 1 Title: Alaki openSUSE Medical: Unconfirmed Priority Requester: Important Requested by: Hamid Reza Jalali (hjalali) Partner organization: openSUSE.org Description: Alaki is a very important feature that must be in every product. Test Case: TC1 Use Case: UC1 -- openSUSE Feature: https://features.opensuse.org/313158

1 0

[New: openFATE 312327] allow configuration of offline local printer
by fate_noreply＠suse.de 19 Jan '12

19 Jan '12

Feature added by: Jean-Daniel Dodin (jdd) Feature #312327, revision 1 Title: allow configuration of offline local printer openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jean-Daniel Dodin (jdd) Partner organization: openSUSE.org Description: Now it's impossible to configure a local printer is it's not detectedn why? Use Case: my friend come at my home with his 11.4 install and ask me to configure his USB printer. I can't do it with yast, cups or hpsetup. Years ago I could do with vi, but now it's a bit too difficult with cups to do things by hand Business case (Partner benefit): openSUSE.org: Linux/openSUSE have a lot of printers available. USB or // ones don't need to be connected to be installed if we know all of them. It's very desirable when you try to move some user from windows to openSUSE and have to configure openSUSE when not all the hardware is present. This can be done with any network printer but not with local. I know most local printer are detected and installed nearly automatically, but it's even better if it's done in advance. -- openSUSE Feature: https://features.opensuse.org/312327

1 3

[New: openFATE 311246] Hide loading modules and running services from user
by fate_noreply＠suse.de 19 Jan '12

19 Jan '12

Feature added by: Sławomir Lach (Lachu) Feature #311246, revision 1 Title: Hide loading modules and running services from user openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Add new PolicyKit enabled deamons to load/stop services and load/unload kernel modules. For outdated tools, we can add running dbus oriented service into running script, like OpenOffice will automatically starts CUPS service on startup, but when OO will be integrated too, we will remove automatically start of CUPS from script. Use Case: Mathew is running VirtualBox installed from standard repository. After run PolicyKit will asks to password to load VirtualBox kernel modules. Business case (Partner benefit): openSUSE.org: Actually many programs will need more dbus oriented service starting. VirtualBox will need load additional module. Actually many services started unnecessary, when it should start on dbus activation(with enhancement of policykit). We can add start of CUPS command to script starting our program. -- openSUSE Feature: https://features.opensuse.org/311246

1 6

[openFATE 313143] YaST LDAP client refactor/cleanup
by fate_noreply＠suse.de 19 Jan '12

19 Jan '12

Feature changed by: Jiří Suchomel (jsuchome) Feature #313143, revision 5 Title: YaST LDAP client refactor/cleanup openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Ralf Haferkamp (rhafer) Partner organization: openSUSE.org Description: Jiri (jsuchome) an I recently discussed some cleanup work we'd like to see in the YaST ldap-client module. This feature lists the main items we'd like to see reworked to improve the Module: Remove no longer needed UI elements Candidates are: * The TLS/SSL checkbox (sssd has a hard requirement for SSL/TLS) * The "LDAP Version 2" checkbox in the advanced settings. (there is AFAIK no LDAPv2-only Server implementation left) * The "Use LDAP but Disable Login" Radio Button Restrict the UI to handle only really LDAP client related things Currently the UI contains quite some settings which are not strictly related to LDAP client (nss/pam) setup. Over the year ldap-client became a bit of a disposal site for all kinds of LDAP related things, which made the UI a bit hard to understand. We should move some things to YaST modules where make a better fit. This is mostly about the settings currently available in the "Administration Settings" Tab (in "Advanced Configuration") * The Password Policies settings seem to fit better into the ldap- server module which already contains some of this functionality * Default Configuration Objects for other YaST modules (e.g. mail, dns, dhcp). Where possible the need for those special configuration objects should be removed. When a specific service still requires those configuration objects the YaST module for that service should be able to handle those objects it self (we could still offer utils API for that in yast2-ldap/ldap-client). E.g. the user management related object should be configured from inside the yast2-users module. yast2- ldap-server could offer to create default objects during the initial LDAP server setup. * The Home Directories on This Machine checkbox seems to be better suite in the Users module as well. * The rest of the values which go to /etc/sysconfig/ldap could be written by yast2-ldap-servers. We still need to figure out how to setup /etc/sysconfig/ldap on machines which to not run the LDAP Server but need access to those settings. (yast2-mail, -dns-server, -dhcp-server) * Adapt the API: move the LDAP* functions from ldap-client (impact on other modules!) Relations: - related feature (feature/id: 313142) + Discussion: + #1: Jiří Suchomel (jsuchome) (2012-01-19 10:15:11) + 1. Removing TLS/SSL is based on assumption that we configure SSSD only, + which is feature 313142. + 2. About The "Use LDAP but Disable Login" Radio Button: did we agree on + some replacement of it? I cannot remember... -- openSUSE Feature: https://features.opensuse.org/313143

1 0