December 2009 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 308458] Include Google Akonadi resource package for KDE 4
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Todd R (TheBlackCat) Feature #308458, revision 1 Title: Include Google Akonadi resource package for KDE 4 openSUSE-11.3: Unconfirmed Priority Requester: Desirable Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Todd R (theblackcat) Description: Since August there has been an Akonadi resource that allows KDE users to sync their google calendars with their KDE korganizer calendars and sync their google address book with their KDE kaddressbook. It is an extragear program, meaning it is hosted on the official KDE servers. However, it is not present in any of the official openSUSE KDE repositories. Considering how common use of Google calendars and gmail seems to be, I think it would be very useful to people to provide an official package for the software. Here is the release announcement: http://www.kdedevelopers.org/node/4049 -- openSUSE Feature: https://features.opensuse.org/308458

1 2

[New: openFATE 308273] Community repositories" should be default selction when adding repository
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Birger Kollstrand (MrKane) Feature #308273, revision 1 Title: Community repositories" should be default selction when adding repository openSUSE-11.3: Unconfirmed Priority Requester: Mandatory Requested by: Birger Kollstrand (mrkane) Description: Currently the default selection in Yast->Software Repositories->Add is the Specify url" choice. >From a usaability point the "Community repository" should be default choice. 1. It is easier for a newcommer to selct in a list, rather than typing in a url. 2. I would guess that a large portio of the users would like to add excisting repositories in that list anyway. http://bugzilla.novell.com/show_bug.cgi?id=549362#c1 (http://bugzilla.novell.com/show_bug.cgi?id=549362#c1) -- openSUSE Feature: https://features.opensuse.org/308273

1 2

[openFATE 307256] openSUSE Developer Network
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Sascha Manns (saigkill) Feature #307256, revision 1 Title: openSUSE Developer Network openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Sascha Manns (saigkill) Description: Hello Mates, today i get an Idea for our Project. We can create an new Project like MSDN (Microsoft Developer Network) specially for OpenSUSE. I thought we can make an DowloadSite (1-Klick) for needed Software. Another Tab includes the API RReferences from KDE4, GNOME and other Stuff. In the Tab Learning we can include some HowTo's for Programming. That's just an thought. Maybe you like it... Sascha -- openSUSE Feature: https://features.opensuse.org/307256

1 7

[openFate 305725] Use gettext for gconf schemas translations
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Vincent Untz (vuntz) Feature #305725, revision 1, last change by Title: Use gettext for gconf schemas translations openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Vincent Untz (vuntz) Partner organization: openSUSE.org Description: The translations of all the descriptions of gconf keys in schemas are already in the gettext files of the application. Removing them from the schemas would make the packages smaller and would possibly improve gconf performance in normal usage (ie, outside of gconf-editor, where the descriptions are used). Martin Pitt and I talked about this, and Martin has implemented it for Ubuntu: https://bugs.launchpad.net/bugs/123025 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305725

1 5

[openFATE 306310] Improve Section About Keyboard Configuration
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Karl Eichwalder (keichwa) Feature #306310, revision 1, last change by Title: Improve Section About Keyboard Configuration openSUSE-11.2: New Priority Requester: Desirable Requested by: Karl Eichwalder (keichwa) Description: What about explaining here how to add the Euro sign to e.g. the 5 key on the keyboard... And what to do with the 'Win/Start' key. Should it be Meta, Hyper, Super, etc? What is the difference? http://doccomments.provo.novell.com/admin/main?/admin/viewcomment/10258 References: http://doccomments.provo.novell.com/admin/main?/admin/viewcomment/10258 Comment: 8174 http://www.novell.com/documentation/opensuse110/opensuse110_startup/data/ch… Customer email: beheer at vahsen dot nl Customer name: Rob Vahsen -- openSUSE Feature: https://features.opensuse.org/306310

1 2

