February 2011 - openSUSE Features - openSUSE Mailing Lists

[openFATE 307498] Improve and Integrate users.opensuse.org across openSUSE sites
by fate_noreply＠suse.de 23 Feb '11

23 Feb '11

Feature added by: Francis Giannaros (apokryphos) Feature #307498, revision 1 Title: Improve and Integrate users.opensuse.org across openSUSE sites openFATE: Unconfirmed Priority Requester: Important Requested by: Francis Giannaros (apokryphos) Description: There is a lot of need IMO for centralisation and improvement with users.opensuse.org and the other websites. This would help in building a community around the project, as it will make it easier to find out who is doing what and where. I really don't think this can be understated either. Things like groups (let's say, KDE devs, Bug triage team, IRC ops), contact details, home: repository in the build service, respective wiki page, and an avatar at the very least should be handled from there. A good example of this working in action (and really _helping_) can be seen on launchpad; i.e. https://launchpad.net/~sabdfl Selecting 'openFATE' because I can't see where else to put this under. -- openSUSE Feature: https://features.opensuse.org/307498

1 5

[New: openFATE 311046] Autoredirect to specify language version wiki
by fate_noreply＠suse.de 23 Feb '11

23 Feb '11

Feature added by: Anton Reznik (reanxp-rus) Feature #311046, revision 1 Title: Autoredirect to specify language version wiki openSUSE.org: Unconfirmed Priority Requester: Important Requested by: Anton Reznik (reanxp-rus) Partner organization: openSUSE.org Description: Can make autoredirect from wiki.opensuse.org to *language*.opensuse.org. As in www.opensuse.org (for me it's autoredirect to www.opensuse.org/ru/) -- openSUSE Feature: https://features.opensuse.org/311046

1 1

[New: openFATE 311065] A radio button "stay login in"
by fate_noreply＠suse.de 23 Feb '11

23 Feb '11

Feature added by: Minh Ngo (Ignotusp) Feature #311065, revision 1 Title: A radio button "stay login in" openSUSE Infrastructure: Unconfirmed Priority Requester: Important Requested by: Minh Ngo (ignotusp) Partner organization: openSUSE.org Description: A radio button "stay login in" in authorization form (like this http://img.flashtux.org/img132db222350dx1203e659.png ) Business case (Partner benefit): openSUSE.org: With the help of this radio button, there is no need to log in after restarting your browser -- openSUSE Feature: https://features.opensuse.org/311065

1 4

[New: openFATE 308352] Easy Way to put Media to USB Stick
by fate_noreply＠suse.de 23 Feb '11

23 Feb '11

Feature added by: Andreas Jaeger (a_jaeger) Feature #308352, revision 1 Title: Easy Way to put Media to USB Stick openSUSE-11.3: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Description: Currently a user has to run "dd" to copy an ISO image from file system to media - and this runs the risk that the user destroys the harddisk instead of the usb stick. We should create some simple ways to do the copy. Some options: a) A shell script that checks for one attached USB stick and copies the image over to it. b) A boot entry on the media to copy the image to an attached USB stick. Option b) would allow me to download and create the image on one machine and then put it to use on another one. -- openSUSE Feature: https://features.opensuse.org/308352

1 18

[New: openFATE 310123] create NET and DVD isos suitable to USB-boot
by fate_noreply＠suse.de 23 Feb '11

23 Feb '11

Feature added by: Bernhard Wiedemann (bmwiedemann) Feature #310123, revision 1 Title: create NET and DVD isos suitable to USB-boot openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Bernhard Wiedemann (bmwiedemann) Description: In the past years, netbooks and other computers without a CD/DVD drive have become more common. While there is http://en.opensuse.org/SDB:Live_USB_stick , there has always been some confusion among users on which openSUSE iso images are suitable for USB boot and on how to get them working. People have been finding out the hard way that DVD and NET isos can not be used as easily. However, at least for NET isos, this can be changed by running isohybrid openSUSE-NET-...iso DVD isos can be made bootable this way, too, but there is some extra work involved to make it find its data. If this does not have disadvantages, iso images should be adjusted during the creation process to make them bootable from USB-storage devices. It is also good to be able to "dd if=/dev/dvd of=/dev/sdX bs=1M" This feature complements (i.e. is orthognal to) https://features.opensuse.org/310029 https://features.opensuse.org/309238 -- openSUSE Feature: https://features.opensuse.org/310123

