December 2015 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 309642] Hacking NetwotkManagement plasma applet
by fate_noreply＠suse.de 12 Aug '16

12 Aug '16

Feature added by: Alexander Naumov (Alexander_Naumov) Feature #309642, revision 1 Title: Hacking NetwotkManagement plasma applet Requested by: Alexander Naumov (alexander_naumov) Description: Trying to create a better support for wifi in NetworkManagement ;) -- openSUSE Feature: https://features.opensuse.org/309642

1 5

[New: openFATE 313139] One letter usernames
by fate_noreply＠suse.de 07 Aug '16

07 Aug '16

Feature added by: Mats Söderström (mazu) Feature #313139, revision 1 Title: One letter usernames openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Mats Söderström (mazu) Partner organization: openSUSE.org Description: The minimum allowed username length is two letters, I see no reason why this can't be changed to one. Business case (Partner benefit): openSUSE.org: To save hassle configuring ssh, nfs, etc. -- openSUSE Feature: https://features.opensuse.org/313139

1 2

[New: openFATE 319632] Grub2: Scan custom.cfg for grub2-once
by fate_noreply＠suse.de 27 Jul '16

27 Jul '16

Feature added by: Egbert Eich (eeich) Feature #319632, revision 1 Title: Grub2: Scan custom.cfg for grub2-once Requested by: Egbert Eich (eeich) Requested by: Egbert Eich (eeich) Partner organization: openSUSE.org Description: grub2-once is used to test grub menu entries which may not boot. This feature is often used by developers. However menu entries for testing are frequently added to custom.cfg. Therefore this file should be scanned as well so that boot entries from it can be selected. -- openSUSE Feature: https://features.opensuse.org/319632

1 7

[New: openFATE 317762] git mirror integration
by fate_noreply＠suse.de 05 Jul '16

05 Jul '16

Feature added by: Adrian Schröter (adrianSuSE) Feature #317762, revision 1 Title: git mirror integration Buildservice: New Milestone: 2.7 Priority Requester: Mandatory Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: OBS can already roll tar balls from git (or other SCM systems) on code change, however, this has two disadvantages: * source server needs to store new tar ball for each change * using files as build descriptions is only working via workarounds. A full git (and only git, not svn,..) support would allow to mirror an entire git tree on the source server and fetch only updates. This means we need to * build tar balls at build time (since package systems like rpm rely on it) * ensure that a rewritten git history can not drop sources of former builds. * allow mirroring of either * * package sources only * * entirely on package level, including .spec files -- openSUSE Feature: https://features.opensuse.org/317762

1 6

[New: openFATE 316517] 32bit version of padsp in 64bit openSUSE
by fate_noreply＠suse.de 27 Jun '16

27 Jun '16

Feature added by: Mircea Kitsune (MirceaKitsune) Feature #316517, revision 1 Title: 32bit version of padsp in 64bit openSUSE openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Mircea Kitsune (mirceakitsune) Partner organization: openSUSE.org Description: I've been trying to fix a Linux game for which sound wasn't working. After some searching, I found that I must run it with the "padsp" command. However, the game is 32 bit and I run 64 bit openSUSE, so "padsp ./game_binary" wouldn't work. I searched for a padsp32 command and even tried to replicate the padsp script, but the library for the x32 version doesn't exist in the x64 repositories. Eventually I got it working by extracting libpulsedsp.so from the x32 openSUSE repos, and manually launching the binary with a LD_PRELOAD pointing to it. This is a workaround and maintaining it can become problematic. The existing library can be found in /usr/lib64/pulseaudio/libpulsedsp.so and the script in /usr/bin/padsp. Basically, I'm asking for x32 bit versions of these in the x64 variant of openSUSE, so any 32bit program can benefit from them too. Business case (Partner benefit): openSUSE.org: Only the 64bit version of padsp is included. Therefore, only 64bit programs can make use of it. Including the 32bit variant in the 32bit pulseaudio package for 64bit openSUSE would solve this problem. -- openSUSE Feature: https://features.opensuse.org/316517

1 2

[New: openFATE 314963] Manage battery threshold
by fate_noreply＠suse.de 19 Jun '16

19 Jun '16

