July 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306971] keep the previous kernel after update process
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Ioan Vancea (IonutVan) Feature #306971, revision 1 Title: keep the previous kernel after update process openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Ioan Vancea (ionutvan) Description: I would like to see that "feature" implemented default because after kernel updates many times there were a lot of issues and to change back to the previous version is not very easy for a novice user. For example after a kernel update I have problems with encrypted filesystems, or the sound stopped to work, .... Yes, I know that it is possible to change the behaviour to keep the old kernel but why not to be default. -- openSUSE Feature: https://features.opensuse.org/306971

1 5

[openFATE 306957] Allow ymp (one-click installs) to set the repo priority
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Sven Burmeister (rabauke) Feature #306957, revision 1 Title: Allow ymp (one-click installs) to set the repo priority openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Sven Burmeister (rabauke) Description: When people use one-click installs to e.g. install or update KDE4, they get a lot of dependency issues because the buildservice repo does not have the right priority, i.e. higher than e.g. the oss or update repository. One-click installs only make sense if they are easy to use and facilitate the process of adding a repo. Having to open YaST software management to adjust the priority manually and re-running the update afterwards is not "one-click". Setting-up a repo includes setting the correct priority. The problem with ymp setting repos' priority is that those are relative to the repos already installed. The best solution would be to read the other repos' priority and suggest priorities for the new repos accordingly. The user can still change them in the one-click GUI. The minimal solution would be to just allow the user to set the repo's priority via the one-click GUI. -- openSUSE Feature: https://features.opensuse.org/306957

1 4

[openFATE 306321] disk id change in fstab
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Jean-Daniel Dodin (jdd_sysop) Feature #306321, revision 1, last change by Title: disk id change in fstab openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jean-Daniel Dodin (jdd_sysop) Description: "That basic request is that one or more simple tools be provided to allow a fstab to be automatically converted from /dev/sdaX nomenclature to one of the preferred methods." In other words, its now necessary to use YaST partitionner to change the fstab entry from /dev/sdx to the veeeeeeeeery long disk identification. This is very scary and is now nearly mandatory for updates. So it would be important to have some utility to make only this change in fstab and no other. If possible add the choice to use and set on the fly disk ID. -- openSUSE Feature: https://features.opensuse.org/306321

1 8

[openFATE 306291] ADD ability to launch YaST modules via SystemSettings
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Stephan Kulow (coolo) Feature #306291, revision 1, last change by Title: ADD ability to launch YaST modules via SystemSettings openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Paul Lubetsky (vegeek) Description: It would be better and simplier for novice to have only one configuration panel in the system, both for KDE and general System Administration via YaST. Similiar work was done for gnome: now opensuse has an integrated all-in-one control panel there. I propose to add an Administration tab in systemsettings, which would provide launchers for YaST`s system administration tools. Reproducible: Always Steps to Reproduce: Simply open menu: you`ll find there two different launchers for YaST and SystemSettings. Actual Results: Now SystemSettings and YaST aren`t integrated. Expected Results: User want to do some system administration tasks, he/she opens SystemSettings and opens required configuration tool. Something similiar was in SuSE 10.0 with KDE3.4. Relations: - ADD ability to launch YaST modules via SystemSettings (novell/bugzilla/id: 487611) https://bugzilla.novell.com/show_bug.cgi?id=487611 -- openSUSE Feature: https://features.opensuse.org/306291

1 7

[openFATE 306905] Create simple fallback output when using live CD
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Piotrek Juzwiak (BenderBendingRodriguez) Feature #306905, revision 1 Title: Create simple fallback output when using live CD openSUSE-11.2: Unconfirmed Priority Requester: Mandatory Requested by: Piotrek Juzwiak (benderbendingrodriguez) Description: We all know that a live CD is best to test out the distro. We also know that not every piece of hardware will be discovered correctly (mainly graphic card). I was thinking about including a simple output with text like "if the X server failed to start and you see just a black screen then try sax2 -r 0=vesa" on the TTY1 just after initializing the X server. Many people get discouraged by such simple thing or sometimes they don't even know what to do in such cases. This should be very simple to implement and will help A LOT to users new to linux. -- openSUSE Feature: https://features.opensuse.org/306905

