March 2011 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 311598] speedup opensuse
by fate_noreply＠suse.de 18 Mar '11

18 Mar '11

Feature added by: jaime torres (jtamate) Feature #311598, revision 1 Title: speedup opensuse openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: jaime torres (jtamate) Partner organization: openSUSE.org Description: When you have tried Gentoo, all the other distributions are slower. If opensSUSE wants to attract a lot more developers, just speedup the distribution doing this simple trick: ****** Provide, as a start, kernel and glibc compiled for every major cpu architecture gcc (and linux) supports. (-march= and -mtune= parameters) i386, i486, i586, i686, pentium, pentiumpro, pentiumii, pentiumiii, pentium4, prescott, nocona, core, core2, corei7, l1om, k6, k6_2, athlon, opteron, k8, amdfam10, bdver1 ****** And if at installation time, the cpu type information is written to a zypper configuration file, it could search the optimized file instead of the generic one. -- openSUSE Feature: https://features.opensuse.org/311598

1 3

[New: openFATE 311112] libvirt driver for new xen toolstack
by fate_noreply＠suse.de 18 Mar '11

18 Mar '11

Feature added by: James Fehlig (jfehlig) Feature #311112, revision 1 Title: libvirt driver for new xen toolstack Hackweek VI: Unconfirmed Priority Requester: Important Requested by: James Fehlig (jfehlig) Partner organization: openSUSE.org Description: Xen 4.1.0 (due February 2011) will be the first release in which the new xl/libxl (aka libxenlight [1]) toolstack will be the default, preferred tool set. Although still included in the release, the legacy xm/xend toolstack will be disabled and in process of deprecation. libvirt needs a hypervisor driver that can communicate with the new Xen toolstack. I'll be working on a libvirt driver for libxl during HW6. Business case (Partner benefit): openSUSE.org: There are many tools using libvirt: vm-install, virt-manager, virt-viewer, vhostmd, libvirt-cim, ... None of these tools will work with Xen 4.1.0 without a libvirt libxl driver. -- openSUSE Feature: https://features.opensuse.org/311112

1 5

[New: openFATE 311452] Suggestions for openSUSE Linux 11.5
by fate_noreply＠suse.de 17 Mar '11

17 Mar '11

1 2

[New: openFATE 311783] Demo for openFATE
by fate_noreply＠suse.de 16 Mar '11

16 Mar '11

Feature added by: Andreas Jaeger (a_jaeger) Feature #311783, revision 1 Title: Demo for openFATE openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: This is just some text with an URL (http://www.novell.com) Use Case: This is a demo for openFATE. -- openSUSE Feature: https://features.opensuse.org/311783

1 4

[openFate 305723] Allow to set the owner of a partition
by fate_noreply＠suse.de 16 Mar '11

16 Mar '11

Feature added by: Rajko Matovic (rajko_m) Feature #305723, revision 1, last change by Title: Allow to set the owner of a partition openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Rajko Matovic (rajko_m) Partner organization: openSUSE.org Description: If a user buys a new external harddrive and partitions it via YaST he will not be able to write on it, since the filesystem is owned by root. A normal user would need to know about how to use konsole and which command to use in order to change the owner. It would be a lot easier, if the user could change the owner within the partitioning module. Of course this should not be possible for system-partitions such as / and /usr etc, yet /windows and /media, as well as /home/xyz/ should be fine. The problem is not trivial as it is not enough to change fstab. See: See: http://ntfs-3g.org/support.html#unprivileged -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305723

1 5

[openFate 305075] Allow to set the owner of a partition
by fate_noreply＠suse.de 16 Mar '11

16 Mar '11

Feature added by: Arvin Schnell (aschnell(a)novell.com) Feature #305075, revision 1 Title: Allow to set the owner of a partition openSUSE-11.1: New Priority Requester: Desirable Requested by: Sven Burmeister (sven.burmeister(a)gmx.net) Partner organization: openSUSE.org Description: If a user buys a new external harddrive and partitions it via YaST he will not be able to write on it, since the filesystem is owned by root. A normal user would need to know about how to use konsole and which command to use in order to change the owner. It would be a lot easier, if the user could change the owner within the partitioning module. Of course this should not be possible for system-partitions such as / and /usr etc, yet /windows and /media, as well as /home/xyz/ should be fine. Discussion: #1: Arvin Schnell(aschnell(a)novell.com) (2008-07-15 08:32:00) Do you want to set gui and uid in /etc/fstab? #2: Sven Burmeister(sven.burmeister(a)gmx.net) (2008-07-15 08:56:26) I'm not sure which is the best approach. Either the user could do something that replaces "chown user:group ." on the new partition or some predefined gui/uid to select from, because the normal user has no idea about those and the numbers that go with them. The goal is that a user that knows the root password can not only partition a new harddrive via GUI but also make it accessible (rw) to users without having to know anything about fstab-syntax and options. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305075