Feature added by: Marc collin (collinm) Feature #314963, revision 1 Title: Manage battery threshold openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Marc collin (collinm) Partner organization: openSUSE.org Description: Some laptop have tool in windows to decide when laptop stop to chargin battery. This feature allow to increate life battery. This is a tool to manage lenovo battery threshold. some laptops are supported by this project tpacpi-bat https://github.com/teleshoes/tpacpi-bat some laptops are managed by this one and have more features https://github.com/evgeni/tp_smapi theses need acpi_call https://github.com/mkottman/acpi_call -- openSUSE Feature: https://features.opensuse.org/314963

1 6

[New: openFATE 315140] Kernel: CONFIG_TCP_MD5SIG needed for quagga
by fate_noreply＠suse.de 14 Jun '16

14 Jun '16

Feature added by: Marc Langer (marclanger) Feature #315140, revision 1 Title: Kernel: CONFIG_TCP_MD5SIG needed for quagga openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Marc Langer (marclanger) Partner organization: openSUSE.org Description: Quagga bgpd allows the configuration of MD5 protected BGP sessions, but the kernel does not have this activated. Business case (Partner benefit): openSUSE.org: Our BGP peers require MD5 but the SuSE Kernel is compiled without CONFIG_TCP_MD5SIG. It takes a long time to find this issue because in the default configuration quagga is not logging properly that this option is missing in the kernel. Each time we have to compile an own kernel. Please activate this in future versions. -- openSUSE Feature: https://features.opensuse.org/315140

1 1

[openFATE 307884] Yafaray instead of Yafray for Blender
by fate_noreply＠suse.de 07 Jun '16

07 Jun '16

Feature added by: Rene Bernhard (rebe) Feature #307884, revision 1 Title: Yafaray instead of Yafray for Blender Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Rene Bernhard (rebe) Description: Hello. As the Yafray render engine for Blender is not longer developed I apreciate if you would replace it with the Yafaray render engine in one of the next openSUSE versions. Or maybe it is possible to make a package for the repositories to download. Thank you very much for your efforts. Best regards rebe -- openSUSE Feature: https://features.opensuse.org/307884

1 4

[New: openFATE 312491] Explicit IPv6 support for YaST printer module
by fate_noreply＠suse.de 11 May '16

11 May '16

Feature added by: Johannes Meixner (jsmeix) Feature #312491, revision 1 Title: Explicit IPv6 support for YaST printer module openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Johannes Meixner (jsmeix) Partner organization: openSUSE.org Description: Currently there is not any kind of special IPv6 support in yast2-printer. Currently IPv6 works only where it is compatible to IPv4 but there are cases where IPv6 needs special handling: For example the tests whether or not a remote host is accessible run "ping <IP-address or hostname>" which fails if IP-address is an IPv6 address because for IPv6 ping6 must be used. See https://bugzilla.novell.com/show_bug.cgi?id=697833 Unfortunately ping6 cannot be used for IPv4 addresses so that yast2-printer needs to implement special distinction of cases in particular if a hostname is given depending on whether or not this hostname has an IPv4 or IPv6 address or both. Probably there are some more special distinction of cases needed to distinguish between IPv4 and IPv6 stuff. -- openSUSE Feature: https://features.opensuse.org/312491

1 20

[New: openFATE 314657] Add setting to not create Failsafe entries in grub menu
by fate_noreply＠suse.de 18 Apr '16

18 Apr '16

Feature added by: Michal Marek (michal-m) Feature #314657, revision 1 Title: Add setting to not create Failsafe entries in grub menu openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Michal Marek (michal-m) Partner organization: openSUSE.org Description: When testing multiple kernels, the grub menu quickly becomes a mess, because every kernel is listed twice. I would love to have a setting in /etc/sysconfig/bootloader, that would allow to tell perl-Bootloader to stop generating the Failsafe entries. -- openSUSE Feature: https://features.opensuse.org/314657

1 1

[New: openFATE 308839] performance: prompt early on failure ...
by fate_noreply＠suse.de 05 Apr '16

05 Apr '16

Feature added by: Michael Meeks (michael_meeks) Feature #308839, revision 1 Title: performance: prompt early on failure ... Buildservice: New Priority Requester: Mandatory Requested by: Michael Meeks (michael_meeks) Description: For local builds, osc has an unfortunate habit of doing a large amount of work, before failing very late. For slow building or leaf packages this can be excessively painful - wasting an "overnight" build slot eg. Many of the checks that we currently do in the middle, should be moved to the beginning (or perhaps just duplicated there). Some examples I have fallen over: * prompt-user-to-re-build-jail - this currently happens after any new packages are downloaded - a process that can take as long as the building. We can know that a jail was dirty before we start & warn then; if we even need dirty jails [cf. fate#308837# ] * simple RPM syntax problems - could be linted ahead of time, currently done after jail construction. + we should catch in particular: missing / mis-named files + mis-applied / not-applied patches + anything else obvious that we can catch Doing this early - while the human is watching is likely to hide long pipeline stalls, and context switching overhead for packagers. -- openSUSE Feature: https://features.opensuse.org/308839