1 5

[openFATE 306418] Bluetooth configuration via YaST
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Joop Boonen (worldcitizen) Feature #306418, revision 1, last change by Title: Bluetooth configuration via YaST openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Joop Boonen (worldcitizen) Description: Corrently is rather complex for a newbee to configue for instance a gps receiver that is connected via bluetooth. Configure /etc/bluetooth/rfcomm.conf rfcomm bind rfcomm0 start gpsd /dev/rfcomm0 It would be helpful is bleutooth and bluetooth devices could be configured via YaST. -- openSUSE Feature: https://features.opensuse.org/306418

1 7

[openFATE 306634] Grey out services in Yast not installed
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Drew Kwashnak (dragonbite) Feature #306634, revision 1 Title: Grey out services in Yast not installed Buildservice: Unconfirmed Priority Requester: Desirable openSUSE-11.2: Unconfirmed Priority Requester: Desirable openSUSE-11.3: Unconfirmed Priority Requester: Desirable Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Drew Kwashnak (dragonbite) Description: Yast lists a lot of configuration options, such as in the Network services section, which users may not necessarily use or knows what it does. This is most likely with newer users to Linux and/or those who are not as involved with system/network administration. I am suggesting that if the related service is not installed (like Samba Server for example) then the configuration option in Yast should be greyed out. It gives a visual indicator of what you don't need to worry about configuring while lets you know what is installed and can be configured. Perhaps users clicking on the greyed-out icons can be greeted with a message giving a brief description of what the service does and offers a chance to install it at that point if they are interested. At that point it could drop them into the software manage screen with the required and recommended services filtered in the package list and the required ones to be already checked off so all the user has to do is click to Accept/Install them. Ultimately when I was trying to configure my openSUSE for the network, for which I am still very new to even though I've learned a lot so far, I was confused by all of the choices and ended up making a bigger mess than accomplishing what I was trying to do. PS: This is my frist openFATE entry. If I am going about this incorrectly please let me know. -- openSUSE Feature: https://features.opensuse.org/306634

1 11

[openFATE 306667] Include Ramlog application
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Glenn Doig (doiggl) Feature #306667, revision 1 Title: Include Ramlog application openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Glenn Doig (doiggl) Description: See article Improve system performance by moving your log files to RAM http://www.linux.com/feature/141231 (http://www.linux.com/feature/141231) http://tofu3.szm.sk/ramlog/ (http://tofu3.szm.sk/ramlog/) (Some info) The Ramlog project lets you keep your system logs in RAM while your machine is running and copies them to disk when you shut down. If you are running a laptop or mobile device with syslog enabled, Ramlog might help you increase your battery life or the life of the flash drive on your mobile device. As a side effect of using Ramlog, you will be less likely to be caught out by a daemon that suddenly starts sending a message to syslog every 30 seconds and saps your battery keeping the hard disk spinning. Rpm: http://tofu3.szm.sk/ramlog/1.1.0/rpm/ramlog-1.1.0-1.noarch.rpm (http://tofu3.szm.sk/ramlog/1.1.0/rpm/ramlog-1.1.0-1.noarch.rpm) Thankyou -- openSUSE Feature: https://features.opensuse.org/306667

1 3

[openFATE 306655] zypper: new command needed
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Sascha Manns (saigkill) Feature #306655, revision 1 Title: zypper: new command needed openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Sascha Manns (saigkill) Description: Today my X-System crashed. So i become an Idea. It would be graeat, if we can implement an Function in zypper, who search the whole RPM-Database, and detects Errors with the installed Packages. And if he found Errors, that he connects to the Net and reinstalls the broken Packages. -- openSUSE Feature: https://features.opensuse.org/306655

1 8

