July 2009 - openSUSE Features - openSUSE Mailing Lists

[openFate 305345] Replace cups-autoconfig with hal-cups-utils
by fate_noreply＠suse.de 07 Sep '09

07 Sep '09

Feature added by: Vincent Untz <vuntz(a)novell.com> Feature #305345, revision 1, last change by Title: Replace cups-autoconfig with hal-cups-utils openSUSE-11.2: New Priority Requester: Important Requested by: Vincent Untz <vuntz(a)novell.com> Partner organization: openSUSE.org Description: In openSUSE, we use cups-autoconfig to automatically configure new printers detected by HAL. However, no other distro uses this, and hal-cups-utils seems to be the long-term solution. Switching to hal-cups-utils means easier maintenance for us. hal-cups-utils also ships the hal backend for cups that we have in cups-backends. I've packaged a new cups-backends package (without the hal backend) and a hal-cups-utils package (with the hal backend, patched like what we had in cups-backends) in home:vuntz:factory-playground. So it's all ready for testing. Note: yast2-printer makes it possible to edit /etc/cups-autoconfig.conf. We might want to keep the configuration option of /etc/cups-autoconfig.conf in hal-cups-utils. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305345

1 9

[openFATE 306168] Wake the PC to run the task if it has been suspended.
by fate_noreply＠suse.de 04 Sep '09

04 Sep '09

Feature added by: Stephan Kulow (coolo) Feature #306168, revision 1, last change by Title: Wake the PC to run the task if it has been suspended. openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Scott Couston (zczc2311) Description: Increasingly we offer tasks to be run that are configured in Yast - Online Update- Apparmour reports, notifications from events etc etc. What we don't offer it an open to wake the PC from suspend to run the task if the user so desires it - I think its is not of much value to schedule any task or to set any type of notification if the user has no option to wake the PC from suspend Reproducible: Always Steps to Reproduce: 1. Set online update to run in 30 minutes time. 2. Suspend the PC. 3. We have lost our instructions to initiate any schedule by NOT offering a way or option to wake a PC from sleep. Actual Results: If the PC suspends itself is is told to suspend any scheduled task set during that period will never run. Expected Results: This is a problem as we are setting a task but don't provide a way for the task we have set to run if the PC is suspended at the time - This could easily mean that any scheduled task may never run if it is scheduled inside say.......23:00 - 04:00 Hours Dont like my luck with default priority ;-) But I think I have a valid point to leave default Severity and aim for 11.2 implementation. Relations: - In all Yast Application that we enable to run at a specific time we currently have no way to wake the PC to run the task if it has been suspended. (novell/bugzilla/id: 482678) https://bugzilla.novell.com/show_bug.cgi?id=482678 -- openSUSE Feature: https://features.opensuse.org/306168

1 4

[openFATE 306733] Add KDE3 buildservice repository to community list
by fate_noreply＠suse.de 02 Sep '09

02 Sep '09

Feature added by: Karsten König (remur) Feature #306733, revision 1 Title: Add KDE3 buildservice repository to community list openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Karsten König (remur) Description: As openSUSE 11.2 will drop KDE3 from main repositories we should make adding the KDE3 repository as easy as possible, adding KDE3 to the community repository list would be an easy way to do this and will point out the unsupported state of the repository. Use Case: * Elmar wants to keep using KDE3 as KDE4 still isn't ready for him, he doesn't mind using a seperate inofficial repository though. This will make it easy for him to add the repository at install time and select KDE3 * Karsten hangs around #opensuse-kde and after 11.2 release a lot of people come and ask how to get KDE3 and start bitching about the decission to drop it, he can now point out this easy way to add the repository and help restore order in the channel -- openSUSE Feature: https://features.opensuse.org/306733

1 28

[openFate 305308] Installation into Windows Partition (Wubi-like)
by fate_noreply＠suse.de 27 Aug '09

27 Aug '09

