September 2008 - openSUSE Features - openSUSE Mailing Lists

[openFate 305144] [Feature-request] Yast as a Linux learning tool
by fate_noreply＠suse.de 30 Jan '18

30 Jan '18

Feature added by: Arvin Schnell <aschnell(a)novell.com> Feature #305144, revision 1, last change by Title: [Feature-request] Yast as a Linux learning tool openSUSE-11.1: New Priority Requester: Desirable Requested by: Alexey Eremenko <al4321(a)gmail.com> Partner organization: openSUSE.org Description: Hi All ! I Have very good new idea: converting Yast into a Linux learning tool. This is very simple to achieve: Yast must show the commands it executes and files it modifies, in a nice GUI dialog. It will allow all kinds of Linux users understand how things really work. Enable learn new things or remind how old-but-forgotten things work for seasoned people. Great, isn't it ? P.S. Jay Vollmer recommends, that among the commands that Yast shows as it executing, it should also recommend "man pages" for the relevant underlying commands. -- -Alexey Eromenko "Technologov", 29.jul.2008. Discussion: #1: Alexey Eremenko <al4321(a)gmail.com> (2008-07-29 12:09:11) Rajko M. wrote: If one wants to see what is gong on in background, than look at logs in realtime. There is console (Konsole) and command tail. Run as root: tail -f /var/log/YaST2/y2log and then start YaST and play with. -- -Alexey Eromenko "Technologov", 29.jul.2008. #2: Jerry Houston <jerry.houston(a)comcast.net> (2008-07-29 15:41:34) Sounds like a great way for new users to learn more about what's under the hood. Or, what's under the bonnet, for the Brits. #3: Cyril Hrubis <chrubis(a)novell.com> (2008-07-31 07:11:21) Moving to maintainers to decide. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305144

1 19

[openFate 305305] 1-click uninstall
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Michael Loeffler <michl(a)novell.com> Feature #305305, revision 1, last change by Title: 1-click uninstall openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Michael Loeffler <michl(a)novell.com> Partner organization: openSUSE.org Description: An easy way to remove Software! For example: you installed an application with "1-click install" (which will install all the packages that you need), there should be an easy way (also with 1 click) to remove what you have installed with that 1-click operation... in another words: an "1-click Uninstall" to remove installed software (dependencies and packages included). -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305305

1 35

[openFate 305099] please have yast do a fsck before attempting to mount existing filesystems
by fate_noreply＠suse.de 28 Jan '15

28 Jan '15

Feature added by: Arvin Schnell <aschnell(a)novell.com> Feature #305099, revision 1, last change by Title: please have yast do a fsck before attempting to mount existing filesystems openSUSE-11.2: New Priority Requester: Important Requested by: Per Jessen <per.jessen(a)enidan.com> Partner organization: openSUSE.org Description: I was doing a new install, but wanted to keep my /home filesystem (JFS). No problem, except that the filesystem wasn't clean and needed an fsck. As far as I can tell, yast didn't do this, so mounting of the /home filesystem failed, which caused the entirely installation process to abend and start over. Discussion: #1: Stefan Hundhammer <sh(a)novell.com> (2008-02-21 06:26:43) I'd really hate to have my 100+ GB ext3 partitions fscked. That takes forever. #2: Per Jessen <per.jessen(a)enidan.com> (2008-02-21 07:15:33) Even when they're clean? It's done on every bootup anyway. See /etc/init.d/boot.localfs #3: Jozef Uhliarik <juhliarik(a)novell.com> (2008-02-21 08:21:41) What is your opinion Thomas? #4: Thomas Fehr <fehr(a)novell.com> (2008-02-21 08:24:13) That would need an feature request, not a bug report. #6: Stephan Kulow <coolo(a)novell.com> (2008-02-21 12:04:27) I think it's not too uncommon that people reinstall their system _because_ the old one had a problem, so dirty file systems may not be too uncommon. #7: Thomas Fehr <fehr(a)novell.com> (2008-02-25 03:00:03) What the customer described happens on JFS, this is an unsupported filesystem exactly for the reason that it behaves quite fundamentally different to most other filesystems. Filesystems like ext3 or reiser simply do their log reply when they are dirty and all is fine. So if you want such things to be added, please specify it as a feature request. Since there needs to be an interactive user interface to the filesystem check program this is in no way a simple change. Or would you prefer for example do a rebuild of reiserfs internal tree as default without asking the user first? Problem is that the questions the filesystem check tools ask the user are quite special and of course totally different for different filesystem types. #8: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-07-17 08:13:00) I happen to suffer from this bug too once. I think the bug is not that the installation cleans the disk, but at least say that is not clean instead of crashing (in my case it was an installation where yast thought the disk was mounted but it was not) #9: Arvin Schnell <aschnell(a)novell.com> (2008-07-17 08:22:23) No time for 11.1. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305099