[openFATE 306324] Improvements to Failsafe mode
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Rajko Matovic (rajko_m) Feature #306324, revision 1, last change by Title: Improvements to Failsafe mode openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Rajko Matovic (rajko_m) Description: Currently when kernel fails to load, user can only give up on installing openSUSE. Failsafe mode can help sometimes, but load of kernel parameters can introduce problems later. Knoppix offers alternatives that may work on particular hardware without going trough process of discovery of proper kernel parameters, and it has help pages available right from the boot screen. Both combined make booting possible with very little to no experience in kernel issues. -- openSUSE Feature: https://features.opensuse.org/306324

1 5

[openFATE 306902] Scripts by the users
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Jan Gerrit Marker (JanGerritJose) Feature #306902, revision 1 Title: Scripts by the users openSUSE-11.3: Unconfirmed Priority Requester: Neutral Requested by: Jan Gerrit Marker (jangerritjose) Description: There some problems which could be solved easily by shell scripts (like deleting plasma-appletsrc if something is wrong with plasma). But nobody knows it and suddenly there are 10 questions about problems with Plasma in 10 forums which all could be fix by deleting plasma-appletsrc. There could be a webinterface where users could upload their scripts. There would be a description of the actions of the script and the problem, they try to fix. Users could use a YaST module to search for a script which fixes the problem, download it and execute it. There could be a voting system about the scripts: solved the problem fast, not so fast, did something wrong and so on. To ensure that the scripts don't destroy the system there could be two categories: "Tested", "Untested". Trustable openSUSE-Members could move the scripts from "Untestes" to "Tested". Or, if there are a lot of good votes for the script, the script would be moved automatically. -- openSUSE Feature: https://features.opensuse.org/306902

1 3

