August 2015 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 319035] Make YaST (incl. modules available in GNOME Software
by fate_noreply＠suse.de 22 Dec '19

22 Dec '19

Feature added by: Dominique Leuenberger (dimstar) Feature #319035, revision 1 Title: Make YaST (incl. modules available in GNOME Software openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Dominique Leuenberger (dimstar) Partner organization: openSUSE.org Description: GNOME Software is an other way of handling installations. Instead of being package centric, it is application centric. An application is being represented by means of an appdata.xml file in it's setup (installed to /usr/share/appdata), then a metadata parser extracts this info and produces 'AppStream' metadata (to be consumed by software centers) In order to make extensions/plugins to applications discoverable, a package can add a metainfo.xml file to the same location and have itself listed as an extension/addon to the application. For YaST, this results in: - an appdata.xml file being provided together with YaST.desktop (done) - For all yast modules to install a metainfo.xml file, describin their extensive nature to yast. -- openSUSE Feature: https://features.opensuse.org/319035

1 4

[New: openFATE 318458] Reading user process memory
by fate_noreply＠suse.de 26 Apr '19

26 Apr '19

Feature added by: Sławomir Lach (Lachu) Feature #318458, revision 1 Title: Reading user process memory Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Reading user's process memory or writting to it is very bad think. Malware can stole passwords or change settings of application. I have two idea about solving this issue: 1. Dissallow to debug(reading/writting memory) process placed in /bin, /sbin, /usr/bin, /usr/sbin 2. Dissallow to debug(reading/writting memory) process of file not belonging to user, who execute file. -- openSUSE Feature: https://features.opensuse.org/318458

1 1

[New: openFATE 310701] package byobu in an opensuse repository
by fate_noreply＠suse.de 28 Jan '19

28 Jan '19

Feature added by: Divan Santana (divansantana7) Feature #310701, revision 1 Title: package byobu in an opensuse repository openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Divan Santana (divansantana7) Description: Would be great if anyone using opensuse could zypper in byobu . Unfortunately it's not in any opensuse repo despite it being a great tool for administrating linux servers. I'm quite surprised this isn't already available for opensuse. Would be a nice addition for 11.4 -- openSUSE Feature: https://features.opensuse.org/310701

1 7

[New: openFATE 308445] Tor is not working out of box
by fate_noreply＠suse.de 29 Nov '18

29 Nov '18

Feature added by: Algimantas B (algyzas) Feature #308445, revision 1 Title: Tor is not working out of box Package Wishlist: Unconfirmed Priority Requester: Neutral Requested by: Algimantas B (algyzas) Description: Let's say I installed tor, it is came alone, without privoxy. One should download it manually. And then if I try :~> screen torify konqueror hich: no tsocks in (/home/senis/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:.) /usr/bin/torify: Can't find tsocks in PATH. Perhaps you haven't installed it? [screen is terminating] There is a guide http://en.opensuse.org/Privoxy_tor_squid how to setup it, I'll try it, but in some other distributions it works out of box like this. -- openSUSE Feature: https://features.opensuse.org/308445

1 1

[New: openFATE 309627] Enhance 'Safely Remove' to spin-down and power-off usb HDDs
by fate_noreply＠suse.de 07 Nov '18

07 Nov '18

Feature added by: Pete Clayson (Olmy) Feature #309627, revision 1 Title: Enhance 'Safely Remove' to spin-down and power-off usb HDDs openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Pete Clayson (olmy) Description: 'Safely remove' should (as far as possible) allow for genuine safe removal of all media. Under certain other OSs, the 'safely remove' option on usb devices will... 1/ On usb pen drive with a power/activity led, switch it off (trivial nicety, but reassuring). 2/ On usb HDDs, spin down the disk and power off. This seems more important. There is some discussion about this, for example, http://elliotli.blogspot.com/2009/01/safely-remove-usb-hard-drive-in-linux.… (http://elliotli.blogspot.com/2009/01/safely-remove-usb-hard-drive-in-linux.…) I know that the latest version of Ubuntu does this and there is a script offered in the above link. However, the script, as it stands and run on my installation of OpenSUSE, does not seem to work (in the same way as WinXP or Ubuntu, anyway - my WD600D036 disk does not power off) despite the positive messages in verbose mode. Perhaps this is the CONFIG_USB_SUSPEND option mentioned? -- openSUSE Feature: https://features.opensuse.org/309627

1 6

[New: openFATE 314778] Use polkit for YaST privilege management
by fate_noreply＠suse.de 14 Sep '18

14 Sep '18

Feature added by: Dainius Masiliunas (GreatEmerald) Feature #314778, revision 1 Title: Use polkit for YaST privilege management openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Dainius Masiliunas (greatemerald) Partner organization: openSUSE.org Description: At the moment of writing, YaST relies on having root privileges through a graphical sudo in order to view and carry out most tasks. However, there is no reason why simply displaying those tasks should be restricted like that. YaST should always be started with user privileges, and only ask for additional privileges when they are truly needed - when the selected tasks should be carried out. This can be achieved by using polkit. It also brings a lot of other benefits. Use Case: Users who do not have access to the root password currently also do not have access to a lot of functionality that does not actually require the password, such as searching for package information. Users that do administrative tasks are also subjecting the system to possible security risks by running YaST with full root privileges. Using polkit would increase security and prevent potential user mistakes. Business case (Partner benefit): openSUSE.org: Using polkit, the graphical interface of YaST would always be run as a normal user. That means that code that should not have elevated privileges - like GUI - would not run with them. More could be done without needing to enter the root password - package information query, printer setup, device information overview, reviewing network configuration options etc. In a restrictive environment, the system administrator could set certain tasks to be available for use by regular users, or to allow certain tasks to be run by certain users only. The authentication screen would provide more information about what tasks are about to be carried out for increased security. For instance, if a custom YaST module requests permission to modify the partition table, while it claims to only set up the date and time, it would be clear to the user that the module is either fraudulent or is malfunctioning. In order to not have to authenticate after every single change a module wishes to do, a global queue for the changes could be created (like what is shown by the /etc/sysconfig editor once its changes are to be applied). Once the global "apply" button is pressed, the user would be informed of what actions will be carried out and what privileges will be given to carry them out. Then, once the user confirms that by supplying a password, all the changes are applied. -- openSUSE Feature: https://features.opensuse.org/314778

1 8

[New: openFATE 314606] Improved Btrfs subvolume management in YaST Partitioner
by fate_noreply＠suse.de 21 Aug '18

21 Aug '18

Feature added by: Dainius Masiliunas (GreatEmerald) Feature #314606, revision 1 Title: Improved Btrfs subvolume management in YaST Partitioner openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Dainius Masiliunas (greatemerald) Partner organization: openSUSE.org Description: The current implementation of Btrfs subvolume management is a bit too simplistic. It allows adding and removing subvolumes, but that is all. Expanding this to view subvolumes as actual subvolumes would be beneficial. Perhaps something akin to LVM configuration, as Btrfs subvolumes can handle much of what LVM does. At the same time, this could allow easier interfacing with Snapper. Use Case: When using Btrfs as the main file system, it is useful to have a single Btrfs partition for both / and /home, as it allows for more efficient disk space use. When reinstalling and upgrading, it is now a problem, as there is no way to remove certain subvolumes and leave others, and keeping /home between installations is often useful. Another case is when a multi-device Btrfs volume is desirable. The YaST partitioner only allows creating "regular" Btrfs partitions right now. A feature like that would also be useful for tighter Snapper integration. It would be a convenient place to set which volumes should be monitored by it, and which are not. In addition, it would help resolve a few bugs, such as the failure to automatically create subvolumes for excluding directories from Snapper monitoring when choosing to format the Btrfs partition. -- openSUSE Feature: https://features.opensuse.org/314606

1 9

[New: openFATE 314529] Add XFCE and LXDE live cds in software.opensuse.org
by fate_noreply＠suse.de 19 Jul '18

19 Jul '18

Feature added by: Narayansamy S (vazhavandan) Feature #314529, revision 1 Title: Add XFCE and LXDE live cds in software.opensuse.org openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Narayansamy S (vazhavandan) Partner organization: openSUSE.org Description: There is urgent need to Add XFCE and LXDE live cds in software.opensuse.org page as many Linux users are moving away from traditional DEs(KDE,GNOME) after some rather controversial changes from KDE3.X==>DE4.X and GNOME2.x==>GNOME3.X Many users moving to LXDE and XFCE can try out th DE environments using the live cds provided in the software download page Business case (Partner benefit): openSUSE.org: To test hardware issues Smaller download compared to DVD Many users are preferring LXDE and XFCE over GNOME and KDE One can keep using live cds in case of system crashes DVD download doesn't support live boots -- openSUSE Feature: https://features.opensuse.org/314529

1 4

[New: openFATE 318341] Include "fixparts" on the live rescue CD
by fate_noreply＠suse.de 19 Jul '18

19 Jul '18

Feature added by: Neil Rickert (nrickert) Feature #318341, revision 1 Title: Include "fixparts" on the live rescue CD openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Neil Rickert (nrickert) Partner organization: openSUSE.org Description: The "fixparts" utililty (package "gptfdisk-fixparts") is useful for repairing corrupted partition tables, such as occur when a user tries to convert a disk from GPT partitioning to legacy MBR partitioning. It would be useful to include that on live media -- at least the live rescue -- so that we can point people to a way to fix their install problems. -- openSUSE Feature: https://features.opensuse.org/318341

1 1

[New: openFATE 314607] formatting
by fate_noreply＠suse.de 18 Jul '18

18 Jul '18

Feature added by: Francesco Noacco (FireLink) Feature #314607, revision 1 Title: formatting openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Francesco Noacco (firelink) Partner organization: openSUSE.org Description: Can format and save data in the partitions stored in any fs and not just fat32 (after installation). Use Case: I solved it with "disk manager" Debian testing (3.0.2 by Red Hat, 2009) In the formatting parameters allows disk usage by users other than root. And to think that I had just complained because the utility from a new disc without mbr creates one that is not compatible with other distributions (gparted from an alert message). Business case (Partner benefit): openSUSE.org: Operations should be for everyone. -- openSUSE Feature: https://features.opensuse.org/314607

1 1