September 2011 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 312672] create an android "osc" app
by fate_noreply＠suse.de 11 Nov '11

11 Nov '11

Feature added by: andrea florio (anubisg1) Feature #312672, revision 1 Title: create an android "osc" app Buildservice: Unconfirmed Priority Requester: Important Requested by: andrea florio (anubisg1) Partner organization: openSUSE.org Description: i believe that with the new smartphones and tablets worlds, is more and more important be able to work from everywhere. I would suggest to create and android app that will support most of the osc features.. (without a build feature of course) with particular attention to tablets. -- openSUSE Feature: https://features.opensuse.org/312672

1 1

[New: openFATE 308357] Replacement for Sax2 in 11.3
by fate_noreply＠suse.de 11 Nov '11

11 Nov '11

Feature added by: Tara Ikeda (TaraIkeda) Feature #308357, revision 1 Title: Replacement for Sax2 in 11.3 openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Tara Ikeda (taraikeda) Partner organization: openSUSE.org Description: We need a replacement for sax2 in 11.3, as a safety measure for when auto configuration fails to detect certain monitors/keyboards/mice. Relying on the Desktop Environment for this is not the best idea, as some DE's or window managers dont provide config tools for what you might need to work. So I propose instead of relying on xrandr, Hal, devicekit or whatever there should be a GUI to configure graphics cards, mice, and keyboards without depending on the DE or a WM to provide a tool for the end user. I mention this as I have had KDE 4 fail to detect my resolutions and sometimes keyboard, luckily SAX2 is there to aid me but if its going the way of the dodo then I propose a relacement tool so that the end user wont have to make a xorg.conf and spend some time setting it up. It takes skill to make edits to a xorg.conf file and one can easily mess it up So having a helpful GUI tool is needed sometimes. Business case (Partner benefit): openSUSE.org: Because of new users mainly, because we dont want them to install openSUSE and have it fail to detect their proper monitor resolution and default to a much smaller one. The goal here is ease of use, but also to have a a safety net just in case. With openSUSE being more geared toward KDE a tool like Sax2 becomes even more needed. KDE4's monitor detection tool sucks, its always given me headaches in Ubuntu, in Mandriva, in many other KDE4 distros. It has no feature to remember monitor settings, nor does it do a good job with enabling my resolution. But i am not doing this just for me, many others have issues with KDE4's monitor tool -- openSUSE Feature: https://features.opensuse.org/308357

1 51

[New: openFATE 312275] automated bugreporting - whole system
by fate_noreply＠suse.de 04 Nov '11

04 Nov '11

Feature added by: melchiaros melchiaros (melchiaros) Feature #312275, revision 1 Title: automated bugreporting - whole system openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: melchiaros melchiaros (melchiaros) Partner organization: openSUSE.org Description: It is a nasty jop to report bugs to the openSUSE bugzilla by hand. A automated bugreporting for the whole openSUSE OS like in KDE (drkonqi) would be great. It would save time for the user, improve the frequency of bugreports for the project(I guess many bugs donÂ´t find the way to bugzilla), and a coupling to a stacktrace or logfiles would improve the quality of the bugreports in the openSUSE bugzilla. Good for the user, good for the quality of openSUSE, not so good for a developer(->many work:) -- openSUSE Feature: https://features.opensuse.org/312275

1 4

[openFATE 306578] Zypper integration with BuildService
by fate_noreply＠suse.de 02 Nov '11

02 Nov '11

Feature added by: Brent McConnell (everettemcconnell) Feature #306578, revision 1 Title: Zypper integration with BuildService Buildservice: Unconfirmed Priority Requester: Desirable openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Brent McConnell (everettemcconnell) Description: Integrate zypper with Buildservice so that users can install packages from BuildService directly from zypper without having to leave the commandline. -- openSUSE Feature: https://features.opensuse.org/306578

1 6

[New: openFATE 310046] yast2 progress report when downloadinadvance is set
by fate_noreply＠suse.de 28 Oct '11

28 Oct '11

Feature added by: Guillaume van Baalen (gvanbaalen) Feature #310046, revision 1 Title: yast2 progress report when downloadinadvance is set openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Guillaume van Baalen (gvanbaalen) Partner organization: openSUSE.org Description: This is a feature request for yast2. As of now, when the option "downloadinadvance" is set for package installation, the "perform installation" screen does not report correctly how the overall installation is progressing. What I mean is that there are two progress bars, one showing how much of the current package is being downloaded/installed, and one supposedly showing the overall process. So far, the "overall" progress bar stays at 0% while packages are being downloaded, and shows progress only when actually installing packages once they are all downloaded. I guess it shouldn't be too hard to have the "overall" progress bar go to 50% while packages are downloaded, then going from 50% to 100% while they are installed. Business case (Partner benefit): openSUSE.org: I want this because we have no clue right now as to whether the installation will take seconds or minutes/hours... -- openSUSE Feature: https://features.opensuse.org/310046

1 4

[New: openFATE 309205] Remove old kernel package only after the new one successfully booted
by fate_noreply＠suse.de 25 Oct '11

25 Oct '11