[openFATE 306666] Complete remove-install-update with zypper
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: James Carter (jimc_uclamath) Feature #306666, revision 1 Title: Complete remove-install-update with zypper openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: James Carter (jimc_uclamath) Description: This is a feature request for zypper-1.0.9-0.1.1 in OpenSuSE 11.1. Obviously the improvements would go into a future SuSE release. In my use case, I have 0.5 FTE to spend on system administration of about 120 researchers' workstations and compute nodes running OpenSuSE. My goals involving zypp in order of frequency of occurrence are: apply security patches; install or remove software according to particular research groups' needs; deploy new machines that have no OS on the disc; and upgrade every 18 months to a new distro version. To accomplish these tasks I need to minimize hand labor in package management. What am I trying to accomplish in package management? Software which is not wanted on a machine should be removed if present, and software which is wanted should be installed if absent, plus dependencies, or upgraded to the latest patch version. I suspect that quite a lot of SuSE users, not just me, would like a package management program which could enforce a locally created pattern, automatically removing, adding and updating packages as needed. Back in SuSE 8.2, rug and zypper/libzypp being in the future, I wrote a perl script to make these goals happen. When zypper first came out I investigated it but found it lacking; the lack of a "dry run" (-D) switch precluded testing. But now with the 64bit x86_64 architecture, and with dependencies involving components and version relations, my script is not flexible enough. I again investigated zypper. With the features now present, specifically the -D (dry run) switch, zypper can now do part of my job if shepherded by a lot of supporting scripting. I would like to list features which would make it useful for the whole job. 1) In rare but important cases we need to blacklist or "hold back" updates. Debian has this feature, and even Microsoft Windows can do it. 2) Zypper should have a "negative removal" mode, that is, rather than listing all the packages you want to remove, you list all the packages you want to keep. Zypper will add all their dependencies, and the non-listed packages (including their exclusive dependencies) will be removed. (My new script uses kludge techniques with rpm, not zypper, to do this calculation, but it's hard and time-consuming, 0.125 second per installed package, to deal with dependencies.) 3) Zypper should have an option to be silent about packages already installed. In other words, you list all the packages you want on the machine, and it installs the missing ones, if any. My new script excludes installed packages from the list of wanted packages before feeding the remainder to zypper, but zypper internally could do this much more neatly. 4) I assume that if I take a back-version machine and trick zypper into orienting on a new distro version, it will recognize that a new version is available for every package and take action accordingly. The distro version (and architecture: changing i586 to x86_64) should be selectable on the command line. 5) The YaST installer downloads a package, then installs it, then repeats. (Or perhaps downloading and installation are smartly overlapped.) Zypper should do the same thing, not requiring disc space for every affected package at the same time. To check that all packages can be downloaded, it can do HEAD requests at the start. There should also be a command line option to not be anally retentive about missing packages: if a transient failure prevents downloading, always retry the package (and those requiring it) later, and if the failure is permanent, install as much as you can, don't die on the spot like zypper presently does. 6) Zypper should install packages in dependency order, so if a failure interrupts the process the machine has no missing dependencies, even if wanted packages are missing. I don't know if zypper already does this. The YaST installer, which I assume is based on libzypp, is seen to install aaa_base kind of in the middle of the set of packages, which leads me to bring up this point. 7) Zypper should have options to remove, install or replace packages itself like it does now, but it should also be able to emit a list or table of affected packages that can be postprocessed before installation or removal. For removal this would be package full names; for installation it would be URLs in the repositories (with an option for plain file names instead of file:/// URLs); for updates both items are needed. It would help in a lot of postprocessing situations if you could optionally ask for the package basenames to be prepended as another field; e.g. if the full name is "zypper-1.0.9-0.1.1" the basename is "zypper". Also helpful in setting up the list of wanted packages would be a separate table of dependency relations, e.g. when the output says "AA BB" it means that package AA is required by package BB. Machine readable format is important; you might make an option to pick tabular output or English texts. In my new script to get dependencies I do "rpm -e --test $pkg" and then parse the English output, which is a crock, takes a lot of time, and is unreliable if you ever "improve" the texts. 8) Wherever a list of thousands of packages or URLs can appear on the command line, zypper should also be able to read these from a file. If either kind of list turns up with zero packages, zypper should shut up and install each of them, same as if one or more packages are on the list. 9) Likely zypper already determines the product, version and architecture from /etc/SuSE-release, but there are so many variants of the first line that it's a crock to parse it. Presently you give "VERSION = 11.1" in the second line (with blanks); I would suggest also giving the PRODUCT and ARCH, and without blanks so in a shell script one can do eval `grep '=' /etc/SuSE-release` rather than dumbly using "tr" to make the blanks go away. 10) Likely it is possible to use the Python binding of libzypp to easily write a wrapper script that easily does all of the above requests. (I prefer Perl; can we have that language binding also?) However, I was not able to find documentation to even get started, i.e. to specify the repositories and a list of packages. So my new script reeks of kludges and fails to use zypper (libzypp) for the most important steps. My final request is for documentation on libzypp that I can use for projects of this kind. Related FATE tickets: * 300758 (../300758) : Show orphan packages (rejected in v11.1). Also 306627 (../306627) , a duplicate with a better use case description. * 302159 (../302159) : Only download packages (rejected in v11.1). Just give me the list of URLs; I'll download them on my home DSL connection, distribute on the home net, and then do rpm -F *.rpm. * 305634 (../305634) : Distro version upgrade from the command line using zypper. Hear, hear! My old script could do this. -- openSUSE Feature: https://features.opensuse.org/306666

1 1

[openFATE 306504] LiveCD: Migrate LiveCD desktop settings to installed system
by fate_noreply＠suse.de 08 Nov '10

08 Nov '10

Feature added by: Jakub Rusinek (liviopl) Feature #306504, revision 1 Title: LiveCD: Migrate LiveCD desktop settings to installed system openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jakub Rusinek (liviopl) Description: After successful installation, when finishing session, user should be asked to migrate his settings to the installed system. -- openSUSE Feature: https://features.opensuse.org/306504

1 11

[openFATE 306475] modify Firefox' plugin finder service to search and install from openSUSE repos
by fate_noreply＠suse.de 08 Nov '10

08 Nov '10

Feature added by: Wolfgang Rosenauer (wrosenauer) Feature #306475, revision 1, last change by Title: modify Firefox' plugin finder service to search and install from openSUSE repos openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Wolfgang Rosenauer (wrosenauer) Description: Firefox' plugin finder service searches for missing plugins at mozilla.org and can't provide useful things usually for Linux. The plugin finder service should be improved to know about plugins available for openSUSE and should invoke an installer on request. -- openSUSE Feature: https://features.opensuse.org/306475