1 3

[New: openFATE 313077] New PAM modules must not be deployed unnoticed by sec team
by fate_noreply＠suse.de 05 Apr '16

05 Apr '16

Feature added by: Sebastian Krahmer (krahmer) Feature #313077, revision 1 Title: New PAM modules must not be deployed unnoticed by sec team openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Sebastian Krahmer (krahmer) Partner organization: openSUSE.org Description: New PAM modules should be reviewed by security team. Just like any suid/daemon/DBUS service. In particular if they are installed by default. -- openSUSE Feature: https://features.opensuse.org/313077

1 4

[New: openFATE 311163] packaging firefox add-ons
by fate_noreply＠suse.de 05 Apr '16

05 Apr '16

Feature added by: Ludwig Nussel (lnussel) Feature #311163, revision 1 Title: packaging firefox add-ons Hackweek VI: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: We lack a way to be able to easily package firefox add-ons as rpm. Packages of add-ons are useful both for the distro vendor and for admins. Distro (or appliance) vendors may install some add-ons by default. Admins want all users to have certain add-ons by default. Moreover some add-ons are not noarch (like bonjourfoxy) and need to be compiled specifically for each distro so a package is unavoidable. To make all of that possible the firefox package needs to provide rpm macros so spec files for add-ons become really simple. By creating a script that downloads version, description etc from addons.mozilla.org and automatically creates spec files the task of packaging add-ons becomes a piece of cake. See home:lnussel:firefox for current status. -- openSUSE Feature: https://features.opensuse.org/311163

1 6

[New: openFATE 316562] Add fs.protected_hardlinks=1
by fate_noreply＠suse.de 15 Mar '16

15 Mar '16

Feature added by: Sebastian Krahmer (krahmer) Feature #316562, revision 1 Title: Add fs.protected_hardlinks=1 Requested by: Sebastian Krahmer (krahmer) Partner organization: openSUSE.org Description: In order to disallow hard linking to suid files etc we should enable hardlink protection: fs.protected_hardlinks=1 or via apropriate /proc entry. -- openSUSE Feature: https://features.opensuse.org/316562

1 9

[New: openFATE 309362] Re-implement Download on Demand (DoD) feature
by fate_noreply＠suse.de 01 Mar '16

01 Mar '16

Feature added by: Adrian Schröter (adrianSuSE) Feature #309362, revision 1 Title: Re-implement Download on Demand (DoD) feature Buildservice: Done Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: The DoD features was dropped for 1.7. LinuxFoundation has re-implemented it in a cleaner way for 1.8 release. -- openSUSE Feature: https://features.opensuse.org/309362

1 8

[openFATE 305838] Integrate ReviewBoard in Buildservice
by fate_noreply＠suse.de 12 Feb '16

12 Feb '16

Feature added by: Klaas Freitag (kfreitag) Feature #305838, revision 1, last change by Title: Integrate ReviewBoard in Buildservice Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Klaas Freitag (kfreitag) Description: ReviewBoard is a code change review system. It should be considered to integrate it to the openSUSE Buildservice infrastructure to ease collaboration. It might be an option that submit requests to packages can be handled in the review board. -- openSUSE Feature: https://features.opensuse.org/305838

1 4

[New: openFATE 318951] YaST should log time like dmesg and journalctl
by fate_noreply＠suse.de 09 Feb '16

09 Feb '16

Feature added by: Joachim Werner (joachimwerner) Feature #318951, revision 1 Title: YaST should log time like dmesg and journalctl Requested by: Arvin Schnell (aschnell) Partner organization: openSUSE.org Description: YaST should log the time in its log-file like 'dmesg' and 'journalctl --output short-monotonic' so that times in the various logs can be compared and events can be synchronized. Relations: - YaST should log time like dmesg and journalctl (feature/copiedfrom: 318921) Business case (Partner benefit): openSUSE.org: Easier to analyse logs in bug reports. -- openSUSE Feature: https://features.opensuse.org/318951

