August 2015 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 312277] Include GNOME Tweak
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Anomyous Anomyous (jcat123) Feature #312277, revision 1 Title: Include GNOME Tweak openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Anomyous Anomyous (jcat123) Partner organization: openSUSE.org Description: Recently I have tried GNOME 3. There are several settings that you once could customize in GNOME 2 that you can't do in GNOME 3. There is a package called gnome-tweak-tool, that lets you customize things like the Theme again. This should be included on the distribution DVD (and perhaps Live CD too) for openSUSE 12.1. -- openSUSE Feature: https://features.opensuse.org/312277

1 4

[New: openFATE 312209] GTK+ client for Smolt
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Vaibhav Mathur (trojanware) Feature #312209, revision 1 Title: GTK+ client for Smolt openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Vaibhav Mathur (trojanware) Partner organization: openSUSE.org Description: A gtk client for smolt would enable it it to be bundled with the default distribution of openSUSE. -- openSUSE Feature: https://features.opensuse.org/312209

1 2

[New: openFATE 310490] Develop and add a GTK smolt client to openSUSE
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Luis Medinas (lmedinas) Feature #310490, revision 1 Title: Develop and add a GTK smolt client to openSUSE openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Luis Medinas (lmedinas) Partner organization: openSUSE.org Description: Smolt is a project that is picking stats about openSUSE installs. Currently smolt-gui developed upstream is written in Qt and it difficult to add this client to GNOME installation of openSUSE. So it's required to have a GNOME integration to ship on the default install. It's important to have a GTK client similar to smolt-gui and ksmolt (which is the notification service launched on KDE). Use Case: User installs openSUSE GNOME and in the first run it shows a notification asking for the user to submit the hardware data to smolt. If necessary launch a smolt GTK client to send the data. Business case (Partner benefit): openSUSE.org: Most of GNOME users aren't submitting openSUSE stats to smolt database because smolt gui isn't integrated with GNOME. -- openSUSE Feature: https://features.opensuse.org/310490

1 2

[New: openFATE 318432] FUSE filesystem to keep /etc/ valid
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Sławomir Lach (Lachu) Feature #318432, revision 1 Title: FUSE filesystem to keep /etc/ valid openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Editing files is road of pain. User can destroy file, so system can be broken. I suggest to add fuse-based file system with BFS(language to describing file structure) to keep file validated, while closed. It buffer or write in /tmp every write operation and check consistency on file close. If file is good, filesystem will replace file placed in /etc. -- openSUSE Feature: https://features.opensuse.org/318432

1 4

[New: openFATE 311136] Use the community repos list to remove repos
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Sven Burmeister (rabauke) Feature #311136, revision 1 Title: Use the community repos list to remove repos openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Sven Burmeister (rabauke) Partner organization: openSUSE.org Description: If the user adds a repo via the community repos list he should be able to remove them via the same way, i.e. have a list where he can de-select and thus remove the repos. That way if he e.g. added some repo which messed-up his system he could just bring up that same list de-select the repo and yast would "update" all installed packages from that repo to the original state and remove the repo afterwards. In YaST's software management it's the same, you add/remove/refresh from within the same list. -- openSUSE Feature: https://features.opensuse.org/311136

1 1

[New: openFATE 312962] Include acpi_osi=Linux pcie_aspm=force by default for Grub boot parameters
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Roger Luedecke (Shadowolf7) Feature #312962, revision 1 Title: Include acpi_osi=Linux pcie_aspm=force by default for Grub boot parameters openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Roger Luedecke (shadowolf7) Partner organization: openSUSE.org Description: acpi_osi=Linux identifies the OS to the BIOS helping fix power and other issues. pcie_aspm=force fixes power regression issue shown here; http://www.phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1 -- openSUSE Feature: https://features.opensuse.org/312962

1 8