[openFATE 306508] external checksum for supplied files
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Marcus Meissner (msmeissn) Feature #306508, revision 1 Title: external checksum for supplied files openSUSE-11.2: New Priority Requester: Desirable Requested by: Marcus Meissner (msmeissn) Description: (on behalf of Elmar Stellnberger) I would appreciate the OpenSuse-project to keep sha-1s/md5sums of all valid files as other professional OS vendors do (Microsoft, Apple). I believe the effort to implement this would not be too high; the creation of an automatic cheksum list could be implemented in the build service (see also: https://bugzilla.novell.com/show_bug.cgi?id=491193). To me keeping such a list is the only way to verify that a system is clean because in my case attackers succeeded to alter the checksum table of the rpm database (rootkit was additionally not found by any antivirus sw i.e. clamav, norton, chkrootkit, etc.). Without such a checksum table I had to recreate a plain installation by hand (i.e. some self written script) by redownloading exactly the same realease and package versions from the same source as they had been drawn originally from in order to compare both roots: very cumbersome, laborious (about 2000 packages) and error prone; some packages from Packman differed although they were of same version, release and download URL; others were not available any more. I believe maintaining such a checksum table would be a true win for the Opensuse project in means of security and error reporting. Relations: - provide boot cd to md5sum core system files (novell/bugzilla/id: 491193) https://bugzilla.novell.com/show_bug.cgi?id=491193 -- openSUSE Feature: https://features.opensuse.org/306508

1 13

[openFATE 305946] NetworkManager - Autoselect correct peap version
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Helmut Schaa (hschaa) Feature #305946, revision 1, last change by Title: NetworkManager - Autoselect correct peap version openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Helmut Schaa (hschaa) Description: If no peap version is specified wpa_supplicant will already choose the right one. However, NetworkManager does not make use of that feature yet. It would be much easier for users to select peapversion "Auto" instead of having to know if the authentication server allows version 0 or 1. The peap version selection should still be possible as the user may restrict the connection to a specific peap version. Hence, I suggest a drop down combo with the items "Auto", "version 0" and "version 1". -- openSUSE Feature: https://features.opensuse.org/305946

1 4

[openFATE 306330] Creating .document files for PDF and HTML
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Karl Eichwalder (keichwa) Feature #306330, revision 1, last change by Title: Creating .document files for PDF and HTML openSUSE-11.2: New Priority Requester: Mandatory Requested by: Karl Eichwalder (keichwa) Description: To make PDFs visible in yelp, we need .document file; for more information, see fate#306322. The same is valid for HTML output. All I need is the title in the "Name" entry of a .document file. The rest I'll create at packaging time with my script. "make package" resp. make package-html resp. "make package-pdf" must create these files. As the file name I propose to use $(BOOK)_$(LL).document. -- openSUSE Feature: https://features.opensuse.org/306330

1 4

[openFATE 305851] Include kiwi-ltsp in Factory
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Stephan Kulow (coolo) Feature #305851, revision 1, last change by Title: Include kiwi-ltsp in Factory openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jigish Gohil (cyberorg) Description: I've been maintaining KIWI-LTSP: LTSP5 implementation on openSUSE using KIWI in server:ltsp Build Service repository, now it is at the stable and production ready state. This is request to include the packages(not all of them) in openSUSE Factory, and possibly 11.3 later. Relations: - Include kiwi-ltsp in Factory (novell/bugzilla/id: 474360) https://bugzilla.novell.com/show_bug.cgi?id=474360 Discussion: #1: Jigish Gohil (cyberorg) (2009-02-10 08:42:08) Should this have gone on https://features.opensuse.org/ ? #2: andrea florio (anubisg1) (2009-02-10 09:16:58) +1 for me... kiwi-ltsp is great and works fine! #3: Shrenik Bhura (sbhura) (2009-02-11 05:20:31) The inclusion will largely serve as an impetus for further development of this great project. With increased exposure, the motivation to deliver a quality project shall also increase. #4: Ken Yap (ken_yap) (2009-02-11 06:31:44) Yes, please include it in OpenSUSE, it will make OpenSUSE more attractive to people who want to build thin client clusters. #5: Stephan Kulow (coolo) (2009-02-11 06:53:23) why not Factory:Contrib? And I agree with #1 Having it in Factory means currently that someone from novell needs to review them and that's why we created contrib where everyone capable can maintain packages that go with a specific openSUSE release. And for having it on the DVD it's a bit too special use case, so it would be online repo only anyway. #6: Jigish Gohil (cyberorg) (2009-02-11 07:00:00) Not on the DVD, but Factory and OSS online repo. Instead of Contrib isn't current location - server:ltsp more appropriate? Idea is to include it officially in the distribution. I am sure we can make a same kind of arrangement we have in place for compiz to maintain this as well. -- openSUSE Feature: https://features.opensuse.org/305851