1 6

[New: openFATE 309261] Hardware Compatibility test before installation starts
by fate_noreply＠suse.de 23 Feb '11

23 Feb '11

Feature added by: ryan smith (ryan1414) Feature #309261, revision 1 Title: Hardware Compatibility test before installation starts openSUSE-11.3: Unconfirmed Priority Requester: Mandatory Requested by: ryan smith (ryan1414) Description: I have a feature request for openSUSE 11.3 Before the openSUSE installation starts, openSUSE should first do a hardware compatibility test to check if a computer's hardware(video card, wifi card, printer, scanner, sound card, wireless keyboard, motherboard chipset,webcam,dvd writer, etc) will work correctly and also to check if openSUSE has the drivers to make them work. It could display a list like this: video card:nvidia 4353 Compatible/Driver not included sound card:Sound Blaster 3455 Compatible/Driver included If a driver is not included, users can look on the internet to see if there is a driver available. Once the hardware compatibility test is done and everything is going to be compatible, openSUSE can start the installation. If something/s are not compatible and/or a driver/s are not included, openSUSE can display 2 options for a user to choose which will be Continue installation or Cancel installation. Do you think you could implement this feature in openSUSE 11.3? Use Case: User testing if openSUSE 11.3 is compatible with their hardware before installation starts. -- openSUSE Feature: https://features.opensuse.org/309261

1 6

[openFATE 120340] decouple download and installation
by fate_noreply＠suse.de 22 Feb '11

22 Feb '11