1 17

[New: openFATE 311736] Report system failures to the user
by fate_noreply＠suse.de 15 Mar '11

15 Mar '11

Feature added by: Christoph Obexer (cobexer) Feature #311736, revision 1 Title: Report system failures to the user openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Christoph Obexer (cobexer) Partner organization: openSUSE.org Description: If a daemon crashes the incident is usually reported to the system log, however on a desktop system such errors may go undetected for months. openSuSE is in need of an application that notifies the user that something in the background reported an error and what happened, where to find infos about it and so forth. the application should monitor all relevant logfile locations (/var/log/messages, ~/.xsession-errors,...). Development / Beta versions of openSuSE should come with that application enabled by default to catch as much errors as possible during development. Use Case: Connect USB Headset -> kernel writes some warnings -> show them to the user so he knows that that device may not work as expected. some daemon crashes -> notify user system suspend -> kdm/splashy tries to call some not existing program -> tell user after restore system suspend, restore: some driver misses restore functionality -> notify user so he knows that some device may not work correctly after resume (eg rt73usb) Business case (Partner benefit): openSUSE.org: I just discovered today that at least during January the NetworkManager crashed on system shutdown. Whenever I connect my USB headset to my USB3.0 port the kernel spews out lots of warnings. and probably more things that i did not see now. A few Quotes from my /var/log/messages(i did not yet look them up, just copied them here): /usr/sbin/cron[2183]: (CRON) bad username (/etc/cron.d/smolt) nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/netcontrol_services' exited with error status 127. kernel: [ 85.849043] start_kdeinit (2581): /proc/2581/oom_adj is deprecated, please use /proc/2581/oom_score_adj instead. I can't report bugs I don't know, being a Factory user knowing bugs and reporting them before a release would certainly help the release quality. -- openSUSE Feature: https://features.opensuse.org/311736

1 0

[New: openFATE 309115] Integrate Apple Magic Mouse driver
by fate_noreply＠suse.de 15 Mar '11

15 Mar '11

Feature added by: Andreas Schneider (Los_Andros) Feature #309115, revision 1 Title: Integrate Apple Magic Mouse driver Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Andreas Schneider (los_andros) Description: Hello, I'm using the Apple Magic Mouse and Apple Wireless Keyboard (both bluetooth). The Apple MAgic Mouse has a Touch Screen surface for vertical & horizontical scrolling. The left click and right click is working out of the box using the standard kernel (also the KOTD). You can find a development of the Aple Magic Mouse driver (hid-magicmouse) here: http://github.com/entrope/linux-magicmouse I was unable to build a kernel module and I'm not sure if the driver will be integrated into the standard kernel, so it would be nice to have patched kernel for the openSUSE standard kernel that supports the Apple Magic Mouse. Regards Andy -- openSUSE Feature: https://features.opensuse.org/309115

1 3

[openFATE 305307] Desktop neutral notification
by fate_noreply＠suse.de 15 Mar '11

15 Mar '11