1 8

[openFATE 306895] Gnome-main-menu improvements
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Atri Bhattacharya (badshah400) Feature #306895, revision 1 Title: Gnome-main-menu improvements openSUSE-11.2: Unconfirmed Priority Requester: Mandatory Requested by: Atri Bhattacharya (badshah400) Description: For openSUSE 11.2, it would be very useful if gnome-main-menu could be improved feature-wise and also performance-wise. Several common features that need to be implemented are as follows: 1) Right click menu to clear recent documents, recent places, etc in the main-menu slab. Important for privacy purposes. 2) Relabelling of YAST to Administrator settings in the main menu slab. 3) Adding frequently used shortcuts to the gnome-control-centre slab. At the moment the commonly used tasks in the gnome-control-centre only has a shortcut to 'set preferred applications'. Other commonly used shortcuts like user-account prefs, etc might be very useful. Performance-wise the main-menu is a lot faster and responsive today than in 10.3, except during the first startup of the application-browser slab after a restart or log-in. This takes a few seconds, and this time taken increases with increasing number of applications (tested on 11.1). -- openSUSE Feature: https://features.opensuse.org/306895

1 6

[openFATE 307359] Create openSUSE Specific Branding for WebYaST
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Andreas Jaeger (a_jaeger) Feature #307359, revision 1 Title: Create openSUSE Specific Branding for WebYaST openSUSE-11.2: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Description: Create an openSUSE specific branding for WebYaST. -- openSUSE Feature: https://features.opensuse.org/307359

1 5

[openFATE 306337] Partitioning with non-standard disk geometry
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Herbert Graeber (hgraeber) Feature #306337, revision 1, last change by Title: Partitioning with non-standard disk geometry openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Herbert Graeber (hgraeber) Description: For SSDs it is important to respect their erase block size (usually 128KB). So instead of using the standard sectors per track of 63 and 255 heads Theodore Ts'o suggests to use 56 and 224 instead to get a cylinder size which is a multiple of 128KB. Similar tricks may be neccessary to achive optimal cylinder sizes for devices which are used for raid partitions. It would be useful, to have the ability to specify the values for sector per track and heads in the expert before any partition is defined. For special cases, like SSDs it would nice, if proper values will be suggested. Theodore Ts'os Blog: Aligning filesystems to an SSD’s erase block size (http://thunk.org/tytso/blog/2009/02/20/aligning-filesystems-to-an-ssds-eras…) -- openSUSE Feature: https://features.opensuse.org/306337

1 12

[openFATE 306984] Create a Single way of Managing NIC Devices
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Scott Couston (zcnnnnzc) Feature #306984, revision 1 Title: Create a Single way of Managing NIC Devices openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Scott Couston (zcnnnnzc) Description: In Opensuse 11.1 the decision was made to remove Yast control of Network Manager. This created 2 semi-dependant ways of managing Network Interface Cards, that in retrospect offered poor or impossible singular control. This decision may have had technical merit however it created a huge deal of complication and bugs as a result. At this time KDE4 NM was not available and KDE3 NM was the only form of NM available to this version of openSuse. In the case where NM is selected over IFUP, other dependant Yast Applications offered no control over the NIC and IP itself. Take the small example of the Yast Firewall. If NM was selected over IFUP, the Yast Firewall offered NO control over the IP. If NM is selected over IFUP, the NIC(s) as a devices, offered no control as Yast defines all dependencies over NIC(s) as a device or multiple devices. If NM is selected over IFUP during Installation, there was no facility to input static IP's or effect any control over NM as Installation only offered the user to choose the alternate NM but not configure it. Poor or No testing of a PC that was on a LAN where NO DHCP Services were offered was obvious. Without DHCP Services, it was not possible to Install updates as IFUP could not provide nominated DNS Services. IFUP could only set a static IP, but failed to provide DNS Services despite being present in IFUP's configuration. NM also suffered at the fate of DHCP Services. Despite Static Services being present in NM, the presence of DHCP Services overruled static entries in NM as these were ignored. NM only provided static services so configured, when DHCP Services were Not present. The control over NIC cards became a total IF issue. Any variant from IFUP using DHCP Services and the LAN also providing them, meant we lost control over the NIC(s).* We need to decide IF we need to maintain both IFUP and NM for control over NIC(s) as of 11.1 we offer almost NO control over any variant so configured* The downline application to configure WIFI, VPN, IPV6 etc are all compromised. 2 totally different methods of applying downline services need provision for the rest of further developments. I do not think it is realistic for us to continue to maintain both IFUP and NM as the down line repercussions are so huge and without control over an IP and DNS we might as well stop development. It is not sufficient to depend on DHCP Services always being present as we then assume a condition that may not be set. This would be akin to stating in the"Installation Requirements" and adding a line stating that OpenSuse requires DHCP Services to be present for the software to "Install and Function Correctly" Either we dump NM or IFUP. Certainly unless Yast can control NM it must go OR if we want to take the other down-line services of VPN, WIFI, IPV6; IFUP must go. Request for Comment needs to start, both in the technical requirements of a singular control and the usability of same. The above statements are all supported by various bugs, mostly opened by the author. Any Commnts please? -- openSUSE Feature: https://features.opensuse.org/306984

