openSUSE Features September 2016

features@lists.opensuse.org

1 participants
607 discussions

[openFATE 307769] remove X-KDE-SubstituteUID and edit Exec on YaST2 .dekstop files

by fate_noreply＠suse.de

Feature added by: andrea florio (anubisg1) Feature #307769, revision 1 Title: remove X-KDE-SubstituteUID and edit Exec on YaST2 .dekstop files openSUSE-11.3: Unconfirmed Priority Requester: Mandatory Requested by: andrea florio (anubisg1) Partner organization: openSUSE.org Description: All YaST .destop files in /usr/share/applications/YaST2 use the "X-KDE-SubstituteUID" to make them running as root. X-KDE-SubstituteUID is a KDE only "workaround" for that only KDE is supposed to be able to understand. Really, also GNOME as very famous DE understand that. All the others DE like XFCE, LXDE, Icewm and so on do not understand that (and they are not supposed to do that) so they run all yast2 modules as NON root user. all that Desktop files should edit their exec line and maybe remove X-KDE-SubstituteUID exactly as has been done with /usr/share/applications/YaST.desktop into yast2-control-center package. /usr/share/applications/YaST.desktop content: [Desktop Entry] X-SuSE-translate=true Type=Application Categories=Settings;System;SystemSetup;X-SuSE-Core-System;X-SuSE-ControlCenter-System; Name=YaST Icon=yast GenericName=Administrator Settings Exec=/usr/bin/xdg-su -c /sbin/yast2 #OnlyShowIn=KDE;GNOME; #X-KDE-SubstituteUID=true X-KDE-RootOnly=true X-KDE-System-Settings-Parent-Category=system X-KDE-ServiceTypes=KCModule Encoding=UTF-8 as you can see use /usr/bin/xdg-su -c in Exec line, made the .desktop file DE independent Test Case: https://bugzilla.novell.com/show_bug.cgi?id=540627 Use Case: any user running a DE different that KDE/GNOME will run al yast2 modules as non root user with all the warnings/errors that came from that Business case (Partner benefit): openSUSE.org: That will increase openSUSE usability for users running a different DE like XFCE and LXDE, and will be a great step to have that feature: https://features.opensuse.org/307729 perfectly working -- openSUSE Feature: https://features.opensuse.org/307769

5 years, 9 months

[New: openFATE 312750] Make Yast2 stay open after installing packages

by fate_noreply＠suse.de

Feature added by: ursan marius bogdan (creatura85) Feature #312750, revision 1 Title: Make Yast2 stay open after installing packages openSUSE.org: Unconfirmed Priority Requester: Important Requested by: ursan marius bogdan (creatura85) Partner organization: openSUSE.org Description: As we all know YaST2 is the best control center around and as title says, can we make it even better by keeping it open after one or more packages are installed? (just like Synaptic for e.g.). I know this can be done adjusting some setting http://dl.dropbox.com/u/10573557/SUSE%20Misc/yast-at-close-action.jpeg but i was thinking if it is possible to make it a default setting for versions to come. Business case (Partner benefit): openSUSE.org: This feature will reduce the time of opening the package manager for any operations: install, delete and upgrade. -- openSUSE Feature: https://features.opensuse.org/312750

5 years, 9 months

[New: openFATE 312647] Preserve Running Kernel On Kernel Update by Default

by fate_noreply＠suse.de