Feature changed by: Oliver Schmidt (spiollinux) Feature #120340, revision 171 - Title: Run download and install in parallel + Title: decouple download and installation openSUSE-10.2: Rejected by Klaus Kämpf (kwk) reject date: 2006-08-09 11:36:10 reject reason: Not possible in 10.2 timeframe Priority Requester: Important openSUSE-10.3: Rejected by Stanislav Visnovsky (visnov) reject date: 2007-08-01 10:25:01 reject reason: Out of time. Priority Requester: Important Projectmanager: Important openSUSE-11.0: Rejected by Jiri Srain (jsrain) reject date: 2008-03-28 13:56:11 reject reason: Out of resources for 11.0. Priority Requester: Important Projectmanager: Important openSUSE-11.1: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-07-11 12:06:35 reject reason: This needs to wait. Postponing. Priority Requester: Important Projectmanager: Important openSUSE-11.2: Rejected by Christoph Thiel (cthiel1) reject date: 2009-06-03 08:43:03 reject reason: No resources for 11.2. Priority Requester: Important Projectmanager: Important openSUSE-11.3: Rejected by Andreas Jaeger (a_jaeger) reject reason: not done Priority Requester: Important Projectmanager: Important openSUSE-11.4: New Priority Requester: Important Requested by: Klaus Kämpf (kwk) Requested by: Peter Poeml (poeml) Requested by: Reinhard Max (rmax) Product Manager: (Novell) Project Manager: (Novell) Engineering Manager: (Novell) Engineering Manager: (Novell) Engineering Manager: (Novell) Developer: (Novell) Partner organization: openSUSE.org Description: Network installation could be improved by running package download and package installation in parallel. References: https://bugzilla.novell.com/show_bug.cgi?id=60844 https://bugzilla.novell.com/show_bug.cgi?id=209799 https://bugzilla.novell.com/show_bug.cgi?id=128050 https://bugzilla.novell.com/show_bug.cgi?id=370457 https://bugzilla.novell.com/show_bug.cgi?id=370054 https://bugzilla.novell.com/show_bug.cgi?id=385711 https://bugzilla.novell.com/show_bug.cgi?id=638191 http://en.opensuse.org/Libzypp/Failover http://metalinker.org/ Fate #300660: Download package groups before install Related Fate #307862: Download multiple packgaes in parallel Use Case: This week i makred a upgrade of Qt libs and other things (install texlive). Yast update qt core and start the download of texlive (~250 MB) Well... the qt-x11 not be upgraded, when i can't start a qt app during the install of texlive because the qt is broken. I use kde and almost all of my applications is qt based. Discussion: #2: Klaus Kämpf (kwk) (2006-08-09 11:36:42) Michael already looked at this. Should be further evaluated for 10.3 #3: Edith Parzefall (emapedl) (2007-07-31 16:56:12) Problem is: what do we do if we lost the network connection when only half the packages are installed? #7: Reinhard Max (rmax) (2008-04-10 11:42:43) (reply to #3) I think this is a general problem for network based installations. Can you elaborate if/why you see this as a special problem when download and installation are running in parallel? #8: Peter Poeml (poeml) (2008-05-19 14:49:53) (reply to #7) For reliable operation of a business critical server, it is a must that packages are downloaded first, before the installation/update is started. Otherwise a network outage can lead to a broken system which is half updated. So if parallel download/install is implemented (for desktop users, maybe...) then please make sure that it is possible to disable it. #9: Reinhard Max (rmax) (2008-05-19 16:01:15) (reply to #8) As we just sorted out on IRC, the current implementation also doesn't allow to complete download before starting installation and the feature proposed here wouldn't make this worse. But as the wish of server admins to have all packages downloaded before starting to install them is very valid, I think we should extend this feature request to contain that requirement as well, and probably rename it to "decouple download and installation". If download and installation are properly decoupled, it should just be a matter of the parameters the algorithm is called with to get one of the following behaviours: * Download and install packages one by one (as it is now) * Keep downloading subsequent packages while installing (as originally proposed here) * Use a fixed-size download cache for flow control between download an installations (in situations where download is faster than installation and disk space is limited) * Download all packages of an update or installation and install them afterwards (as requested by Peter for server admins) #10: Jiri Srain (jsrain) (2008-05-20 10:22:10) (reply to #9) We already do have similar feature: #300660: Download package groups before install #42: Martin Seidler (pistazienfresser) (2010-06-09 20:35:25) (reply to #9) That surgestion of Reinhard Max sound's good. And I would surgest the last (and maybe most stable) variant or at least the situation now as default. How much time could be saved in parallel installation and how much time could be wasted with a system with packages that do not fit together if the download had been broken up during installation of the fist packages? #46: Artur Mustafin (hack2root) (2010-08-26 07:21:27) (reply to #3) I think all installation technology shuld be revised: We should invent globaly visible versioned library store, new packaging system, e.t.c. I think it is must be a simple commit, like this: -begin transaction -installs missing libraries/apps in libary store (multiversional, global, cached) -commit transaction in case of any error: -rollback trasaction #4: Edith Parzefall (emapedl) (2007-07-31 16:57:22) Please reject for 10.3. #5: Duncan Mac-Vicar (dmacvicar) (2008-01-10 16:23:46) This is included in the ZYpp plan for 11.0, however implementation will start after beta. Will keep in evaluation, it depends on other milestones for beta1 #14: Chris Hills (chaz6) (2009-02-16 16:42:06) Is there a feature request to install using both the base and updates repo so that the latest packages available at install-time are used, thus saving bandwidth? #15: Jiri Srain (jsrain) (2009-02-17 08:45:38) (reply to #14) This is how it works for quite some time. Repositories providing patches also provide the packages so that they can be installed directly from the update repositories (provided they contain newer version). #16: Duncan Mac-Vicar (dmacvicar) (2009-06-02 15:18:00) For 11.2 we will focus on flexibility of the download and install order (like installing after everything is downloaded), however parallel stuff should be done after we have this in place. Please reject. #20: Jörn Knie-von Allmen (phisiker) (2009-08-05 12:12:29) (reply to #16) Please do not reject. With a downloadprotocol this should be solvable. The Installtask can poll an that protocol (or be informed by a Signal when a download has ended. This is better then polling. Or if prefering an IPC-Framework: D-BUS. Never mind!). Such problems I had some times often to solve (but in Java) and generally, it isn't so dificult. #21: Ralph Ulrich (ulenrich) (2009-08-05 13:03:25) (reply to #20) Please reject forever: As operating system are sort of highly integrated databases there should be a commit like funcutionality: First download then install (like debian). Otherwise repositories representing a rolling release (factory) will potentially break an updating system. #22: Reinhard Max (rmax) (2009-08-06 16:18:54) (reply to #21) Yes, there are situations where this (optional) feature should better not be used, but that does not mean it should not be implemented, because there are many situations where it can be very useful. BTW, how would "download then install" give you anything near commit- like functionality? Factory could still change on the server while you are downloading and packages could still fail during installation, leaving you with an inconsistent installation. #24: Ralph Ulrich (ulenrich) (2009-08-11 23:42:59) (reply to #22) Yes, "still fail during installation": there is no commit-like functionality But in case of a changed Factory repository there would be an error: zypper dup --download-then-install || ( zypper ref && zypper dup) || ... In this more often case there would be a commit-like functionality #25: Reinhard Max (rmax) (2009-08-12 11:22:08) (reply to #24) I think the most common case is end users installing from mostly static repositories such as the original release and the official updates. That's what I had in mind when I first suggested this feature many many years ago when there was no openSUSE or Factory. So, please don't insist in this feature being rejected just because you don't have a usecase for it yourself. Nobody will force you to use it if you don't want to. #23: Reinhard Max (rmax) (2009-08-06 16:20:58) (reply to #16) As I've explained in comment #9, the different modes of operation would have been possible with a single implementation and different runtime parameters. I think this would actually be easier than implementing the different modes separately, so why hasn't it been considered? #17: Michal Papis (mpapis) (2009-07-04 20:58:23) I think great example here may be Gentoo, there You can chose the way of getting packages, by default download and installation go in paraler, but it is possible to get first sources and then run build/installation. If you are on the default and something breaks, ex. network, Yuo can always resume the last download&installation task. #18: Giuseppe Salinaro (superpeppo89) (2009-07-16 19:37:27) (reply to #17) This idea of gentoo is good... #19: Ján Kupec (jkupec) (2009-07-20 10:59:31) (reply to #18) Guys, as Duncan wrote in c#16, we are already developing the "download all, install all" mode (currently we only have "download one, install one, ..."), and yes, users will be able to choose one of these. This particular feature would be an improvement of the current mode: "download one, install one while downloading others, ...". I hope this clarifies the current status a bit. #26: Eduard Avetisyan (dich) (2009-09-15 09:16:15) (reply to #19) Sorry Jan, I think both "download one, install one, download next, install next..." and " download all, install all" are both MUCH slower than " download one, install one, download next in parallel ". Come on guys, you focused on two SLOW modes and left the only fast one for future, and that's since 5 versions! Why not reserve a couple of hundred MB (customizable) of diskspace and cache the downloads there while installing in the meantime. Hope it's not too late to think of it for os11.2... #27: Michael Kromer (mkromer) (2009-10-23 01:11:45) (reply to #26) Absolutely: I agree with you Eduard. The optimized way is to run a download process while rpm -{i,U} is running in the background, as all resources (Disk I/O, CPU, Net) can get used parallel. The only trick is to keep the installation of following packages on hold, if there is some kind of package which takes longer (like kernel-{default,source}; to keep --requires safe; example: kmp's which rely on the specific kernel version to be installed first, however even this could be developed in an optimized way, as package lists and therefore also package requirements are available at time of download). I think there would even be real great customization options possible like an option such as --download-threads. So if the installation/upgrade can keep up with the downloadspeed you will get *significant* performance. And even if not -> it could never get slower. #31: Bart Otten (bartotten) (2009-11-08 13:46:41) (reply to #26) Guess it is too late for for 11.2 but I think Eduard and Michael made a good point. This request is old, even before openFATE was for public... #32: Ján Kupec (jkupec) (2009-11-09 11:25:45) (reply to #26) Well, whether we should do one thing first and then the other, that's debatable, but the point is we do want this downloading while installing . The only issue here are the resources and priorities. Now that we have the first, we can hopefully move on to the next for 11.3 #37: Robert Davies (robopensuse) (2009-12-18 15:19:01) (reply to #32) #306966: [Beta2] No Shutdown/Suspend During Package Update https://features.opensuse.org/306966 is proposing making the slow disk Hog option DownloadInAdvance the default claiming practical integrity benefits, so this most popular feature request is needed to be implemented for 11.3 to mitigate end-user annoyance. #38: Duncan Mac-Vicar (dmacvicar) (2009-12-18 16:03:54) (reply to #37) Yeah, like if disk space would be a big problem nowadays compared with battery duration #39: Robert Davies (robopensuse) (2009-12-18 16:40:21) (reply to #38) Some people have netbooks with relatively limited space, SSD's are likely to become more popular to. So it is not just older machines with smaller disks. Improving battery life by reducing the time the disk needs to be spun up rather than idle, is just another reason to offer parallel download/install option. #28: Reza Davoudi (rd1381) (2009-10-27 14:35:07) plz make it so that it be an option in GUI not just command line i am sick of going through cmdline flags and options #29: John Bester (johnbester) (2009-10-29 07:13:05) I think the proposed sulotion will help, but to me this is not the real important issue. The most frustrating issue around installing a small package using YaST is the repository upgrade that must complete before you can do anything. (Unfortunately we do not all have the internet speeds as are the norm in Europe and US). The worst is actually when you have your laptop somewhere where you do not have internet access and have to wait for connection timeouts before you can do an installation. It happened a few times that I just wanted to install a small tool which slipped my mind when I did a clean install (such as midnight commander) quickly so that I can continue with what I am doing. At this point I am not fussed about having the absolute latest security fix - I just need to get going. In any case, I would propose that when you open the package manager, it should kick off a thread to download repository updates into a temp folder. The next time you start the package manader, it can simply replace those repositories for which there are updates available in the temp folder. My reasoning is: If I opened the package manager yesterday and I open it again today (and maybe again later today), why should I always wait a few minutes before I can start selecting packages? Switching off the refresh feature in "Software repostories" is not an option, because it takes too long and you typically do not want it switched off. #30: Reinhard Max (rmax) (2009-10-29 09:59:10) (reply to #29) Please open a new feature request for your proposal, as it is unrelated to the feature that is being discussed here. #33: Fco. Javier Nacher (xiscoj) (2009-12-07 09:39:04) hi, why don't we learn from another package managers?. I usually use smart ( http://labix.org/smart (http://labix.org/smart) ), I think it working mode is the apropiate. It downloads in parallel and after downloading all packages, installs them sequentially, also allows to update channels pressing a button only on demand, so it opens faster. I think that parallel install is not a good choice but parallel download is more than recommended. #34: Duncan Mac-Vicar (dmacvicar) (2009-12-07 11:01:03) (reply to #33) You missunderstood the feature. The feature talks about downloading multiple files at the same time, and installing what is possible to install at the same time. It does not implies that multiple packages are installed in parallel (however it does not discard it). You give no reason when stating that "parallel install is not a good choice". Downloading in parallel is something we will do anyways. However, as we have DownloadInAdvance and DownloadInHeaps, we can download group of packages that form a minimal dependency transaction. I doubt smart has this information. This would allow us to download the maximum amount of packages (either sequential or in paralell) that can be downloaded and installed while leaving the system in a consistent state. Those could be installed in parallel while the next "heap" or group is downloaded. Any error in the next download would leave the system still in a consistent state. So yes, we should learn from smart, yum and others, but we should not just copy, as we don't have all the limitations they do have, and that means we can actually try to improve things. #35: Robert Davies (robopensuse) (2009-12-07 21:21:45) (reply to #34) It is possible to grab the small "odds & sods" together that start being downloaded early in install even if they are logically independant? The trouble I notice on network install, is that there's many small packages not particularly important packages, which don't let the TCP/IP download get to decent speed, making things crawl early on at nowhere near usual bandwidth. So a strategy, like a browser of getting small files in parrallel, whilst mainly wanting those large consistent sets you mention, might make things look pleasingly snappy, rather than naive. Of course if a large package were to be downloaded, as the small ones arrive and are installed noone would complain. #40: Fco. Javier Nacher (xiscoj) (2010-01-28 09:15:41) (reply to #34) hi, I think parallel download good be a good start point, so once you have all the packages you can install without dependency problems and you'll be sure that the system will be consistent. Of course if some packages are not dependant on others could be installed while downloading the rest. But I think this could be more difficult to implement so as first step for this features could be parallel download of packages and the next step parallel install, and maybe the first step would be easier and faster to implement for 11.3 and the second step can be delayed for next opensuse version. Improving is always good :) #36: Robert Davies (robopensuse) (2009-12-10 16:21:39) Testing out Kubuntu 9.10, and one of early things it does on starting Konqi, is suggest installing "restricted" multia-media codecs. The downloads were fast, stating off at full 10Mb/s, just tailing off a touch after a while. Similarly installing 110 bug fix updates took only a few minutes, despite requiring full kernel download. By comparison, though zypper itself is fast searching in DB, getting the repo info and sequence of small files, can really keep the end user waiting with alot of under-utilised bandwidth. #41: Thiago Sayao (sayao) (2010-06-03 03:29:13) https://bugzilla.novell.com/show_bug.cgi?id=609276 (https://bugzilla.novell.com/show_bug.cgi?id=609276) Anyone would pick this on Hack Week? I think parallel downloads would speed up things a lot. I could keep downloading when installing so the connection would not close - this would save a lot of "hand-shaking" time. #43: Emmanuel ESCARABAJAL (eescar) (2010-06-29 03:28:38) I've been using SuSE for years, since the 5.x, and been wondering since then why they stop downloading packages while installing the one just finished, as compared to some other distros who keeps downloading while installing what was ready to! Ok, I must admit that in those early days, DSL was just born and 56k connections makes each and every second of time saved quite valuable; is it a reason, now we (quite) all have fat Dsl connections, to tolerate such a waste??? I, personnaly only have a 1k dsl line and it makes a great difference with the 10k line I have at work when speaking of the net install experience ... So Please, make the download process in-interupted Soooooon! #44: nick skeen (ns89) (2010-08-01 17:47:22) This is fine with me, as long as there's some form of limiting the number of downloads at once, and perhaps some sort of scheduler to decide which ones to download at the same time. #45: Ralph Ulrich (ulenrich) (2010-08-01 22:24:02) To prevent having a half way update done when crashing, if you use openSUSE factory then edit /etc/zypp/zypp.conf commit.downloadMode = DownloadInAdvance #47: Wallacy Freitas (wallacyf) (2010-09-06 18:52:33) I know the installation order of packages is important. But that does not mean having to wait to install a package for now start downloading the next. Downloading and installation are separate tasks. Package "A" was downloaded, the package "A" goes to "queue" for installation, while this package "B" is downloaded, then "C" then "D", etc.. Just use the term "cache", the packets are downloaded regardless of the previous packet has already been installed. So you can even download multiple packages at once. It would also be possible to install more than one at the same time, if in compliance with the dependences of course. The biggest problem of downloading one by one, is time spent with HTTP requests only to start the download itself. Outside we have to expect a package to be installed to start the next request. #48: Jeremy Thornton (leebrad) (2010-09-16 23:19:45) Would it be possible to have a switch option depending on the usage. Simply, by default, especially for the desktop use 1. Download, 2. Que for Install (Install), 3. Begin downloading next file. Call it REAL- TIME mode. Then offer an alternative called BATCH mode which simply downloads all files needed and installs when the entire download is complete, and the downloaded files are kept in cache until all are verified download and installed. This option allows an administrator to choose based on the particular setting of the unit. It could look something like zypper -rt install whatever (REAL-TIME mode) zypper -batch install whatever (BATCH mode) and in the YAST have GUI option to choose at the top before downloading. #49: Edward Cullen (screamingwithnosound) (2010-12-31 21:49:59) As Zypper already knows about dependencies, surely it would be (relatively) trivial to arrange download & install in such a way that if the connection was cut half-way through, the system would still remain consistent? That is, if A require B and B requires A, one would download both before installing them. If, however, X required Z, but Z does not require anything, one would download and install Z while X was still downloading. #50: Enea George (premamotion) (2011-01-23 15:18:59) Like in Ubuntu installation... #51: Glenn Doig (doiggl) (2011-01-25 16:11:12) Allow option to select open suse mirror. It maybe in the same country as you, or has good bandwidth which allows a large number of files in to be processed in a short period of time. Cheers... -- openSUSE Feature: https://features.opensuse.org/120340