1 2

[openFATE 307116] support hauppauge wintv hvr h900
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Josef Siegel (emmentaler) Feature #307116, revision 1 Title: support hauppauge wintv hvr h900 openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Josef Siegel (emmentaler) Description: There are sources in the source tree which told me that there could be support for that USB device. But nobody seems to be responsible. Would be very nice, if someone could take the chance. -- openSUSE Feature: https://features.opensuse.org/307116

1 1

[openFATE 307197] Mencoder Graph Client
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Flex Liu (winddss) Feature #307197, revision 1 Title: Mencoder Graph Client Requested by: Flex Liu (winddss) Description: This is a front-end of the "mencoder" ( a video & audio encode transfer tools. based on gtk & gnome-desktop. you'll use it to change the video or audio encode easier than the command line mode. -- openSUSE Feature: https://features.opensuse.org/307197

1 4

[openFATE 306910] Add the possibility to enable Roaming Home Directories in the YaST Samba Client
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Andreas Schneider (gladiac) Feature #306910, revision 1 Title: Add the possibility to enable Roaming Home Directories in the YaST Samba Client openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Andreas Schneider (gladiac) Description: There should be the possibility to enable Roaming Home Directories with pam_csync in the YaST2 Samba Client module. pam-config has support to setup pam_csync. The YaST module has to change the config file (ini) from pam_csync and run pam-config. Test Case: Login to your Active Directory account. Check if the configuration files have been synchronized to the ADS. Use Case: Roaming Home Directories is the missing piece of the SUSE Active Directory Integration. This feature was planned already for SLE10 and should be possible in one of the next SUSE products. -- openSUSE Feature: https://features.opensuse.org/306910

1 2

[openFATE 307415] Back to the old GDM 2.20 branch, the version with gdmsetup
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Everaldo Canuto (ecanuto) Feature #307415, revision 1 Title: Back to the old GDM 2.20 branch, the version with gdmsetup openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Everaldo Canuto (ecanuto) Partner organization: openSUSE.org Description: The new GDM is ugly and miss lots of features available in previous versions, look at web gdm web site (http://live.gnome.org/GDM) we can see that old branch still maintained: "A rewrite of GDM is underway. On 15 October 2007, the new design replaced the existing SVN.w/ gdm-setup) trunk At the moment, this rewrite provides a functional login program, but is missing some features which are in the last stable (2.20) branch. It would be great if more people could get involved to help complete the rewrite. The existing stable branch will continue to be maintained with bug fixes until the rewrite is ready. Apologies for any inconveniences this causes while we are working on this rewrite." So, why we dont get back to old branch and wait until "rewrite" get done. Business case (Partner benefit): openSUSE.org: Because new GDM used in openSUSE 11.1 and openSUSE 11.2 lack lots of features already available in old versions of openSUSE. Also, lots of people what to have gdm-setup back, artists want to make new gdm themes and well, new gdm just sucks and is ugly. -- openSUSE Feature: https://features.opensuse.org/307415