Feature added by: Robert Davies (robopensuse) Feature #312647, revision 1 Title: Preserve Running Kernel On Kernel Update by Default openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Robert Davies (robopensuse) Partner organization: openSUSE.org Description: My suggestion is to enable multiversion kernel & preserve running kernel for safer kernel updates, to reduce support problems when new kernels won't boot. This is now possible for 12.1 by 1 line change to zypp.conf. Since Online Update was first introduced (SuSE 7.1?) it replaced the running kernel by default, which can lead to problems booting. For a while multiversion kernel has been supported by libzypp (1 line edit in zypp.conf). The drawback with multiversion was manual deletion required of unwanted kernel packages (see http://lists.opensuse.org/opensuse-kernel/2011-07/msg00056.html). Now in Factory 12.1 M3 Michel Marek has included & announced - kernel package retention options (see http://lizards.opensuse.org/2011/07/14/improved-kernel-package-retention-in…). The default is sane, to preserve the Lastest & Running Kernels. So lets use it and make 12.1 kernel updates safer for all, and by default do the right thing! Use Case: End user upgrades kernel to Tumbleweed and it fails to boot. With kernel package retention, the running kernel was saved and recovery is simply a matter of choosing the "good" kernel from GRUB menu. Business case (Partner benefit): openSUSE.org: To reduce support caused by kernel upgrade "accidents". To encourage safer testing of Kernel Team "stable" & "HEAD" kernels. To correct a long standing risky choice, made for implementation convenience of deleting old kernel package, before the new was tested. -- openSUSE Feature: https://features.opensuse.org/312647

5 years, 9 months

[New: openFATE 311388] openSUSE Sky

by fate_noreply＠suse.de

Feature added by: Timo Hoenig (thoenig) Feature #311388, revision 1 Title: openSUSE Sky openSUSE Distribution: Unconfirmed Priority Requester: Important openSUSE Infrastructure: Unconfirmed Priority Requester: Important Requested by: Timo Hoenig (thoenig) Partner organization: openSUSE.org Description: With this feature I am announcing openSUSE Sky. openSUSE Sky will bring our distribution to cloud environments by providing official images for both openSUSE releases and snapshots of current development versions. With openSUSE Sky running the latest and greatest snapshot of openSUSE will be as easy as a mouse click. This gives developers the most efficient way for reproducing bugs on vanilla snapshots. Cloud users will appreciate to have access to trusted built of our distribution without any unknown modifications (e.g. intentional backdoors). Target cloud platforms are Amazon EC2 (using EBS/S3) and Eucalyptus (Walrus). Target audience are cloud users and developers. -- openSUSE Feature: https://features.opensuse.org/311388

5 years, 9 months

[New: openFATE 316224] Drop dhcpcd from distribution

by fate_noreply＠suse.de

Feature added by: Peter Varkoly (varkoly) Feature #316224, revision 1 Title: Drop dhcpcd from distribution Requested by: Peter Varkoly (varkoly) Partner organization: openSUSE.org Description: We are going to drop dhcpcd on SLES. There are more reasons: 1. We already have two alternate packages for dhcpcd: dhcp-client and wicked. 2. The actual version will not be maintained by upstream 3. An update to the actual dhcpcd version requires a lot of unneeded work. Stefan Winterfeld was informed and he knows that our initrd must be adapted. -- openSUSE Feature: https://features.opensuse.org/316224

5 years, 9 months

[New: openFATE 310668] run pulseaudio server with 'flat-volumes=no'

by fate_noreply＠suse.de

Feature added by: robert spitzenpfeil (robert_spitzenpfeil) Feature #310668, revision 1 Title: run pulseaudio server with 'flat-volumes=no' openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: robert spitzenpfeil (robert_spitzenpfeil) Partner organization: openSUSE.org Description: I listen to music while writing... and every single time I change songs a hilariously loud POP is almost killing my ears. This is annoying and painful. What's also annoying is that with 'flat-volumes = yes' the master volume is changed to the loudest individual stream. If a rogue application should choose to up the volume, my ears get fried (headphones !) Personally I think the purpose of having a master volume slider is to limit the max volume to avoid this kind of crap, which is totally nullified by 'flat-volumes = yes' ! Proposal: use 'flat-volumes = no' as the default in '/etc/pulse/daemon.conf'. I think the user is clever enough to handle the volume sliders himself. And only because Vista or W7 fiddles with the master volume in this _sick_ way, we don't need that as well. Reproducible: Always Steps to Reproduce: 1. play a song 2. increase the volume for the app. using pavucontrol or with the app. itself 3. master volume is pushed up as well Expected Results: The user should be the _only_ one messing with MASTER VOLUME. Business case (Partner benefit): openSUSE.org: With 'flat-volumes=yes' it is possible to get permanent hearing damage if unexpected volume surges are forced into the user's ears! Again with this feature enabled _any_ application that uses pulseaudio can set the master volume to 100%. That might be tolerable with a stereo system with a manual volume knob, but on a laptop + headphones this is close to a criminal assault. -- openSUSE Feature: https://features.opensuse.org/310668