Feature added by: Michal Marek (michal-m) Feature #309205, revision 1 Title: Remove old kernel package only after the new one successfully booted openSUSE-11.2: New Priority Requester: Important Requested by: Martin Barry (supine) Description: When the kernel package is upgraded the old one is immediately removed leaving the currently running kernel with no modules. This breaks anything that requires modules until the user has an opportunity to reboot. The removal of the old package should be delayed till the system is rebooted into the new kernel. Reproducible: Always Steps to Reproduce: 1. Kernel package is upgraded 2. Try to run tcpdump Actual Results: 3. Get error about "interface not supported" and "unknown address family" 4. Reboot into new kernel 5. Try again to run tcpdump with identical arguements 6. tcpdump works as expected Expected Results: 3. tcpdump works as expected even before system is booted into new kernel Relations: - Kernel upgrade removes modules of running kernel subtly breaking the system until rebooted into new kernel (novell/bugzilla/id: 590496) https://bugzilla.novell.com/show_bug.cgi?id=590496 Discussion: #1: unknown user (2010-03-23 14:38:59) This is another symptom of needing the ability to clean up an old kernel after a successful boot. #2: (michal-m) (2010-03-23 16:02:38) (reply to #1) Let alone defining "successful boot" would be tough, but let's say if the user has logged in, there is at least some success (but e.g. the network might still not be working though). This would be the kernel packaging part. Then there would need to be some way to tell the package manager "now it's time to remove packages x,y and z, ask the user for confirmation either via the update applet, or as soon as the package manager is started". IMO it would be a nice feature, but I have no idea how difficult the zypp/yast/updater applet part would be. -- openSUSE Feature: https://features.opensuse.org/309205

1 12

[New: openFATE 312855] Kernel crash dump identification
by fate_noreply＠suse.de 19 Oct '11

19 Oct '11

Feature added by: Petr Tesařík (ptesarik) Feature #312855, revision 1 Title: Kernel crash dump identification Hackweek VII: Unconfirmed Priority Requester: Important Requested by: Petr Tesařík (ptesarik) Partner organization: openSUSE.org Description: A utility that looks at any crash dump and finds out the architecture, kernel version, and possibly even kernel log. -- openSUSE Feature: https://features.opensuse.org/312855

1 1

[New: openFATE 309702] Make NetworkManager better
by fate_noreply＠suse.de 18 Oct '11

18 Oct '11

Feature added by: Li Bin (BinLi) Feature #309702, revision 1 Title: Make NetworkManager better Requested by: Li Bin (binli) Description: There are several features in NetworkManager, I wanna focus one or two * VPN autoconnect (?) ( bgo #349151 (https://bugzilla.gnome.org/show_bug.cgi?id=349151) , bgo #560471 (https://bugzilla.gnome.org/show_bug.cgi?id=560471) ) * Interface bonding support ( bgo #540995 (https://bugzilla.gnome.org/show_bug.cgi?id=540995) ) * Bridge interface support ( bgo #546197 (https://bugzilla.gnome.org/show_bug.cgi?id=546197) ) * Local caching nameserver support * PPPoE over WiFi (http://live.gnome.org/WiFi) support ( bgo #559134 (https://bugzilla.gnome.org/show_bug.cgi?id=559134) ) * Connection time and traffic tracking ( bgo #601372 (https://bugzilla.gnome.org/show_bug.cgi?id=601372) ) * VPN connections in the top-level applet menu First I wanna hack the VPN autoconnect for NetworkManager. -- openSUSE Feature: https://features.opensuse.org/309702

1 10

[New: openFATE 312854] make nfs-server and nfs-client setup in YaST themselves deal with the Firewall
by fate_noreply＠suse.de 18 Oct '11

18 Oct '11

Feature added by: Steffen Eibicht (steffen13) Feature #312854, revision 1 Title: make nfs-server and nfs-client setup in YaST themselves deal with the Firewall openSUSE 12.1: Unconfirmed Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Steffen Eibicht (steffen13) Partner organization: openSUSE.org Description: Hi, when setting up a NFS Server or a NFS client, you can tick "open firewall port" That is really convinient. But there are also other services involved with NFS, which also require some modifications to the firewall. As far as I understood (I do not have that much clue about all this), it is rpc.mountd and rpc.statd, which need to go through the firewall as well. So the normal user (like me) is not able to setup NFS at home, without switching off the firewall completely as it seems like that you can not force these two services to use ports, which you specify as open. Switching off the firewall completely is a workaround but it leaves a bitter taste, as it lowers the security. So it would be cool, if YaST could take care of all services related to NFS in terms of firewall settings and also the settings coming from the NFS setup Business case (Partner benefit): openSUSE.org: it would increase the security of the system if you do not need to switch off the firewall completely. And of course it would make YaST and openSUSE even better, as this then fullfills the promise, YaST makes as an convinient tool. -- openSUSE Feature: https://features.opensuse.org/312854

1 3

[New: openFATE 312806] Jitsi
by fate_noreply＠suse.de 18 Oct '11

18 Oct '11

Feature added by: Christian Spaan (Gyges88) Feature #312806, revision 1 Title: Jitsi Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Christian Spaan (gyges88) Partner organization: openSUSE.org Description: Provide Jitsi (formerly SIP Communicator), a cross-platform multiprotocol messaging and SIP client. Main benefits: audio/video with XMPP Jingle on all platforms, thus improving interoperability; out-of-the-box encryption for chats and calls. -- openSUSE Feature: https://features.opensuse.org/312806

1 2