1 6

[openFATE 306992] Zypper dup needs a --lock-vendor <vendor> switch
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Dave Plater (plater) Feature #306992, revision 1 Title: Zypper dup needs a --lock-vendor <vendor> switch openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Dave Plater (plater) Description: When using zypper dup it is very difficult and sometimes impossible to prevent certain packages from changing vendor. I propose a switch which will prevent certain vendors from being changed. Packman for instance has kaffeine and cairo. You have packman kaffeine installed and you wish to stay with the packman version but you wish cairo to stay opensuse. You can either give packman repo a higher priority in which case your cairo will change vendor or you can give opensuse repo a higher priority in which case your kaffeine will change vendor. Performing a "zypper dup --lock-vendor packman" will enable you to have a higher priority opensuse but still keep your packman packages and update with newer packman packages. -- openSUSE Feature: https://features.opensuse.org/306992

1 6

[openFATE 307189] Keyboard variants during setup and Euro sign
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Peter Tselios (tpe) Feature #307189, revision 1 Title: Keyboard variants during setup and Euro sign openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Peter Tselios (tpe) Description: A nice to have feature for future versions of openSuse would be the option to add more than one keyboard layouts during setup. Additionally, it would be nice to automatically (during setup) configure the X and console in order to be ready to use the Euro sign. This could be done either by the language selection (not very safe because some people use English anyways) or (more precise and safe) by the timezone selected by user. I believe that this feature would be helpful for European users. -- openSUSE Feature: https://features.opensuse.org/307189

1 1

[openFATE 306994] Create a strong DE-neutral system/profiles
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: dmitry serpokryl (dmitry_serpokryl) Feature #306994, revision 1 Title: Create a strong DE-neutral system/profiles openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: dmitry serpokryl (dmitry_serpokryl) Description: it's just a response to the (http://lizards.opensuse.org/2009/07/31/openfate-feature-306967-kde-default) yet another proposed feature which i hope never will be accepted as a default. my response is in the 3-rd comment. suppose that the creation of a more flexible and DE-neutral system/settings/presets could benefit to all SLE/SUSE Users. examples: * pure GTK Desktop * pure Qt Desktop (why not?) * no Mono preset (we can easily use Tracker instead of Beagle and at least gNote/others to wipe out the Tomboy+Company) * no Java preset (mostly targeted to the OOo replacement option by Gnumeric+AbiWord) * Wicd instead of NM * more attention to the low-level core components like kernel, drivers, basic libs and so on. -- openSUSE Feature: https://features.opensuse.org/306994

1 2

[openFATE 307257] Default kdesu to use sudo and not su
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Bill P (google01103) Feature #307257, revision 1 Title: Default kdesu to use sudo and not su openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Bill P (google01103) Description: as described in the article http://www.benkevan.com/blog/default-kdesu-to-use-sudo-and-not-su/ -- openSUSE Feature: https://features.opensuse.org/307257

1 1