Feature changed by: Stefan Behlert (sbehlert) Feature #305307, revision 20 Title: Desktop neutral notification openSUSE-11.2: Rejected by Stefan Behlert (sbehlert) reject date: 2009-09-02 18:49:19 reject reason: no resources. Priority Requester: Important Projectmanager: Desirable - openSUSE-11.3: Evaluation by product manager + openSUSE-11.3: Rejected by Stefan Behlert (sbehlert) + reject date: 2011-03-15 16:55:55 + reject reason: 11.3 is done. Priority Requester: Important Requested by: Stanislav Brabec (sbrabec) Product Manager: (Novell) Product Manager: (Novell) Project Manager: (Novell) Engineering Manager: (Novell) Partner organization: openSUSE.org Description: Up to 11.0, powersave-notify provided desktop neutral notification. Since 11.1, there is no way, how daemons can notify desktop users about fatal issues. Examples: smartd needs to notify about dying disc nut and apcupsd need to notify about failing power (hal power management cannot be used yet, as many UPS devices are not auto- detectable, hal static-config-based prober does not exist yet, nut-hal supports ony HID devices and apcupsd has no hal connector at all). References: https://bugzilla.novell.com/show_bug.cgi?id=230267 Discussion: #1: Holger Macht (hmacht) (2008-09-17 17:27:33) This should be added to a bakend like the HAL database so that desktop applets can catch the information and show them to the user. We already have something like this for "defective batteries" gnome-power-managar shows to the user. #2: Stanislav Brabec (sbrabec) (2008-12-16 11:48:45) Virtual console may be another way to implement it: http://gxconsole.sourceforge.net/ But such simple implementation does not allow i18n. #4: Klaas Freitag (kfreitag) (2009-09-02 17:21:13) Please reject for now, but I like the idea of the common desktop initiative. #5: Holger Macht (hmacht) (2010-03-02 14:05:08) I really think this feature isn't up to date anymore. In times of D- Bus, every daemon can send system notifications via D-Bus. There just has to be proper desktop application which catches the event and shows an appropriate message. So I think there's no direct need for having an infrastructure for daemons showing a notification on the desktop, but for the proper applications catching specific events on the desktop. And if those applications are missing, corresponding features should be opened one by one. -- openSUSE Feature: https://features.opensuse.org/305307

1 0

[openFATE 302476] KDE notification for apparmor rejects
by fate_noreply＠suse.de 15 Mar '11

15 Mar '11

Feature changed by: Stefan Behlert (sbehlert) Feature #302476, revision 43 Title: KDE notification for apparmor rejects openSUSE-11.0: Rejected by Stephan Kulow (coolo) reject date: 2008-03-26 17:30:24 Priority Requester: Desirable Projectmanager: Desirable openSUSE-11.1: Rejected by JP Rosevear (jproseve) reject date: 2008-08-15 11:38:24 reject reason: Rejected due to lack of time. Priority Requester: Desirable Projectmanager: Desirable openSUSE-11.2: Rejected by Stephan Kulow (coolo) reject date: 2009-08-12 12:07:30 reject reason: too late for 11.2 Priority Requester: Important Projectmanager: Desirable - openSUSE-11.3: Evaluation by engineering manager + openSUSE-11.3: Rejected by Stefan Behlert (sbehlert) + reject date: 2011-03-15 16:48:30 + reject reason: obviously not done Priority Requester: Important Projectmanager: Desirable Requested by: Stephan Kulow (coolo) Product Manager: (Novell) - Product Manager: (Novell) Project Manager: (Novell) Engineering Manager: (Novell) Partner organization: openSUSE.org Description: fate #300563 added dbus event advertising. We'd need a KDE frontend for these dbus events that shows a notification of these events. Documentation Impact: Needs to be documented Discussion: #1: Stephan Binner (beineri) (2008-03-18 10:45:07) Just had a chat with Ludwig and Marcus about this topic (if it would be a nice SoC project) and they don't see much use in having such an applet on the desktop. #2: Marcus Meissner (msmeissn) (2008-03-20 14:52:14) (reply to #1) (background reasoning is: it would spend almost all of the time: doing nothing.) #4: Stephan Kulow (coolo) (2008-03-26 17:30:09) (reply to #2) such dbus callbacks are perfect kded modules - they would register a callback and be dead code after that and create a notification on callback. And it's half a day effort, not really SoC material. #3: Jared Allen (jpallen) (2008-03-20 13:56:50) I like the idea of using this as a SoC project. Let's consider this for openSUSE 11.1 #6: Stephan Binner (beineri) (2009-01-17 16:16:46) (reply to #3) Any objection to make this fate public for openSUSE.org partner and try to advertize it there? #8: Ralph Ulrich (ulenrich) (2009-08-21 17:09:33) This is key competence of distributions: Is there best expertise integrating security features. For openSUSE-11.2 rejected? Choosen another security framework? -- openSUSE Feature: https://features.opensuse.org/302476

1 0