Feature added by: Stephan Binner <stbinner(a)novell.com> Feature #305308, revision 1, last change by Title: Installation into Windows Partition (Wubi-like) openSUSE-11.2: New Priority Requester: Desirable Requested by: Stephan Binner <stbinner(a)novell.com> Partner organization: openSUSE.org Description: Wubi allows the installation of Ubuntu on a MS Windows System without changing the partition setup. Users can test-drive a Linux system without major performance loss like when using a Live-CD, have data persistence beyond reboot and an easy way to deinstall like any other application after trial. References: http://wubi-installer.org , https://wiki.ubuntu.com/WubiGuide , http://en.wikipedia.org/wiki/Wubi_(Ubuntu) Business case (Partner benefit): openSUSE.org: Having a Wubi-alike installer for openSUSE would be a great way to promote openSUSE to Windows users. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305308

1 14

[openFATE 306652] description field silently removes words in < angular brackets >
by fate_noreply＠suse.de 24 Aug '09

24 Aug '09

Feature added by: Juergen Weigert (jnweiger) Feature #306652, revision 1 Title: description field silently removes words in < angular brackets > openFATE: Unconfirmed Priority Requester: Important Requested by: Juergen Weigert (jnweiger) Description: angular brackets < and > should be escaped from the rich text validator, if taped in by the user. currently the validator silently removes them together with the words in them, thus crippling the text. -- openSUSE Feature: https://features.opensuse.org/306652

1 4

[openFATE 306995] make voting widget more prominent in openFATE
by fate_noreply＠suse.de 24 Aug '09

24 Aug '09

Feature added by: Ciaran Farrell (babelworx) Feature #306995, revision 1 Title: make voting widget more prominent in openFATE openFATE: Unconfirmed Priority Requester: Desirable Requested by: Ciaran Farrell (babelworx) Description: When viewing a feature on features.opensuse.org it is hard to see how you can vote the feature up or down. You can see a scorebar, but no indication of how to influence it. After viewing the Help page, I found out that "The voting widget is displayed on the upper right side of a feature. It shows the current score of a feature, and you can see a history of the votes on "toggle statistics". To give a vote, please login, and you will have the three options "down", "neutral" and "up" when hovering over the voting applet." The Help documentation is perfect - but would it not be better if the "vote up and vote down" buttons were: * directly visible without needing to hover over anything * accessible not just from the feature page itself but also when viewing a list of features sorted e.g. by score * from the dashboard -- openSUSE Feature: https://features.opensuse.org/306995

1 4

[openFATE 306909] Implement kio_sftp with libssh
by fate_noreply＠suse.de 21 Aug '09

21 Aug '09

Feature added by: Andreas Schneider (gladiac) Feature #306909, revision 1 Title: Implement kio_sftp with libssh Hackweek IV: Unconfirmed Priority Requester: Important Requested by: Andreas Schneider (gladiac) Description: The current kio_sftp implementation calls the openssh ssh binary for sftp. This is ugly and slow. It is time to replace kio_sftp with libssh's sftp implementation. This is a POSIX like API for IO. Andreas Schneider and Dirk Müller will work on this. Test Case: Whatever ... :) Use Case: Better, faster, cleaner! -- openSUSE Feature: https://features.opensuse.org/306909

1 3

[openFate 305320] Show accessed mirror(s)
by fate_noreply＠suse.de 18 Aug '09

18 Aug '09