1 0

[New: openFATE 311339] service enable framework
by fate_noreply＠suse.de 22 Feb '11

22 Feb '11

Feature added by: Ludwig Nussel (lnussel) Feature #311339, revision 1 Title: service enable framework openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: The chkconfig tool on openSUSE handles enabling and disabling of sysv init scripts and [x]inetd services. e.g. chkconfig apache2 on chkconfig vsftpd inetd This convenience allows us to ship services disabled by default. So installation of packages doesn't automatically cause more running daemons or exposed network services. There are many other kinds of services though so the framework should be extended to handle them as well: - systemd units - dbus services - apache modules - [list more here] Ideally the services should be managed by symlinks like sysv init scripts so no .rpmnew files hurt distro upgrades. -- openSUSE Feature: https://features.opensuse.org/311339

1 0

[openFATE 308813] Gnome slab menu bookmarks editable
by fate_noreply＠suse.de 22 Feb '11

22 Feb '11

Feature changed by: Vincent Untz (vuntz) Feature #308813, revision 3 Title: Gnome slab menu bookmarks editable - Package Wishlist: Unconfirmed + openSUSE Distribution: Unconfirmed Priority Requester: Desirable + Package Wishlist: Rejected by Vincent Untz (vuntz) + reject reason: Not a package wishlist. + Priority + Requester: Desirable Requested by: Drew Kwashnak (dragonbite) Partner organization: openSUSE.org Description: Currently the Gnome slab menu applications are not editable. There is no option to add the application launcher to the desktop or the panel, nor to open the properties for adjusting how it is launched. Use Case: Cheese sometimes does not work unless the command used is env LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so cheese In other situations I would make an application launcher and change the launch command from just "cheese" to shis whole line so it would work. This command was also recommended for Skype. *please note, this webcam is listed on the UVC Webcam list as supported and in Ubuntu and Fedora it has been detected and work with Cheese without any manual modifications. Business case (Partner benefit): openSUSE.org: To bring the flexibility Gnome is capable of, to the Slab menu. This will help others to see the benefits of it and to consider using it in their own distribution. -- openSUSE Feature: https://features.opensuse.org/308813