1 15

[openFATE 306443] change parted to use Hardware suggested sectors per track
by fate_noreply＠suse.de 05 Nov '10

05 Nov '10

Feature added by: Dean Giles (dgiles) Feature #306443, revision 1, last change by Title: change parted to use Hardware suggested sectors per track openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Dean Giles (dgiles) Description: parted creates partitions which are automatically assigned 63 sectors per track. Hardware, such as HP raid devices, advertise that they want 32 sectors per track. It advertises that through ioctl HDIO_GETGEO. fdisk can utilize the hardware reported sectors per track. parted needs to be changed to do the same. See bug # 501152. Dean -- openSUSE Feature: https://features.opensuse.org/306443

1 20

[openFATE 306641] Manage flickr from the openSUSE Desktop
by fate_noreply＠suse.de 04 Nov '10

04 Nov '10

Feature added by: Karl Eichwalder (keichwa) Feature #306641, revision 1 Title: Manage flickr from the openSUSE Desktop Hackweek IV: Unconfirmed Priority Requester: Important Requested by: Karl Eichwalder (keichwa) Description: For a short into, see http://en.opensuse.org/Flickr -- openSUSE Feature: https://features.opensuse.org/306641

1 4

[openFATE 306975] Sort list of in windows domain membership
by fate_noreply＠suse.de 04 Nov '10

04 Nov '10

Feature added by: Todd R (TheBlackCat) Feature #306975, revision 1 Title: Sort list of in windows domain membership openSUSE-11.2: Unconfirmed Priority Requester: Desirable openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Todd R (theblackcat) Description: Currently, in the windows domain membership module, when you try to join a domain you are given the option to enter a username and password and to select the Machine Account Organization Unit from a list. This list is provided in no apparent order. At the very least it is not sorted by the name of the organizational unit. This may be fine if there is only a small number of them, but for a large institution there might be hundreds, maybe even thousands. It takes a lot of time to search through ever single item on the list to find the one you belong to. I think it would be much easier if the list was sorted alphabetically by the name of the organizational unit, ideally the leaf organizational unit if there is a heirarchy since users may not know that higher nodes their organizational unit belonds to. -- openSUSE Feature: https://features.opensuse.org/306975

1 6

[openFATE 306925] Adjust Colors of the Default Desktop Wallpaper
by fate_noreply＠suse.de 04 Nov '10

04 Nov '10

Feature added by: Rafael Allende (jeaserve) Feature #306925, revision 1 Title: Adjust Colors of the Default Desktop Wallpaper openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Rafael Allende (jeaserve) Description: In GNOME, the color of the default desktop theme and the colors of the default wallpaper do not fit. Especially look at the title bar of the active window. -- openSUSE Feature: https://features.opensuse.org/306925

1 1

[openFATE 306759] Include video editing software - Kdenlive
by fate_noreply＠suse.de 04 Nov '10

04 Nov '10

Feature added by: Glenn Doig (doiggl) Feature #306759, revision 1 Title: Include video editing software - Kdenlive openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Glenn Doig (doiggl) Description: Include video editing software. >From the website - http://kdenlive.org/ Kdenlive is an intuitive and powerful multi-track video editor, including most recent video technologies. Our software is completely free, in all sences of the expression, as defined by the GNU foundation (http://www.gnu.org/) . Using Kdenlive is investing in a community driven project, which aims to establish relationships between people in order to built the best video tools. Other - http://www.linux-mag.com/id/7413/ -- openSUSE Feature: https://features.opensuse.org/306759

1 3

[openFATE 306473] Support KDE initiative to build a brand together
by fate_noreply＠suse.de 04 Nov '10

04 Nov '10