[openFATE 306373] revival of openCA
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Stephan Kulow (coolo) Feature #306373, revision 1, last change by Title: revival of openCA openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Hans Witvliet (digi_hans) Description: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060425 SUSE/1.5.0.3-7 Firefox/1.5.0.3 Any chance of reviving OpenCA? In the security manuals, chapter x509, it says that the yast-module for maintaing certificates is nice for small set-up's, but not intented for large roll-outs. OpenCA seems to be right for that job, with (poosible) seperate CA, RA, OSCP, support for smartcards and LDAP, mysql. If i'm not mistaken, Adrian maintained some time ago an old version of OpenCA for openSuSE_10.3. Hence my question: is it possible to re-create it for the 1.0.2 (ten-ten) version of openCA, preferably for openSUSE_11.1 and SLES-11 ? It seems that current verion of OpenCA does build on older versions of openSUSE, but fails to compile on 11.1. (not yet tried on sles11, but expect same results) Relations: - revival of openCA (novell/bugzilla/id: 491024) https://bugzilla.novell.com/show_bug.cgi?id=491024 Discussion: #1: Stephan Kulow (coolo) (2009-04-08 09:11:05) if you can't even get it to compile, it doesn't seem to be that well maintained. So I would think it's not good to rely on security of it. #2: Hans Witvliet (digi_hans) (2009-04-08 16:19:04) To put in perspective... I couldn't complete a compile of the latest version on 11.1. openca offers binaries for fedora, centos, ubuntu and open slowaris. I just tried it on 32/64-bit versions of 11.1, I can try it aagain on older versions. Allthough i just upgraded our whole environment, using our install server with xen farm wouldn't take too long. At work i've got a tough job keeping all the noses point to one direction. But it would be hard to defend sticking with open/sles with considerable effort if it compiles flawless (I kow: seeing is believing..) with others. It seems that OpenCA is the only opensource product in this class, comparing with CASA, yaST, tinyCA, pyCA that are only intended for small scale deployment. And for this particular assigment was specifically asked to evaluate OpenCA, regardless of the environment it runs in, though my first choice would be a sles11-cluster and secondly an open-11.1 cluster. #3: Stephan Kulow (coolo) (2009-04-08 23:58:21) you have two options: a) the openSUSE way: you're free to maintain it in openSUSE:Factory:Contrib (see en.opensuse.org/Contrib) b) the SLES way: you convince your presales contact person that there is no way around The "file an enhancement bug against openSUSE to get a SLES feature" does not work. #4: Hans Witvliet (digi_hans) (2009-04-09 15:22:41) Sorry, if i gave you the wrong impression. imho, openca looks great (from the docu and the live-version) It used to be included 10.0 - 10.3 with the distro itself, and later on it became also available on the OBS (Adrian). I presume that if you got someone who has spent some time before on it, it would be the first one to humbly ask to have a look again, instead of re-inventing the wheel. Personnaly, i work on the R&D department, only doing prototypes and prove-of-concepts and i am happy using openSuSE. Our production department however is using the official SLES-9 and now SLES-10 version. a) So if there is a version on the OBS for open_11.1 i would be happy. b) If it could be incorporated in the list of packages for SLE it would make you happy (sales) c) If the OBS could hold versions for 11.1 and SLE, you would be happier, (sales but no additional packages to officially maintain) Final word about the code: Yes, it is _old_ code, but the only thing that comes close with regards with its features, is the code that comes from AOL: http://www.redhat.com/certificate_system/ And i'm neither eager to switch to rh/fc/ct, nor to suggest a re-write of the 10MB from openCA. Hence my req to revive it on the OBS, anyone would benefit. Or do you have plans to "adopt" the above mentioned GPL-ed java code ;=) -- openSUSE Feature: https://features.opensuse.org/306373

1 3

[openFATE 306779] a better support for Wlan driver
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Claus Rebler (Zunami) Feature #306779, revision 1 Title: a better support for Wlan driver openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Claus Rebler (zunami) Description: i have always a problem to install wlan drivers on opensuse i hab 1 acer laptop 1 hp laptop 1 asus latop and always the sam problem. the system have not the divers. i must after the system installation (opensuse 11.1) over again to install the driver. and then i must hope to find my network (next problem). when i install kubuntu i have no this problem. please make a easy or better wlan support. and after the installtion the system must be run -- openSUSE Feature: https://features.opensuse.org/306779

1 2

[openFATE 307171] Use Device Manager instead of the standard Device Notifier
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Robert Erne (Jeremay) Feature #307171, revision 1 Title: Use Device Manager instead of the standard Device Notifier openFATE: Unconfirmed Priority Requester: Desirable Requested by: Robert Erne (jeremay) Description: I think Device Manager has a lot of interesting and nice features. It`s rather stable and makes a good impression. -- openSUSE Feature: https://features.opensuse.org/307171

1 3

[openFATE 306949] Clearing Documents List from GNOME Slab Menu
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Eric Yeoh (yeoheric) Feature #306949, revision 1 Title: Clearing Documents List from GNOME Slab Menu openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Eric Yeoh (yeoheric) Description: There is no feature in openSUSE or SLED 11 to clear recently used documents under the GNOME desktop using the Slab Menu. This presents a possible privacy issue. If there is a way to clear via context-menu will be great. -- openSUSE Feature: https://features.opensuse.org/306949

1 1