1 9

[openFate 305249] Remove agfa-fonts from openSUSE 11.1
by fate_noreply＠suse.de 22 Jul '14

22 Jul '14

Feature added by: Michael Loeffler <michl(a)novell.com> Feature #305249, revision 1, last change by Title: Remove agfa-fonts from openSUSE 11.1 openSUSE-11.1: Evaluation Priority Requester: Important Requested by: Michael Loeffler <michl(a)novell.com> Partner organization: openSUSE.org Description: As Liberation fonts looking really good meanwhile I propose to replace the proprietary agfa-fonts with the open source fonts for openSUSE 11.1 and future versions. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305249

1 17

[openFate 305112] Add webcam configuration module for yast
by fate_noreply＠suse.de 19 Oct '12

19 Oct '12

Feature added by: Michael Loeffler <michl(a)novell.com> Feature #305112, revision 1, last change by Title: Add webcam configuration module for yast openSUSE-11.1: New Priority Requester: Desirable Requested by: Michael Loeffler <michl(a)novell.com> Partner organization: openSUSE.org Description: Webcam is configured automatically. But for users having trouble with configuration a webcam configuration module would be useful. See also bug #359729 Business case (Partner benefit): openSUSE.org: Users in trouble with webcam configuration need a webcam configuration possibility in YaST. As the usage of webcams is rising, eg. through instant messanger this feature request adresses more and more users -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305112

1 25

[openFate 305148] Automatic Compiling of Kernel Modules
by fate_noreply＠suse.de 04 Sep '12

04 Sep '12

Feature added by: Andreas Jaeger <aj(a)novell.com> Feature #305148, revision 1, last change by Title: Automatic Compiling of Kernel Modules openSUSE-11.2: New Priority Requester: Important Requested by: Andreas Jaeger <aj(a)novell.com> Partner organization: openSUSE.org Description: The Standard Linux-Kernel provides a lot of hardware drivers/kernel modules. Nevertheless there are still devices not supported by the kernel. If a user compiles a kernel module by himself, he has to redo this step after each kernel update (if he is aware at all, that this step is needed). My idea was to install kernel-source, kernel-syms, gcc and make with each standard installation and to define a standard directory for the source code of kernel modules, e.g /usr/src/updates. When a Kernel Update is done, the system looks on boot in /usr/src/updates for directories and does there a 'make' and 'make install'. (build a kmp-package ?) If this could become a standard for other distributions (LSB) as well and corresponding init scripts would exist, third party kernel modules could be installed automagically after extracting code to /usr/src/update, so there would be some kind of standard for installing external kernel modules. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305148

1 21

