openSUSE Features March 2009

features@lists.opensuse.org

1 participants
185 discussions

[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 05 Sep '09

05 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 305308] Installation into Windows Partition (Wubi-like)
by fate_noreply＠suse.de 28 Aug '09

28 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 305320] Show accessed mirror(s)
by fate_noreply＠suse.de 19 Aug '09

19 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 19 Aug '09

19 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 305680] access table contents in YaST in more ways than just by push buttons
by fate_noreply＠suse.de 18 Aug '09

18 Aug '09

Feature added by: Martin Schmidkunz (mschmidkunz) Feature #305680, revision 1, last change by Title: access table contents in YaST in more ways than just by push buttons openSUSE-11.2: New Priority Requester: Important Requested by: Martin Schmidkunz (mschmidkunz) Interested: Johannes Meixner (jsmeix) Interested: Katarina Machalkova (kmachalkova) Interested: Lukas Ocilka (locilka) Interested: Martin Vidner (mvidner) Interested: Ricardo Cruz (rpmcruz) Description: There is feedback (e.g. http://mvidner.blogspot.com/2009/01/yast-ui-table-usability.html) that users might get confused with the fact that table actions (performed on the table items) are accesible only as push buttons below the table. What users are used to from other GUI applications and what they miss in YaST UI is: a) context menu activated by right click on table item (e.g. edit/delete this item) b) more function key bindings (e.g. 'Delete' key will do the same what would pushing delete button do) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305680

1 6

[openFATE 306230] Auto-Reset the screen settings
by fate_noreply＠suse.de 14 Aug '09

14 Aug '09

Feature added by: Marcel Müller (open_assistant) Feature #306230, revision 1, last change by Title: Auto-Reset the screen settings openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Marcel Müller (open_assistant) Description: The "Bildschirmeinstellungen"(~screen settings, don't know the name in the english version, the little Monitor in the Gnome panel, where you can set the screen solution and the frequenzy) should reset the solution after 30 or 15 seconds automatically, if you don't press save. Like in Windows or SaX2. It would avoid much trouble if you choose the wrong settings. -- openSUSE Feature: https://features.opensuse.org/306230

1 6

[openFATE 305803] improve command_not_found_helper speed
by fate_noreply＠suse.de 14 Aug '09

14 Aug '09

Feature added by: Susanne Oberhauser (froh) Feature #305803, revision 1, last change by Title: improve command_not_found_helper speed openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Susanne Oberhauser (froh) Description: In the discussion on opensuse-factory [opensuse-factory] issues with command-not-found speed (Message-ID: <20081210084607.GA2988@taygeta>), I've suggested a different approach: I'd very much prefer bash to tell me without any delay: Command not found. If this is not a typo, type "man make-it-work" for help. And then the make-it-work man page will tell you right away to run "make-it-work commandname' to locate and install the package providing fancytool. with a little practice you will go one back in history, prefix your last command with 'make-it-work ' and have fun... imho the current solution is solving a problem that doesn't really exist (pretend all software is preinstalled) and creates a new one (lag). Michal Vyskocil pointed out that such magic should at least look in /sbin and /usr/sbin and give a usefull message if the command is found there: command found in /sbin or /usr/sbin. Maybe retry as root, e.g. with 'sudo $command' -- openSUSE Feature: https://features.opensuse.org/305803

1 6

[openFate 305658] Official USB stick images
by fate_noreply＠suse.de 14 Aug '09

14 Aug '09

Feature added by: Stephan Binner <stbinner(a)novell.com> Feature #305658, revision 1, last change by Title: Official USB stick images openSUSE-11.2: New Priority Requester: Desirable Requested by: Stephan Binner (beineri) Description: It would like to see openSUSE releases with official USB images (one with KDE, one with GNOME) next to the Live-CDs. As alternative the Live-CD images could be mastered in a way that they also can boot from USB (afaik they are not able atm) together with a small app/script to install them to USB - other distributions offer that. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305658

1 49

[openFate 305318] Move gconf schemas to /usr
by fate_noreply＠suse.de 14 Aug '09

14 Aug '09

Feature added by: Vincent Untz <vuntz(a)novell.com> Feature #305318, revision 1, last change by Title: Move gconf schemas to /usr openSUSE-11.2: New Priority Requester: Desirable Requested by: Vincent Untz <vuntz(a)novell.com> Partner organization: openSUSE.org Description: We store gconf schemas in /etc/gconf. However, the schemas are not configuration files, but simply data. Therefore, we should move the schemas to /usr. Simply changing a line in /etc/gconf/2/path should make gconf work with the new location. Note that Debian already implements this. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305318

1 7

← Newer
1
...
7
8
9
10
11
12
13
...
19
Older →

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openSUSE Features March 2009