1 4

[New: openFATE 319895] Add btrfs subvolume options to autoyast
by fate_noreply＠suse.de 16 Jan '16

16 Jan '16

Feature added by: Robert Klein (kleinrob) Feature #319895, revision 1 Title: Add btrfs subvolume options to autoyast openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Robert Klein (kleinrob) Partner organization: openSUSE.org Description: Currently you can't specify btrfs subvolume options is a autoYaST control file. E.g. the standard install of Leap 42.1 creates four subvolumes with option "no copy on write": - @/var/lib/libvirt/images - @/var/lib/mariadb - @/var/lib/mysql - @/var/lib/pgsql There ought to be a way to achieve this with autoYaST. Currently subvolumes are specified as: <subvolumes config:type="list"> <listentry>boot/grub2/i386-pc</listentry> <listentry>boot/grub2/x86_64-efi</listentry> <listentry>home</listentry> </subvolumes> a possibly syntax could be e.g.: <subvolumes config:type="list"> <subvolume> <subvolume-path>var/lib/pgsql</subvolume-path> <subvolume-options>nodatacow,noacl</subvolume-options> </subvolume> </subvolumes> or make the subvolume-options a list.. Also the installer should respect these options and autoyast should use them when creating a reference profile. -- openSUSE Feature: https://features.opensuse.org/319895

1 2

[New: openFATE 313233] Get Zypper to remove installed patterns
by fate_noreply＠suse.de 15 Jan '16

15 Jan '16

Feature added by: Drew Adams (Druonysus) Feature #313233, revision 1 Title: Get Zypper to remove installed patterns openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Drew Adams (druonysus) Partner organization: openSUSE.org Description: Get Zypper to remove a pattern. Zypper can install a pattern nut when going to remove that same pattern, Zypper does not remove that pattern... When do a: "zypper rm -t pattern <pattern name>" Zypper, just tells you: "Uninstallation of a pattern is currently not defined and implemented." You CAN remove a pattern in YaST so I would think that there should be a way to remove the pattern with Zypper. "yum groupremove <group name>" works on Fedora/CentOS/RHEL... we should really have this working to keep up with them. Use Case: If I build a bare openSUSE image on SUSE Studio, and I decide not to install yast and only Zypper... I will only be able to install patterns but NO way to remove it. -- openSUSE Feature: https://features.opensuse.org/313233

1 2

[New: openFATE 312293] Option to disable disk check on certian volumes in YaST
by fate_noreply＠suse.de 04 Jan '16

04 Jan '16

Feature added by: Dean Hilkewich (deanjo13) Feature #312293, revision 1 Title: Option to disable disk check on certian volumes in YaST openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Dean Hilkewich (deanjo13) Partner organization: openSUSE.org Description: This is one really really really annoying feature in yast. Here is the scenario, you have a machine with a bunch of storage drives, drives that are normally kept full. Everytime you enter something like package management in YaST it pops up a low disk space warning. This warning should only apply for volumes where YaST utilizes for it's files (such as download cache, home, etc). A HTPC for example often has volumes full to the max. -- openSUSE Feature: https://features.opensuse.org/312293

1 1

[New: openFATE 318082] [Shell][Scripting] Shell-reqs command
by fate_noreply＠suse.de 19 Dec '15

19 Dec '15

Feature added by: Sławomir Lach (Lachu) Feature #318082, revision 1 Title: [Shell][Scripting] Shell-reqs command openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Idea is about creating tool, which checks that given programs are installed. If some program aren't installed then it call special program(dependent on user is working on console and GUI environment), which displays cnf output for missing programs. On program missing return code is not 0, so script can terminate. Idea was proposed by some Red Hat's developers many years ago, but this idea was about to automatically install tools from standard repositories. Use Case: Marek is normal computer user. He decided to download script, but to run correctly script needs some command. This script can looks like this: #!/bin/bash shell-reqs command1 command2 if [ $? -eq 1 ]; then exit fi; command1 parameter1 parameter2 command2 parameter1 parameter2 parameter3 When he run this script, desktop environment reports that command1 and command2 is missing and suggest how to install these commands. Marek will install these commands and rerun script. -- openSUSE Feature: https://features.opensuse.org/318082

1 2

[openFATE 309385] Improve "Pattern" handling
by fate_noreply＠suse.de 18 Dec '15