1 0

[New: openFATE 309159] Reorganize/Add functionality to the Gnome main menu.
by fate_noreply＠suse.de 22 Feb '11

22 Feb '11

Feature added by: Mariusz Bielski (marbpl) Feature #309159, revision 1 Title: Reorganize/Add functionality to the Gnome main menu. openSUSE-11.3: Unconfirmed Priority Requester: Neutral Requested by: Mariusz Bielski (marbpl) Description: Nowadays if we want to launch application that is not in favourite (or recent) group, we have to do 3 steps: open menu, click More applications, and launch it there or search for it with search field - which is not the best example of usability. People are often changing Slab, to traditional menu, and/or to Gnome Do. How about making it like in KDE4 menu, where search field has different functionalities depending on tab on which we are currently. So, if we are in Applications tab, search engine searches for apps. Results are displayed in real time, in the menu itself. Of course it works as incremental search. <a href="http://kimag.es/share/29911151.png">[image] Menu: Searching fo apps.</a> In Documents tab we are searching for files: <a href="http://kimag.es/share/18560681.png">[image] Menu: Searching for files.</a> And in Places tab we are searching for places: <a href="http://kimag.es/share/67970630.png">[image] Menu: Searching for places.</a> There is a problem with this idea, because menu isn't designed to display huge amount of entries. Searching for a "a" string, can result with big number. So maybe in this situation scrollbar <a href="http://kimag.es/share/26285986.png">(r.1)</a>should be implemented, or only first few entries should be displayed in the menu, and rest will be available through "More Applications..." button <a href="http://kimag.es/share/36102822.png">(r.2)</a>. In this case, search string should be automatically copied into Application Browser search field. -- openSUSE Feature: https://features.opensuse.org/309159

1 2