[New: openFATE 314585] Reinstate KNode
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Christopher Yeleighton (yecril71pl) Feature #314585, revision 1 Title: Reinstate KNode openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Christopher Yeleighton (yecril71pl) Partner organization: openSUSE.org Description: KNode has been removed from the KDE pattern in openSUSE; it is not installed by default in 12.2. The results: 1. The news URL scheme is not recognized. 2. The nntp URL scheme is handled by Dolphin, which is basically unable to handle it. Test Case: { xdg-open 'news:news.answers'; } Business case (Partner benefit): openSUSE.org: News is one of the basic protocols of the Internet, and failing to support it is a shame. -- openSUSE Feature: https://features.opensuse.org/314585

1 2

[openFATE 307746] Yast2-UI to mount remote Samba/CIFS-shares
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Alex Müller (Larx) Feature #307746, revision 1 Title: Yast2-UI to mount remote Samba/CIFS-shares openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Alex Müller (larx) Description: At the moment there is no working Yast2-module to simply mount remote SAMBA/CIFS shares the "unix way" (i.e. with a directory entry in the filesystem a la "/network/sharename/"). (yast2-samba-client seems to offer this as "expert option", however I don't get it to work.) The different desktop environments offer access with the "smb:/"-protocol, however this doesn't work really consistently. E.g. it doesn't help with consoles and scripts, and even some desktop apps, namely KDE's own Amarok, refuse to use the smb:/-protocol. So I think a Yast2-module - which should be simple to do, as it would only be a frontend to /etc/fstab or /etc/samba/smbfstab - to mount SAMBA shares should be implemented. -- openSUSE Feature: https://features.opensuse.org/307746

1 5

[New: openFATE 317297] YaST2 software manager changes
by fate_noreply＠suse.de 06 Dec '16

06 Dec '16

Feature added by: John Shand (jshand2013) Feature #317297, revision 1 Title: YaST2 software manager changes openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: John Shand (jshand2013) Partner organization: openSUSE.org Description: there are a few distributions that are offering a rolling update release, which means you don't need to install the system ever again or update manually. The idea is that when a new stable release is released, it will give the user a message asking them if they would like to upgrade their system to the newer version. -- openSUSE Feature: https://features.opensuse.org/317297

1 4

[New: openFATE 312174] Kpackagekit: Patches by default, other updates optional
by fate_noreply＠suse.de 04 Dec '16

04 Dec '16

Feature added by: Jean Cayron (jeancayron) Feature #312174, revision 1 Title: Kpackagekit: Patches by default, other updates optional openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Jean Cayron (jeancayron) Partner organization: openSUSE.org Description: Since 11.4, the official updater in KDE is now kpackagekit and not kupdateapplet anymore. It gives you by default the notification of patches but also the packages on all the repos enabled. For a power user it's a nice feature but for a basic user or a user that wants to have choice in softwares but just wants the system to work, it's anoying. Even with few additional repos, it'll give you a huge amount of updates. For example, you've got just the packman repo enabled, there'll be lots of "micro" version updates (a bit everyday). If you've got to many updates, you won't take the time to sort them, you'll install them all to be no more notified. An official patch from the update-repo is an update that was tested to not break the system. I shouldn't affect stability or functionalities. An update on an additional repo isn't tested as much as a patch. You take always a risk to beak something in your system by using an aditionnal repo. You multiply the risk if you update the same packages constantly. Updating takes also a lot of memory. On low ram systems (like netbooks), it's anoying and can make your system unusable for the time of the update. In few word, update everything possible is bad for stability and uses a lot of memory. In kpackagekit you don't have the choice : - If you remove the other repositories in the preferences, it'll remove it from zypper and yast as well (and you must launch kpk as root to do it, even as it gives the impression you can do it as a normal user). - If you only choose to apply the patches, it's time consuming (click, click, click) and you're constantly left with a notification that you've got X updates. Solution : Kpackagekit should by defalut have the option to list/apply only patch from the official update repo as updates. The listing/apply of other updates should be activated optionaly. -- openSUSE Feature: https://features.opensuse.org/312174

1 1