Feature added by: Klaas Freitag (kfreitag) Feature #306473, revision 1, last change by Title: Support KDE initiative to build a brand together openSUSE-11.2: Unconfirmed Priority Requester: Mandatory openSUSE-11.3: Unconfirmed Priority Requester: Mandatory Requested by: Klaas Freitag (kfreitag) Description: Please carefully read http://aseigo.blogspot.com/2009/06/building-brand-together.html Aaron suggests to start combined efforts up- and downstream to create a strong brand for FOSS. Aaron outlines the overall goal: "The desired result is the ability to build a visually identifiable F/OSS desktop brand together , one that fits nicely with your brand as well. This way people can continue to say, "Oh hey, that's $COMPANY $NAME Linux" while giving the human population half a chance to build a relationship with F/OSS itself as a visually identifiable thing.In short: the goal is to increase our net effect in the market by working together." For that, the KDE project is starting to offer a service that helps creating a brand that is fine for both openSUSE and the KDE project. I think we should be an early adoptor here. -- openSUSE Feature: https://features.opensuse.org/306473

1 12

[openFATE 306427] WLAN Driver for eeePCs
by fate_noreply＠suse.de 04 Nov '10

04 Nov '10

Feature added by: Dominik Heidler (dheidler) Feature #306427, revision 1, last change by Title: WLAN Driver for eeePCs openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Dominik Heidler (dheidler) Description: When you are using openSUSE on an eeePC, only unencrypted and WEP Networks are working, because of Asus using a special Version of the Ateros WLAN chipset. You can fix this by installing the Kernel, provided at the end of this thred (http://www.pc-forum24.de/suse-treiber/10335-geloest-ralink-rt2860-unter-ope…) . -- openSUSE Feature: https://features.opensuse.org/306427

1 10

[openFATE 306770] Hiding Interactive Menus within kdm login
by fate_noreply＠suse.de 04 Nov '10

04 Nov '10

Feature added by: John Shand (jshand2008) Feature #306770, revision 1 Title: Hiding Interactive Menus within kdm login openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: John Shand (jshand2008) Description: This would greatly enhance the security of the system as it would prevent the user from logging in in a backwards approach. thus saying this, it would be great if you can create a better security module to include this security feature within the login area. -- openSUSE Feature: https://features.opensuse.org/306770

1 6

[openFATE 306847] Internet Cafe
by fate_noreply＠suse.de 04 Nov '10

04 Nov '10

Feature added by: John Shand (jshand2008) Feature #306847, revision 1 Title: Internet Cafe openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Package Wishlist: Unconfirmed Priority Requester: Important Requested by: John Shand (jshand2008) Description: i am half way through my business plan and have decided that i need Thin Clients and high encryption logons and function working seemlessly. it would make life a lot easier if you only had one server to fix up when things go wrong instead of troubleshooting many. -- openSUSE Feature: https://features.opensuse.org/306847

1 6

[openFATE 306649] Full Google Wave support built in to openSUSE.
by fate_noreply＠suse.de 04 Nov '10

04 Nov '10

Feature added by: Michael Mooney (RaspyYeti) Feature #306649, revision 1 Title: Full Google Wave support built in to openSUSE. Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Michael Mooney (raspyyeti) Description: Ok as you may have seen in the Google I/O demo video, Google Wave is a very powerful new technology that is built around hosted conversations to enable people to communicate and work together in new and more effective ways But it's use will surpass it's creators concept for Wave. My request is for openSUSE to support both Google Wave provider features and Google Wave user features. -- openSUSE Feature: https://features.opensuse.org/306649

1 5

[openFATE 306308] Preview and cancel functions in openFATE edit mode
by fate_noreply＠suse.de 27 Oct '10

27 Oct '10

Feature added by: Rajko Matovic (rajko_m) Feature #306308, revision 1, last change by Title: Preview and cancel functions in openFATE edit mode openFATE: Unconfirmed Priority Requester: Desirable Requested by: Rajko Matovic (rajko_m) Description: Preview button - adds user comment, reply, usecase, testcase but leaves edit window opened, so that user can change layout. Cancel button - quits edit mode and drops all changes. -- openSUSE Feature: https://features.opensuse.org/306308

1 11