[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

[openFate 305081] openSUSE Testfeature
by fate_noreply＠suse.de 11 Dec '10

11 Dec '10

Feature added by: Christopher Hofmann (cwh(a)novell.com) Feature #305081, revision 1 Title: openSUSE Testfeature openSUSE-11.1: New Priority Requester: Neutral Requested by: Christopher Hofmann (cwh(a)novell.com) Partner organization: openSUSE.org Description: Feel free to play aroud with this feature. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305081

1 34

[openFate 305312] OpenSUSE <= 11.1 Alpha 2 don't install on SD card
by fate_noreply＠suse.de 06 Oct '10

06 Oct '10

Feature added by: Arvin Schnell <aschnell(a)novell.com> Feature #305312, revision 1, last change by Title: OpenSUSE <= 11.1 Alpha 2 don't install on SD card openSUSE-11.2: New Priority Requester: Important Requested by: Harald Welte <haraldwelte(a)viatech.com> Partner organization: openSUSE.org Description: [Please note that I'm working for the CPU+Chipset maker VIA and this is an actually important feature for the 'netbook' class of devices in the coming months] Recently, BIOS vendors have been starting to implement a 'boot from SD card' feature, much like they have added 'boot from USB memory stick' some years ago. The only SD-card host controller that I've seen this implemented for is SDHCI compliant host controllers. While this is a nice feature to support, for most systems it is just a gimmick and not something neccessarry. However, there are hand-held devices such as netbooks in the pipeline which do not have any other mass storage device. No hard disk and no IDE-attached flash disk or the like. They just have one (more likely two or more) SD card slots and you install and store not only your data but the entire operating system on that SD card. Furthermore, there are products like Samsung moviNAND which are basically a SDcard in a BGA package that can be soldered onto a PCB. So from a protocol and software point of view it is a SD card, but it is mechanically soldered onto the board. Such device have gained some popularity in ARM-based designs, but we'll likely see them in the x86 world, too. To make this happen, The distribution installation initrd needs to 1. include and auto-load the sdhc.ko and sdhci_pci.ko kernel modules 2. create the /dev/mmcblk* device nodes as per udev/hotplug events The actual distribution installation program needs to 1. recognize /dev/mmcblk* as block devices that can be used as target device 2. use a grub-install or similar program that can discover the bios drive number to /dev/mmcblk* device name mapping I have outlined the full details at http://wiki.gpl-devices.org/wiki/Installing_Linux_on_booting_SD_card -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305312

1 18

[openFate 305267] Installation using Orca (screen reader) to Improve Accessibility
by fate_noreply＠suse.de 10 Aug '10

10 Aug '10

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305267, revision 1, last change by Title: Installation using Orca (screen reader) to Improve Accessibility openSUSE-11.2: New Priority Requester: Desirable Requested by: Darragh Ó Héiligh <d(a)digitaldarragh.com> Partner organization: openSUSE.org Description: Original title: Accessibility for installation could be automated with better results. Users can currently press F9 at the boot screen to hear the boot options spoken. THis is a fantastic new feature and is one that OpenSuSE is the first to add. For this you should be very proud. However, I would ask that you further build upon this success by recognising that accessibility at the boot menu has been enabled and automatically start the Orca screen reader with also setting gnome accessibility to enabled. One further consideration should be taken into account. To enable Orca to access the installation screen, Orca must be run as root. However, if Orca is run as root, the rest of the desktop is not accessible due to permissioning issues. Therefore, the installation should be run automatically if the f9 key si pressed. Note, a similar feature excluding the accessible boot menu has also been added to Ubuntu 8.04. Note that they also have a key press (F5) to automatically enable assistive technologies for installation on their live CD. References: See bnc #417874 (https://bugzilla.novell.com/show_bug.cgi?id=417874) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305267

1 5

[openFate 305104] Provide possibility to configure WEP/WPA/WPA2/... at installation
by fate_noreply＠suse.de 09 Mar '10

09 Mar '10

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305104, revision 1, last change by Title: Provide possibility to configure WEP/WPA/WPA2/... at installation openSUSE-11.1: New Priority Requester: Desirable Requested by: Jim Creech <jacreech(a)suddenlink.net> Partner organization: openSUSE.org Description: It is possible to configure a network in the first stage installation but it is only possible to select DHCP or Static + configure proxy. It is impossible to configure a secure wireless connection. See also: Bug 293609 (https://bugzilla.novell.com/show_bug.cgi?id=293609) - No provision for entering WEP at installation -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305104

1 9

[openFate 305308] Installation into Windows Partition (Wubi-like)
by fate_noreply＠suse.de 27 Aug '09

27 Aug '09

Feature added by: Stephan Binner <stbinner(a)novell.com> Feature #305308, revision 1, last change by Title: Installation into Windows Partition (Wubi-like) openSUSE-11.2: New Priority Requester: Desirable Requested by: Stephan Binner <stbinner(a)novell.com> Partner organization: openSUSE.org Description: Wubi allows the installation of Ubuntu on a MS Windows System without changing the partition setup. Users can test-drive a Linux system without major performance loss like when using a Live-CD, have data persistence beyond reboot and an easy way to deinstall like any other application after trial. References: http://wubi-installer.org , https://wiki.ubuntu.com/WubiGuide , http://en.wikipedia.org/wiki/Wubi_(Ubuntu) Business case (Partner benefit): openSUSE.org: Having a Wubi-alike installer for openSUSE would be a great way to promote openSUSE to Windows users. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305308

1 14

[openFate 305318] Move gconf schemas to /usr
by fate_noreply＠suse.de 14 Aug '09

14 Aug '09

Feature added by: Vincent Untz <vuntz(a)novell.com> Feature #305318, revision 1, last change by Title: Move gconf schemas to /usr openSUSE-11.2: New Priority Requester: Desirable Requested by: Vincent Untz <vuntz(a)novell.com> Partner organization: openSUSE.org Description: We store gconf schemas in /etc/gconf. However, the schemas are not configuration files, but simply data. Therefore, we should move the schemas to /usr. Simply changing a line in /etc/gconf/2/path should make gconf work with the new location. Note that Debian already implements this. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305318

1 7

[openFate 305149] [Feature-request] Yast Expert Partitioner: should not require mounting "/" root partition
by fate_noreply＠suse.de 14 Aug '09

14 Aug '09

Feature added by: Arvin Schnell <aschnell(a)novell.com> Feature #305149, revision 1, last change by Title: [Feature-request] Yast Expert Partitioner: should not require mounting "/" root partition openSUSE-11.2: New Priority Requester: Desirable Requested by: Alexey Eremenko <al4321(a)gmail.com> Partner organization: openSUSE.org Description: Hi All ! Since openSUSE 11.1 will have brand new expert partitioner, I would like to request the ability to use SUSE's partitioner for partition hard disks for other operating systems. Currently it is not possible, because SUSE requires mounting "/" root partition. In some cases I need to install third-party OSes before I install openSUSE, so I want to use SUSE flexible partitioner to partition and format the hard disk, then install the other OSes and only in the end I want to install openSUSE. -Alexey Discussion: #1: Arvin Schnell <aschnell(a)novell.com> (2008-08-04 08:41:18) So in a nutshell you want to use the partitioner as a separate program (started from the DVD) without the other installation features like package managment. Right? #2: Arvin Schnell <aschnell(a)novell.com> (2008-08-05 12:11:02) Not mounting "/" during installation will certainly lead to a failure so I hesitate to remove the check. But we could add a special mode with disabled checks. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305149

1 9

[openFate 305146] Use old system network configuration when updating instead of demanding a new one
by fate_noreply＠suse.de 24 Jun '09

24 Jun '09

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305146, revision 1, last change by Title: Use old system network configuration when updating instead of demanding a new one openSUSE-11.2: New Priority Requester: Desirable Requested by: Pacho Ramos <pacho(a)condmat1.ciencias.uniovi.es> Partner organization: openSUSE.org Description: Currently, when I try to update from opensuse 10.3 to 11.0 with DVD and I want to add network repositories, I have to configure again my network for opensuse installer even when it is already configured on my opensuse-10.3 I think that would be much better try to use network configuration from old installation and only ask user if a problem occurs Business case (Partner benefit): openSUSE.org: System update from media: Start installation / Update, select network-based repositories to be used, you will be asked to configure the network. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305146

1 5

[openFate 305272] Definition in the Yast2 samba server module for "workgroup" host
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305272, revision 1, last change by Title: Definition in the Yast2 samba server module for "workgroup" host openSUSE-11.2: New Priority Requester: Desirable Requested by: Andreas van dem Helge <andrew(a)joako.net> Partner organization: openSUSE.org Description: Add a definition in the samba server module for "workgroup" host. I.E. in a SOHO it isn't always necessary to setup a true "domain" server, however if there were a set of options for things like "LMB" aka "local master browser" and a quick set of clicks to join a "Workgrp" as a client. this tutorial highlights the amount of script editing that could be avoided if the samba server were more "workgroup" friendly http://www.swerdna.net.au/linhowtolanprimer.html#samba (http://www.swerdna.net.au/linhowtolanprimer.html#samba) References: Originally reported as BNC #420766 (https://bugzilla.novell.com/show_bug.cgi?id=420766) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305272

1 3

[openFate 305170] openFATE test
by fate_noreply＠suse.de 05 Mar '09

05 Mar '09

Feature added by: Michael Loeffler <michl(a)novell.com> Feature #305170, revision 1, last change by Title: openFATE test openSUSE-11.1: Evaluation Priority Requester: Mandatory Requested by: Michael Loeffler <michl(a)novell.com> Partner organization: openSUSE.org Description: test Business case (Partner benefit): openSUSE.org: sdf -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305170

1 5

[openFate 305162] Support Ext4 in Grub
by fate_noreply＠suse.de 18 Jan '09

18 Jan '09

Feature added by: coly li <coyli(a)novell.com> Feature #305162, revision 1, last change by Title: Support Ext4 in Grub openSUSE-11.1: New Priority Requester: Important Requested by: coly li <coyli(a)novell.com> Partner organization: openSUSE.org Description: Ext4 is in upstream kernel already. But since lack of grub legacy supporting, Ext4 can not be used as booting partition. By effort of opensuse's GSoC project, Ext4 stage1.5 is aded into grub legacy. We should consider adding the feature in next opensuse release. Code can be found from http://code.google.com/p/grub4ext4/downloads/list -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305162

1 10

[openFate 303520] Default NTP Setup
by fate_noreply＠suse.de 30 Sep '08

30 Sep '08

Feature changed by: Karl Eichwalder <ke(a)novell.com> Feature #303520, revision 21 Title: Default NTP Setup openSUSE-11.1: Done Priority Requester: Mandatory Projectmanager: Mandatory SLED-11: Done Priority Requester: Mandatory Projectmanager: Mandatory SLES-11: Done Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Federico Lucifredi <flucifredi(a)novell.com> Partner organization: openSUSE.org Description: A Yast pane should prompt for NTP set up, which should be configured by default, but of course can also be disabled there. Documentation Impact: Installation guide needs to be updated. + [0123].opensuse.pool.ntp.org mentioned for openSUSE. + If you want me to document something for SLE11, please set the Doc + Status accordingly. Discussion: #1: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-17 12:56:47) Federico, NTP setup is already possible. Do you want it in a more prominent place? Also I see a missing way for the product to pre-define the value, correct? #2: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-23 21:03:12) (reply to #1) right. I want to see it pre-enabled by default againt a dedicated suse. pool.ntp.org / time.novell.com server (separate feature for that). We are lagging a bit behind Win and Mac where the vendos provide their own time source, and we need to catch up there. #3: Jiri Srain <jsrain(a)novell.com> (2008-07-07 12:18:32) We will need not only to enable NTP during installation, but display this information in the installation proposal (and possibly time zone dialog) as well. #6: Jiří Suchomel <jsuchome(a)novell.com> (2008-08-12 13:27:44) (reply to #3) OK, this (http://w3.suse.de/~jsuchome/screenshots/yast2-timezone-ntp-status.png) is proposal how to show the info in current time zone dialog. It is probably bad that status is part of the frame label, but I didn't want to take more space from the whole dialog by adding new line... #4: Stephan Kulow <coolo(a)novell.com> (2008-07-31 16:15:46) for openSUSE it's 0.opensuse.pool.ntp.org 1.opensuse.pool.ntp.org 2. opensuse.pool.ntp.org 3.opensuse.pool.ntp.org, for SLE there is no NTP server. time.novell.com can not be used, IS&T does not provide that level of service. #7: Jiří Suchomel <jsuchome(a)novell.com> (2008-09-02 16:05:00) Alpha2 solution is working, to solve remaining issues there is a bug 422128. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303520

1 0

[openFate 305131] connecting an unpartitioned disk should bring up a partitioner
by fate_noreply＠suse.de 26 Sep '08

26 Sep '08

Feature changed by: Christian Zoz <zoz(a)novell.com> Feature #305131, revision 6 Title: connecting an unpartitioned disk should bring up a partitioner - openSUSE-11.1: Evaluation + openSUSE-11.1: Rejected by Christian Zoz <zoz(a)novell.com> + reject date: 2008-09-26 13:28:38 + reject reason: No easy solution and to late now. Priority Requester: Desirable Projectmanager: Desirable Requested by: Juergen Weigert <jw(a)novell.com> Partner organization: openSUSE.org Description: USB or Firewire disks can be easily connected at runtime. For a newly bought disk, nothing happens, when it is connected for the first time. Unlike e.g. a USB-Memory-stick, which immediatly opens a filebrowser, when first connected. The technical difference is, disks come unformatted, USB-sticks come formatted. We should recognize this difference and pop up an easy to use partitioner. Discussion: #1: Stefan Behlert <behlert(a)novell.com> (2008-08-18 12:52:42) Christian, would it be possible to use HAL or something like that to pop-up the Yast-partitioner? I don't think we will get a stripped down partitioner at the moment for 11.1. #2: Danny Kukawka <dkukawka(a)novell.com> (2008-09-25 18:48:47) (reply to #1) No, HAL can't and shouldn't popup anything. It's up to the desktop (e.g. suse-plugger) to check the HAL events if a device get added to the machine and react on this. + #3: Christian Zoz <zoz(a)novell.com> (2008-09-26 13:28:09) + This must be done by the desktop. But it's to late now. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305131

1 0

[openFate 305131] connecting an unpartitioned disk should bring up a partitioner
by fate_noreply＠suse.de 25 Sep '08

25 Sep '08

Feature changed by: Danny Kukawka <dkukawka(a)novell.com> Feature #305131, revision 5 Title: connecting an unpartitioned disk should bring up a partitioner openSUSE-11.1: Evaluation Priority Requester: Desirable Projectmanager: Desirable Requested by: Juergen Weigert <jw(a)novell.com> Partner organization: openSUSE.org Description: USB or Firewire disks can be easily connected at runtime. For a newly bought disk, nothing happens, when it is connected for the first time. Unlike e.g. a USB-Memory-stick, which immediatly opens a filebrowser, when first connected. The technical difference is, disks come unformatted, USB-sticks come formatted. We should recognize this difference and pop up an easy to use partitioner. Discussion: #1: Stefan Behlert <behlert(a)novell.com> (2008-08-18 12:52:42) Christian, would it be possible to use HAL or something like that to pop-up the Yast-partitioner? I don't think we will get a stripped down partitioner at the moment for 11.1. + #2: Danny Kukawka <dkukawka(a)novell.com> (2008-09-25 18:48:47) (reply to + #1) + No, HAL can't and shouldn't popup anything. It's up to the desktop (e.g. + suse-plugger) to check the HAL events if a device get added to the + machine and react on this. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305131

1 0

[openFate 301919] Ship nspluginwrapper to better support 32bit Firefox plugins on 64bit systems
by fate_noreply＠suse.de 16 Sep '08

16 Sep '08

Feature changed by: Stanislav Brabec <sbrabec(a)novell.com> Feature #301919, revision 26 Title: Ship nspluginwrapper to better support 32bit Firefox plugins on 64bit systems openSUSE-10.3: Done Priority Requester: Mandatory Projectmanager: Mandatory SLED-11: Candidate Priority Requester: Mandatory Projectmanager: Important Archs: i386, x86-64 SLES-11: Candidate Priority Requester: Mandatory Projectmanager: Important Requested by: Klaus Kämpf <kkaempf(a)novell.com> Partner organization: openSUSE.org Description: As of openSUSE 10.2, components of the Mozilla browser suite are building on 64bit. However, plugin compatibility is suffering (e.g. flash-player not working). The nspluginwrapper (available at freshmeat (http://freshmeat.net/projects/nspluginwrapper) fixes these issues nicely References: https://bugzilla.novell.com/show_bug.cgi?id=229257 Discussion: #1: Andreas Jaeger <aj(a)novell.com> (2007-07-27 10:04:18) We're shipping nspluginwrapper now. Unfortunately it does not handle Java yet. #2: Gary Ekker <gekker(a)novell.com> (2008-05-28 20:34:33) Michael, what would it take to finish this off for 11.1 and SLED11? #3: Stefan Behlert <behlert(a)novell.com> (2008-07-01 23:30:58) (reply to #2) Michael? #6: Gary Ekker <gekker(a)novell.com> (2008-09-08 15:30:29) Michael Wolf: It looks like nspluginwrapper itself needs some love in order to get it to support the java plugin reasonably. See http://gwenole.beauchesne.info/en/blog/2008/07/06/nspluginwrapper_1.1.0, a blog entry written about two months ago by nspluginwrapper's maintainer. + #8: Stanislav Brabec <sbrabec(a)novell.com> (2008-09-16 15:23:24) + Unless you will explicitly request update to development version 1.1.0 + (which supports windowless plugin in Flash 10 and restart plugin after + crash) or 1.2.0 (not yet written, should support Java plugin), I would + consider this feature as done for both 11.1 and SLED11. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=301919

1 0

[openFate 303527] Resolve dependencies after ignoring package download failure
by fate_noreply＠suse.de 12 Sep '08

12 Sep '08

Feature changed by: Ladislav Slezak <lslezak(a)novell.com> Feature #303527, revision 17 Title: Resolve dependencies after ignoring package download failure - openSUSE-11.1: Candidate + openSUSE-11.1: Done Priority Requester: Desirable Projectmanager: Desirable Requested by: Ján Kupec <jkupec(a)novell.com> Partner organization: openSUSE.org Description: YaST and Zypper should run the solver before resuming installation if download of a package fails and the user chooses to ignore that package. Currently YaST continues withough solving which makes the ignore button useful only if the user knows how the missing package will affect the system. References: https://bugzilla.novell.com/show_bug.cgi?id=340345#c4 http://lists.opensuse.org/zypp-devel/2008-03/msg00025.html Documentation Impact: Check whether this has documentation impact Discussion: #1: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-13 15:13:41) bit of a corner case. #2: Ján Kupec <jkupec(a)novell.com> (2008-06-16 11:44:24) Well, yes. An idea to cover it easily to some extent: let's advice users to run 'zypper verify' (or the YaST equivalent) in such case, after the installation is finished. This will fix hard dependencies. #3: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-24 15:32:30) (reply to #2) Yes, I would just suggest to add a message with instructions for the user. #4: Jiri Srain <jsrain(a)novell.com> (2008-07-11 10:22:19) (reply to #3) That should be pretty simple. #5: Ján Kupec <jkupec(a)novell.com> (2008-09-12 11:09:55) done in zypper, handing over to Lada for YaST + #6: Ladislav Slezak <lslezak(a)novell.com> (2008-09-12 16:00:59) (reply + to #5) + Implemented in yast2-2.17.23. + After pressing [Ignore] user is advised to run the Software Management + module (sw_single) to verify the system later. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303527

1 0

[openFate 302119] Load package selector and libzypp only when needed
by fate_noreply＠suse.de 12 Sep '08

12 Sep '08

Feature changed by: Stanislav Visnovsky <visnov(a)novell.com> Feature #302119, revision 30 Title: Load package selector and libzypp only when needed openSUSE-10.3: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2007-08-01 16:40:54 reject reason: Postponing. Priority Requester: Desirable Projectmanager: Important openSUSE-11.0: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-04-28 13:42:30 reject reason: Did not make it, postponing. Priority Requester: Desirable Projectmanager: Important - openSUSE-11.1: Evaluation + openSUSE-11.1: Rejected by Stanislav Visnovsky <visnov(a)novell.com> + reject date: 2008-09-12 14:13:58 + reject reason: Postponing. Priority Requester: Desirable Projectmanager: Important + openSUSE-11.2: New + Priority + Requester: Desirable Requested by: Stefan Hundhammer <sh(a)novell.com> Partner organization: openSUSE.org Description: The YaST2 UI should load the code for the package selector and libzypp only when needed. Not all applications / YaST2 modules need package selection code, yet for all of them the respective code from the YaST2 UI and libzypp is loaded. Discussion: #1: Stefan Hundhammer <sh(a)novell.com> (2007-04-13 18:13:44) In the YaST2 Qt the package management related code is now moved to a separate plugin that is loaded upon demand only if the calling YCP application actually requests a PackageSelector widget. This reduces the memory footprint from 20 MB VmRSS minimum (HelloWorld. ycp) to 18 MB minimum (PackageSelector-empty.ycp). #3: Katarina Machalkova <kmachalkova(a)novell.com> (2007-04-16 14:41: 35) Stano, do we want this for curses UI as well? If yes, than it's not 'done' ... #4: Stanislav Visnovsky <visnov(a)novell.com> (2007-04-16 14:47:02) (reply to #3) Agreed. Reopening for ncurses and possibly gtk+. #5: Jiri Srain <jsrain(a)novell.com> (2007-06-13 13:54:26) JP, both Qt and NCurses are done, but GTK is still missing. #6: Stefan Hundhammer <sh(a)novell.com> (2007-06-13 15:08:58) Looks like yast2-pkg-bindings are also loaded unconditionally. It shouldn't be too hard to do that with "lazy initialization" like UI built-ins: Postpone loading the Y2Component until it's really needed. #7: Stanislav Visnovsky <visnov(a)novell.com> (2007-06-19 15:01:54) (reply to #6) Jiri, if Pkg bindings problem is not addressed, it does not make sense to fix Gtk UI. #8: Jiri Srain <jsrain(a)novell.com> (2007-07-18 13:59:50) (reply to #7) Sorry for missing this. Martin, please, solve this for the Pkg bindings. #10: Stanislav Visnovsky <visnov(a)novell.com> (2007-11-08 11:38:22) (reply to #9) Please, follow up on this. #11: Martin Vidner <mvidner(a)novell.com> (2008-04-10 15:23:51) yast2-perl-bindings-2.16.6 no longer links to libzypp, which means libzypp will not be loaded at the very start of yast (perl still will be loaded, but that is relatively cheap). That helps in some cases, but mostly it only delays loading of libzypp, which occurs as soon as Pkg (or Package) is imported. Now I need to make Pkg lazy. #12: Martin Vidner <mvidner(a)novell.com> (2008-04-21 15:32:09) I have it almost working, but got stopped by bug 381917 (https://bugzilla.novell.com/show_bug.cgi?id=381917) : problems with destructors of static objects #13: JP Rosevear <jpr(a)novell.com> (2008-07-21 13:59:18) (reply to #12) Martin, what's the status here? Will we need to do anything explicit in packagekit to get this functionality? #14: Stanislav Visnovsky <visnov(a)novell.com> (2008-09-08 16:44:06) (reply to #13) There is nothing regarding packagekit for this feature. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=302119

1 0

[openFate 303517] Configure a cronjob for refreshing repositories
by fate_noreply＠suse.de 12 Sep '08

12 Sep '08

Feature changed by: Stanislav Visnovsky <visnov(a)novell.com> Feature #303517, revision 22 Title: Configure a cronjob for refreshing repositories - openSUSE-11.1: Evaluation + openSUSE-11.1: Rejected by Stanislav Visnovsky <visnov(a)novell.com> + reject date: 2008-09-12 14:12:10 + reject reason: Postponing. Priority Requester: Desirable - Projectmanager: Mandatory + Projectmanager: Important + openSUSE-11.2: New + Priority + Requester: Desirable Requested by: Ladislav Slezak <lslezak(a)novell.com> Partner organization: openSUSE.org Description: Autorefresh configured repositories at certain times, this could be on certain days, or time of day, etc. A mockup and more details are in https://bugzilla.novell.com/show_bug.cgi?id=346966 Discussion: #1: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-13 15:12:52) there are some caveats I can think of requiring silent fail (for instance, a laptop), or requiring randomization (not hitting NCC with a volley all at the same time), but I think the idea is good. #2: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-07-07 11:13:37) If you think you can make it work in a reliable way, please present a concept. Right now PackageKit and updater applets do refresh often before checking for updates so the system repos _are_ refreshed. So I don't see much value in this feature (unless a concept is presented). #3: Stanislav Visnovsky <visnov(a)novell.com> (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: Jiri Srain <jsrain(a)novell.com> (2008-07-07 12:58:59) (reply to #3) You mean running online update from cron? It should involve metadata refresh, but I do not see any reason for a separate metadata download from cron. #5: Ladislav Slezak <lslezak(a)novell.com> (2008-07-09 10:30:09) (reply to #4) The feature should allow to disable "autorefresh" flag for all repositories so the package management can be started quickly without connecting to network. The cronjob would keep the metadata uptodate. Of course, there might be a problem when metadata are changed too often on the server, but in my opinion that's not a usual case in the real world. #6: Jiri Srain <jsrain(a)novell.com> (2008-07-10 12:16:08) Let's extend the "automatic online update" module so that it offers whether to do real automatic online update, or just refresh the metadata (via one check box) #8: J. Daniel Schmidt <jdsn(a)novell.com> (2008-07-18 18:13:38) (reply to #6) This would hide the feature in an update related module. But the feature does not restrict this only to update repositories. Build-Service Repos might need a refresh as well or think of Factory. The right place for this feature is the Repository Manager. It has no relation to the update process or a configuration concerning updates. #7: Jiří Suchomel <jsuchome(a)novell.com> (2008-07-14 14:46:01) Daniel, what's the status of the plan to merge "online update configuration" into registration module? #9: J. Daniel Schmidt <jdsn(a)novell.com> (2008-07-18 18:15:46) (reply to #7) Currently I plan to merge it into a new module together with "Online Update Configuration" related settings. Please do not extend it with this unrelated repo refreshing dialog. #10: J. Daniel Schmidt <jdsn(a)novell.com> (2008-09-10 19:48:24) Why am I listed as the only developer here? I just said that I will merge the modules "automatic online update setup" and "online update setup". This feature is requesting something completely different. #11: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-09-10 22:21:17) (reply to #10) Don't worry, this feature will be dropped as because the OnStar work. It is just abandoned. #13: Jiří Suchomel <jsuchome(a)novell.com> (2008-09-11 08:20:55) (reply to #11) Really? I don't think so.This feature is aimed for opensuse (it wants to extend the current "online update setup"), while OnStar is for SLE. #12: Jiří Suchomel <jsuchome(a)novell.com> (2008-09-11 08:22:02) (reply to #10) Because the requested feature would be part of what is currently "online update setup". And after the merge, I assumed you should mainain the merged parts. #15: J. Daniel Schmidt <jdsn(a)novell.com> (2008-09-11 12:37:19) (reply to #12) No the requested feature will not be part of the successor of "online update setup". Maybe you want it to be. But IMHO this has nothing to do with anything that is called "online update *something*". This feature is about a general refresh of repositories - not just the update repo. Software repositories are handled in the "Software repositories" module. And thats the place where this feature is asking for enhancement. Just look at the linked bug (bnc#346966). It even has a mockup (yes, I added one as well, but just look at the original one). And this is now quite the same I already wrote in comment #8. #16: Jiří Suchomel <jsuchome(a)novell.com> (2008-09-11 12:44:53) (reply to #15) Ah, sorry. Looks like I have some other feature in mind while commenting this one. This one really is not online-update specific. + #17: Stanislav Visnovsky <visnov(a)novell.com> (2008-09-12 14:12:02) + PM-Priority for product openSUSE-11.1 downgraded from mandatory to + important: + Aurora ECO approved. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303517

1 0