18 Dec '15

Feature changed by: Ludwig Nussel (lnussel) Feature #309385, revision 42 Title: Improve "Pattern" handling openSUSE-11.3: Rejected by Andreas Jaeger (a_jaeger) reject date: 2013-08-09 13:10:33 reject reason: Not done for 11.3. Priority Requester: Important - openSUSE Distribution: Unconfirmed - Priority - Requester: Important Requested by: Michael Andres (mlandres) Partner organization: openSUSE.org Description: We need to clearly define the way to deal with patterns. - The code11 decision not to install pattern makes them hard to handle. The solver not knowing which patterns were actually selected by the user results in bugs like https://bugzilla.novell.com/show_bug.cgi?id=576059 or https://bugzilla.novell.com/show_bug.cgi?id=676994. It also produces poor results on upgrades, as we can only guess which patterns should be updated. - The approach on opensuse 11.2 to use a package to represent the pattern and it's dependencies might be a step into the right direction (similar to the release-package representing a product). But the link between a pattern and it's prepresenting package is missing. This leads to bugs like https://bugzilla.novell.com/show_bug.cgi?id=592640, where actions like 'set Taboo' on patterns have no effect, because we don't know, thus can't lock, the corresponding package. Another open issue is removal of patterns like in https://bugzilla.novell.com/show_bug.cgi?id=407040. Removing the pattern package with cleanup enabled could be an option. This also requires a link between pattern and package. Whithout a decision accepted by all stakeholders, libzypp/zypper won't be able to resolve several bugs satisfactory. Discussion: #19: Michael Andres (mlandres) (2014-01-27 11:35:53) Done in libzypp-14.7.0 / libsolv-0.4.2 for alpha3. We should be able to drop the old pattern metadata files. -- openSUSE Feature: https://features.opensuse.org/309385

1 0

[New: openFATE 320184] Session rescue mode
by fate_noreply＠suse.de 12 Dec '15

12 Dec '15

Feature added by: Sławomir Lach (Lachu) Feature #320184, revision 1 Title: Session rescue mode openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: There should exist (optional) way to made rescue of user session possible. Systemd-logind should use cgroups to preserve memory for session rescue process(for each session some bulk of memory should been reserved). This memory could be used only by process in specify cgroup, like process manager, window manager and X server. Other idea is to pause any process not belongs to privileged cgroup, to avoid problems with CPU/IO usage, when some keyboard combination was used. Optional idea is to allow use of reserved memory by special keyboard combination(the same, which pauses process). Access to additional memory could been made by special kernel call, but I'm not sure this is necessary. Use Case: Martin have computer with only 2GiB of memory. He wants to run broken sword installer gained from gog.com. System hangs, so he click ctrl+esc, all other processes than window manager, X and process manager pauses and not paused process could allocate additional memory. He selects broken process, kill it and click ctrl+esc to bring session work again. Business case (Partner benefit): openSUSE.org: System could have problems, while a lot of memory are used, so we need to reserve memory for special purposes. -- openSUSE Feature: https://features.opensuse.org/320184

1 0

[openFATE 305914] PAC support for 'system wide proxy configuration'
by fate_noreply＠suse.de 05 Dec '15

05 Dec '15

Feature added by: Dominique Leuenberger (dimstar) Feature #305914, revision 1, last change by Title: PAC support for 'system wide proxy configuration' openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Dominique Leuenberger (dimstar) Description: The distribution now contains libproxy and we should try to make as much use of it as possible. A big advantage is the ability to parse PAC (Proxy AutoConfiguration) without the need for this in every application. Simply linking against libproxy with it's very simple API (3 API calls, 2 without parameters) is enugh to have the advantage of no longer needing to 'guess' what proxy to use. What is now: - You can set in yast / proxy a general proxy to be used (http://foo.proxy.com:1234) This is bascially put into http_proxy envvar. In gnome you can set user proxy configuration as: - Use System Proxy (as configured in yast) - Use proxy configuration (static, same options as in yast) - Use automatic proxy configuration script Yast lacks the option to specify a PAC script on system wide level. This is only possible in the user sessions configuration. This made sense as most applications don't know how to handle pac files anyway. But with libroxy, this hurdle can be taken away from every single application and can thus be offered. I'm glad to elaborate on questions; I'm sure there are some :-) -- openSUSE Feature: https://features.opensuse.org/305914

1 17