Feature added by: Peter Poeml <poeml(a)novell.com> Feature #305320, revision 1, last change by Title: Show accessed mirror(s) openSUSE-11.1: New Priority Requester: Mandatory Requested by: Peter Poeml <poeml(a)novell.com> Partner organization: openSUSE.org Description: This concerns both YaST and zypper. It would help a lot if they would show the mirror which is accessed when downloading a package. (Technically, the download client is following redirects and the actually URL needs to be shown, not just the first URL that was contacted but that redirected to another URL) It is a long-standing problem that this information is lacking and it makes debugging and optimizing much harder than necessary, because this information is only available deeply buried in some logfile. We need this information for two reasons: 1) Debugging - to see which URL was accessed when something goes wrong, like a mirror timing out. For example, Whenever a mirror returns garbage, it takes a lot of additional time to find out which one, because all reports are lacking the critical detail, and it is usually hard to find it out later. 2) Optimizing the load sharing between different mirrors - to distinguish slow mirrors from fast ones. For example, I am very much in need of information about the situation in the US, but even though people in the US run installations for me and are willing to send me logs, I can't get this information. In reply to a question from Stano: > Do you want the information in the log or to be shown in e.g. zypper -vvv ? Shown, in normal output. It is already in some log I believe, I don't know which one exactly anymore though. Thing is, users won't be able to tell us anything useful if they weren't shown the information. And later it is not reproducible. At least in a failure situation the URLs must be shown. That alone wouldn't give us the chance to find out about slow mirrors, but at least it would allow to debug problems. Real life example #1: If a mirror is behind a firewall that lets every 10th connection stall (so the transfer hangs or the connection is reset), it usually takes weeks (!) to find out about it. But it hits virtually every user from mirrors country during the time. We have had this 4 times during the last 18 months. Real life example #2: I got feedback from someone who did a network install of openSUSE 11.0 from download.opensuse.org, located in the US. He had to let it running overnight because it took a long time. Next morning, the install hadn't even completed. YaST was hanging and waiting for somebody to hit retry. Problem is, it took us a lot of work to find out which mirror was at fault. We actually had to repeat the install, I had to follow the log and live watching his machine accessing download.opensuse.org, to see where it was redirected, and where it spent most time (while downloading some package). We found a mirror which was really slow, and I could disable it. I have a suspicion though, that we have more such mirrors, because I have got some similar reports from recently. But how to find out? People only complain about slowness, without the ability to give any useful detail. See http://news.opensuse.org/2008/09/23/upcoming-factory-changes/#comments (http://news.opensuse.org/2008/09/23/upcoming-factory-changes/#comments) for examples of this. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305320

1 18

[openFate 305694] Separate Desktop / Server Kernels
by fate_noreply＠suse.de 18 Aug '09

18 Aug '09

Feature added by: Dean Hilkewich (deanjo13) Feature #305694, revision 1, last change by Title: Separate Desktop / Server Kernels openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Dean Hilkewich (deanjo13) Partner organization: openSUSE.org Description: It seems to me that the current default kernels are somewhat hurting openSUSE's performance perception. Current kernel configs are OK but are not very well suited for desktop usage. In the future I would like to see a kernel package that is optimized for desktop usage. Current timer settings and no preemption really (sometimes drastically) hurts openGL performance and applications such as wine and causes alot of issues such as audio studdering. It would be nice to see a separate desktop performance kernel package with options such as Preemption model set to Preemptable Kenel (low-latency Desktop) and Timer Frequency Set to 1000 Hz, HPET support, Tickless System, disable optimize for size, disable Control Group support and disable Group CPU scheduler. You could also disable items and modules that are extremely rare in a desktop environment such as ATM support, Infiniband etc etc as these are not typically used in a desktop scenario which would be a large majority of openSUSE users. Further performance enhancements would also be done through out the system aimed at desktop use as well such as disabling barriers (even making it a simple checkmark option in the partitioner). Such optimizations for desktop usage can overcome openSUSE's reputation as being slower then the other mainstream distro's. The kernel settings alone can make up to a 30-40% increase in framerates in wine games for example and can cure alot of hiccups in multimedia apps. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305694

1 53

[openFATE 306941] Live Per-process I/O graph similar to iotop
by fate_noreply＠suse.de 18 Aug '09

18 Aug '09

Feature added by: Nikanth K (nikanth) Feature #306941, revision 1 Title: Live Per-process I/O graph similar to iotop Hackweek IV: Unconfirmed Priority Requester: Important Requested by: Nikanth K (nikanth) Description: iotop has a similar interface to top but dislays I/O data. But I/O could be spiky and it is easy to miss I/O events. Watching a real-time graph of it, would be more interesting. Also most of the time I write only C code. So I would use this oppurtunity to keep abreast modern languages like python, Java,... The iotop code which I need to refer is in python, and I would write this application in Java!!! -- openSUSE Feature: https://features.opensuse.org/306941

1 7