5 years, 9 months

[New: openFATE 312890] Opensuse 12.1 - provide Blender 2.6 as default install

by fate_noreply＠suse.de

Feature added by: Jedi Beeftrix (Jedibeeftrix) Feature #312890, revision 1 Title: Opensuse 12.1 - provide Blender 2.6 as default install openSUSE Distribution: Unconfirmed Priority Requester: Important Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Jedi Beeftrix (jedibeeftrix) Partner organization: openSUSE.org Description: Blender 2.6 finally here on Sunday the 16th of October. A huge milestone for Blender, and the best opensource 3D modelling/rendering/animation/editing package available, on linux or otherwise. http://www.blendernation.com/2011/10/14/blender-2-60-rc2-available/ This really should be included on the 12.1 dvd .iso Please! -- openSUSE Feature: https://features.opensuse.org/312890

5 years, 9 months

[New: openFATE 314707] zypper history

by fate_noreply＠suse.de

Feature added by: Marcus Moeller (MarcusMoeller) Feature #314707, revision 1 Title: zypper history openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Marcus Moeller (marcusmoeller) Partner organization: openSUSE.org Description: zypper should have something like a history function, similar to yum. With this history function, past installation tasks could be listed, and even undone. example usage: zypper history info: list history -> every step in history has a dedicated number zypper history undo $number: undo the installation This could also be very useful on software testing. If one wants to take a look at the current status of e.g. KDE and uninstall it afterwards. -- openSUSE Feature: https://features.opensuse.org/314707

5 years, 9 months

[New: openFATE 314853] Remove xterm and icewm from default installation

by fate_noreply＠suse.de

Feature added by: Jared Meidal (kahu) Feature #314853, revision 1 Title: Remove xterm and icewm from default installation openFATE: Unconfirmed Priority Requester: Important Requested by: Jared Meidal (kahu) Partner organization: openSUSE.org Description: xterm and icewm are great alternatives, but seem redundant when always bundled with default installations of Gnome or KDE's terminal (gnome-terminal, konsole). Also, having the icewm session is a great fallback and useful for emergency access but really necessary by default? I have found that if I remove xterm is removed the bundle with icewm, but also xorg-X11 and other packages. When this happens GDM will not launch after a reboot without CLI commands. This does not feel intuitive for a smooth default system, or helpful for a user who is wanting to clean up their packages or menu items they do not use. -- openSUSE Feature: https://features.opensuse.org/314853

5 years, 9 months

[New: openFATE 314883] /root symlinked to /home/root

by fate_noreply＠suse.de

Feature added by: Kalenz . (Kalenz) Feature #314883, revision 1 Title: /root symlinked to /home/root openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Kalenz . (kalenz) Partner organization: openSUSE.org Description: I might be saying something stupid here, in which case just shout me down. But: by default openSUSE installs with a separate /home partition, and for a typical user the most obvious benefits are: - ability to format/reinstall without erasing /home; - ability to share /home with different installs/distros; - (less sexy: keep root partition small, for efficiency.) Based on the first two arguments, I think we would be doing most users a favour by placing /root on the /home folder. Arguments for: (1) It is the home folder of the root user, so surely /home is a sensible place to keep it; (2) /root typically contains credential files, config scripts and so on, which you probably don't want to lose if you format / (and not /home). Arguments against: (3) I can imagine this to be problematic if you encrypt /, but not /home. What do others think? -- openSUSE Feature: https://features.opensuse.org/314883

5 years, 9 months

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openSUSE Features September 2016