July 2012 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 313842] auto sleep on login screen with kdm
by fate_noreply＠suse.de 13 Aug '12

13 Aug '12

Feature added by: Philippe Baril Lecavalier (p_barill) Feature #313842, revision 1 Title: auto sleep on login screen with kdm openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Philippe Baril Lecavalier (p_barill) Partner organization: openSUSE.org Description: Any multi-user machine is prone to spend a fair amount of time on the login screen. How come there are no power management settings for this situation? If a user leaves a computer unattended for a few minutes while logged in, it will go to sleep after some minutes. Not so if it stays on the login screen. In this case and with kdm, the user must manually "suspend to RAM", and know the difference between this and "suspend to disk". Besides, I observed that the procedure to initiate sleep on the kdm login screen is quite involved for someone with a low computer literacy: Click on menu > shutdown > hold suspend > select "suspend to RAM" Clicking on "suspend" defaults to hibernate (I think the default should be sleep, not hibernate). Personally, I don't mind. But it's involved enough that some people told me "I got to write that down". There are some ways to automatically logout users after some period of inactivity. This can be justified to avoid waste of network resources. Similarly, the idea of enabling "sleep after x minutes" on the login screen is to save power and avoid unnecessary wear. I do not dare annoy you with yet another default setting request, but a simple way to turn this on. This could be useful in a variety of environments, such as home computers and computer labs with low usage rates (and reduce cooling bills too!). Obviously I deduce little need for this on a single-user machine. The only time I see the login screen is when I boot. Thus my logoff=shutdown. This is primarily about kdm. This follows a discussion from the forum: http://forums.opensuse.org/english/get-technical-help-here/install-boot-log… -- openSUSE Feature: https://features.opensuse.org/313842

1 2

[New: openFATE 311132] Compile Mesa and x-server with --enable-glx-tls
by fate_noreply＠suse.de 13 Aug '12

13 Aug '12

Feature added by: Iaroslav Andrusiak (pontostroy) Feature #311132, revision 1 Title: Compile Mesa and x-server with --enable-glx-tls Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Iaroslav Andrusiak (pontostroy) Partner organization: openSUSE.org Description: Most famous Linux distributions are compile Mesa and x-server with --enable-glx-tls. -- openSUSE Feature: https://features.opensuse.org/311132

1 4

[New: openFATE 313038] Remove "tracker" from lxde
by fate_noreply＠suse.de 09 Aug '12

09 Aug '12

Feature added by: Lutz Thuns (lOtz1009) Feature #313038, revision 1 Title: Remove "tracker" from lxde openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Lutz Thuns (lotz1009) Partner organization: openSUSE.org Description: As LXDE is intended to provide a LEIGHTWEIGHT desktop environment, unnecessary bloats like tracker should not be provided with it. Unfortunately the openSUSE pattern for LXDE contains Brasero, which automatically brings tracker as a dependency. Business case (Partner benefit): openSUSE.org: We want to keep a L ightweight- X - D esktop- E nvironment LIGHTWEIGHT. -- openSUSE Feature: https://features.opensuse.org/313038

1 3

[New: openFATE 311028] Add "Enable/disable numlock at startup" option to installer and YaST
by fate_noreply＠suse.de 04 Aug '12

04 Aug '12

Feature added by: Pieter De Decker (pdedecker) Feature #311028, revision 1 Title: Add "Enable/disable numlock at startup" option to installer and YaST openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Pieter De Decker (pdedecker) Partner organization: openSUSE.org Description: Related thread: https://features.opensuse.org/310152 Some people who don't have a QWERTY layout can't use the numbers on the top of the keyboard. I'm an AZERTY user (http://en.wikipedia.org/wiki/File:Belgian_pc_keyboard.svg) so I have to hold Shift to use the numbers on top of the keyboard. Therefore I usually prefer using the numpad, but that isn't possible if the numlock is switched off. Auto-enabling numlock at startup would be a huge time-saver. Some people on the other hand prefer having numlock switched off. Quoting Ned Ulbricht: "Enabling NumLock at boot would be very annoying on ThinkPads (and possibly other laptops) that overlay the numeric keypad on top of the alphabetic keys." I think the best way to resolve this little annoyance is to offer the user a choice during install as to what the default setting should be. Or even better: if it's possible to auto-detect which numlock setting is most desirable depending on the keyboard, the user doesn't even need to be presented this option. Additionally, I'd like to see this option added to the "System Keyboard Layout" applet in YaST. Business case (Partner benefit): openSUSE.org: This satisfies people who need to disable numlock for their keyboard to work properly and people who prefer using the numpad. -- openSUSE Feature: https://features.opensuse.org/311028

1 3

[openFATE 307254] Use POSIX capabilities instead of suid
by fate_noreply＠suse.de 04 Aug '12

04 Aug '12

Feature added by: Pascal Bleser (pbleser) Feature #307254, revision 1 Title: Use POSIX capabilities instead of suid openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Pascal Bleser (pbleser) Description: Use POSIX file capabilities instead of suid processes and running e.g. Apache as root: * http://www.nuxified.org/blog/dear-distributors (http://www.nuxified.org/blog/dear-distributors) * http://www.friedhoff.org/posixfilecaps.html (http://www.friedhoff.org/posixfilecaps.html) * https://www.redhat.com/archives/fedora-devel-list/2009-July/msg01568.html (https://www.redhat.com/archives/fedora-devel-list/2009-July/msg01568.html) -- openSUSE Feature: https://features.opensuse.org/307254

1 23

[New: openFATE 313475] opensuse 12.2 - is it time to replace kopete with telepathy?
by fate_noreply＠suse.de 02 Aug '12

02 Aug '12

Feature added by: jimbo bigcreed (Dimble_ThriceFoon) Feature #313475, revision 1 Title: opensuse 12.2 - is it time to replace kopete with telepathy? Package Wishlist: Unconfirmed Priority Requester: Important Requested by: jimbo bigcreed (dimble_thricefoon) Partner organization: openSUSE.org Description: it hasn't been considered ready for previous releases, but in the time since 12.1 released v0.3 of telepathy arrived to generally positive reaction, and after a minor bug-fix we can expect v0.4 to release on June 1st: http://mail.kde.org/pipermail/kde-telepathy/2012-May/006268.html -- openSUSE Feature: https://features.opensuse.org/313475

1 8

[New: openFATE 311068] Akmod Equivalent for openSUSE
by fate_noreply＠suse.de 02 Aug '12

02 Aug '12

Feature added by: Luke Wolf (LukeWolf) Feature #311068, revision 1 Title: Akmod Equivalent for openSUSE openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Luke Wolf (lukewolf) Partner organization: openSUSE.org Description: Tumbleweed related as opposed to 11.4 related Fedora has this really nice tool called Akmod or Automatic Kernel Module, which builds kmods on boot when you load into a new kernel that doesn't have kmods or to use the openSUSE term kmps. As we now have a rolling release in openSUSE: Tumbleweed this kind of functionality is more important than ever. Unless there are plans for rebuilding the kmps for Tumbleweed each time there is a new kernel. Which doesn't seem to be the case with the Nvidia kmp only supporting up to 2.6.34 series. Use Case: A user wants to run the rolling release version as opposed to the version based version because it better suits his needs to not have to reinstall every 8 months, This user updates to all the latest packages in Tumbleweed but unfortunately the latest kmp is for the last version release and so the user is forced to fall back to either the open source drivers which as of yet are not up to the user's needs, or fall back to the older kernel. an Akmod equivalent would fix this problem Business case (Partner benefit): openSUSE.org: Because we have a rolling release now and this rolling release has new kernels but there aren't for instance new Nvidia kmps to support it but an akmp or whatever you want to call it would fix that -- openSUSE Feature: https://features.opensuse.org/311068

1 3

[openFATE 309448] Clean temporary data in SUSE
by fate_noreply＠suse.de 30 Jul '12

30 Jul '12

Feature changed by: Peter Gumbrell (gumb) Feature #309448, revision 41 Title: Clean temporary data in SUSE openSUSE Distribution: New Priority Requester: Important Requested by: Michal Vyskocil (mvyskocil) Partner organization: openSUSE.org Description: The current default behavior of SUSE is not touch files in /tmp and others to prevent an unwanted data lost. There are at least two requests willing to change it somehow: * FATE#307510: Cron: set MAX_DAYS_IN_TMP different from 0 * bug#594778 - RN: include tmpwatch in a pattern The pros: * The common meaining of /tmp is that is for temporary data. FHS says - "Programs must not assume that any files or directories in /tmp are preserved between invocations of the program". FHS also allows the removal of a content of /var/tmp and /var/cache , even if those directories should be more persistent as /tmp . * As SUSE places the /tmp and /var on root partition by default and not remove the content of it, the free space should be simply eaten. There are a lot of applications in SUSE distribution that stores a lot of data inside those dirs, but because of the common meaning - they not removed them. For instance - Mozilla Firefox, ssh, gpg, kde, mc, Adobe Flash, and many others. The other way is to fix all of those programs to safely remove all content they store in /tmp after it's not needed. The cons: * Strictly speaking the not removal of /tmp and others is not againts FHS. * Change of the default is dangerous, especially if we are talking about files removal, because long time SUSE users might rely on this specific behavior of SUSE. * The default should be SAFE and not removing of files is considered as a safe default. Please note this FATE is not about concrete technical solution (existing scron script, tmwatch, tmpfs, /dev/shm, or something else). The question is - change the default behavior to remove temporary files, or not ? And if so, which ones and how often. Discussion: #1: Per Jessen (pjessen) (2010-05-04 11:31:51) I'm not really sure how this differs from feature 307510, but never mind - the only advantage of this change is to save disk space. Disk space is becoming cheaper by the minute and Terabyte is no longer an exotic amount reserved for large datacentres. I say we keep the safe default in openSUSE, and leave it to the sysadmin to do the one-line change if he or she wants to automatically purge temporary files. #3: Michal Vyskocil (mvyskocil) (2010-05-04 12:00:54) (reply to #1) The biggest reason is that this FATE does not recommend the technical solution. You're not right, the advantage is to prevent the filling of the disc on a running system. Your argument about cheaper disc space is true only if you consider new and new hardware. The existing one has typically fixed amount of disc space, should not be wasted by having a lot of unwanted data in /tmp . For instance my five year old laptop has 40GB HDD and 7GB root partition, so it is very sensitive on available space - not all SUSE are in datacenters :-). #5: Per Jessen (pjessen) (2010-05-05 13:25:22) (reply to #3) So for five years you have (presumably) managed quite well without this default setting. My argument about cheaper disk space has held true since around 2000 when disk sizes started doubling about once a year due to GMR. Not having temporary files purged was not an issue then, I see no reason why it is likely to become an issue now or later (with disk sizes continuing to grow). Neither openSUSE nor SuSE Linux have ever done such an automatic purge by default, so I maintain it is not a safe change as people may well have gotten used to keeping non- temporary data in /tmp. Given the minimal advantage, the risk of deleting non-temporary data and that changing the retention time is a matter of five seconds with vi, this is really not much of a feature. IMHO. #2: Guido Berhörster (gberh) (2010-05-04 11:41:11) Cleaning /tmp on bootup and/or periodically through a cronjob is also common practice on all other major Linux distros (e.g. Debian, Ubuntu, RHEL/Fedora, Mandriva) and UNIX(-like) OS (e.g. Solaris/Opensolaris, OpenBSD). I'd also really like to hear any use cases and reasons why users would put any valuable data in /tmp (rather than /var/tmp or their homedir) and expect it to persist indefinitely. #4: Gerald Pfeifer (geraldpfeifer) (2010-05-04 13:25:25) It's not necessarily (just) about disk size, there is also the aspect of partitioning and /tmp may not be all that large. It's also not primarily about data centers (which is not the key focus of openSUSE), but more individual users or wide spread use not necessarily governed by professional admins, and there this just reduces risk assuming we go for a somewhat conservative default (not just 24 hours). The use case is my significant other's machine (or mine), not some data center. For what it's worth, I, for one, don't want to keep all the crap that tends to pile up under /tmp for years. And non-expert users, of which we have many, will be surprised what kind of staff remains under /tmp, leaving behind a trail many won't be aware of, remaining even after months or years. #6: Per Jessen (pjessen) (2010-05-05 13:35:35) (reply to #4) Well, the non-expert user is exactly who I am worried about and why I think this feature is unsafe The non-expert user won't be aware of how the professional sysadmins would like to run things, and might just (intentionally or not) store or have stored valuable data in /tmp. Oops. Besides, I disagree about the use case - my use case is my datacentre run by professional sysadmins. (who decided what the primary target audience for openSUSE is? I thought we were still aiming to be everything for everyone.) #7: Guido Berhörster (gberh) (2010-05-05 13:51:08) (reply to #6) The non-expert user will store his data in /home/non-expert where these neatly named folders Documents, Music, Pictures etc. are. But he will fill slowly fill up his 10G rootfs by opening lots of pdfs, mp3s, archives etc. from Firefox (which are put into /tmp and never get deleted) without being aware of it , let alone how to avoid this in the first place. #8: Per Jessen (pjessen) (2010-05-05 14:07:39) (reply to #7) I'm less concerned about the new non-expert user, more about the OLD ditto who had already been using e.g. /tmp for storing non-temp data. For him this would not be a safe change, even if it was bent in neon in the Changelog. (as for Firefox using /tmp - my FF3.6 doesn't seem to store anything there?) #9: Michal Vyskocil (mvyskocil) (2010-05-06 11:20:21) (reply to #8) > I'm less concerned about the new non-expert user, more about the OLD ditto who had already been using e.g. /tmp for storing non-temp data. Are there any serious reasons why those data needs to be stored in /tmp and should not be placed elsewhere in system? I'm sure that expert you mention is fully able to understand the meaning of /tmp and place his files to other safe location. Or at least disable this behavior. As I understood your arguments - there is a bug (or rather an uncommon behavior of SUSE, if you'd preffer it), but because some people rely on that, so it might be not fixed/changed. And sorry, but that's not seems to me as a right argumentation. #11: Per Jessen (pjessen) (2010-05-06 19:41:02) (reply to #9) No, there are no real reasons why data needs to be stored in /tmp (unless they are genuinely temporary). My arguments against this are: * it is unsafe. openSUSE/SuSE Linux has not been purging /tmp at least since 4.4.1 (my first SuSE Linux).Some innocent non-expert user might very well end up having valuable data purged. * the change is so easily made that it's difficult to imagine why we are even discussing it here. * the change brings no real world benefits. #14: Guido Berhörster (gberh) (2010-05-07 00:15:20) (reply to #11) >* it is unsafe. openSUSE/SuSE Linux has not been purging /tmp at least since 4.4.1 (my first SuSE Linux).Some innocent non-expert user might very well end up having valuable data purged. That really sounds a bit far fetched. tmp is short for temporary. tem·po·rary: lasting for a limited time (in this case 10 days) >* the change is so easily made that it's difficult to imagine why we are even discussing it here. Not to the innocent non-expert user who doesn't even know that this option exists, that it is not turned on by default, and why he actually wants it changed. >* the change brings no real world benefits. It has been pointed out that several times that it prevents filling up the root patition. And not everyone has a multi-terabyte rootfs, IIRC by default the installer creates a relatively small rootfs and assigns the rest of the available space to a partition which gets mounted on /home. In effect the default setting is more likely to cause harm which is why it should be changed and why e.g. FATE#307510 was requested in the first place. #15: Per Jessen (pjessen) (2010-05-07 10:46:09) (reply to #14) Last entry on my part - in my opinion, it is not a safe change and it brings little or no real-life benefits. The default setting has caused little or no harm in the last 15 years, and it is difficult to imagine why it should become more likely to cause harm in the future. #10: Ricardo Gabriel Berlasso (rgbsuse) (2010-05-06 14:23:55) Can, please, the people who are against this provide a clear user case in which retaining these files is desirable? I really can't imagine such scenario... In the 10+ years I'm using Linux I've never see anyone using /tmp as storage folder: in fact, most people I know simply ignore the content of /tmp and /var/tmp folders. Some time ago a friend of mine had a problem with a print job which went crazy: in a few seconds a log file of several GB was created without his knowledge and afterwards he had problems to log-in in his system because the disk was full: cleaning /var/tmp was the solution. #12: Per Jessen (pjessen) (2010-05-06 20:25:36) (reply to #10) Use case: Retaining files stored in /tmp in desirable when they meant to be kept. #13: Per Jessen (pjessen) (2010-05-06 21:00:10) (reply to #12) Use case: Retaining files stored in /tmp is desirable when they were meant to be kept. #16: Ricardo Gabriel Berlasso (rgbsuse) (2010-05-07 15:38:40) (reply to #13) My first reaction to your "answer" was a mixture of "are you kidding?" with a "Wait, what?", but I will try to maintain the conversation in the right track. After all, we are here exchanging ideas. Articulated and complete ideas. Files that enters automatically in the tmp folder have no value per se in the long run (youtube videos, partial downloads, temporary image files... in /var/tmp you can also find log files which only show interesting information when something goes wrong, temporary information from kde sessions...). Some of those files are erased by the app that generated them, but some not, specially when the app crash. And as I pointed before, useless and big log files are really common, specially when there is a crash. Log files are useful only immediately after a crash, and if you set a reasonably default you will not lost them. Point is: If there is some valuable information there that needs to be kept forever it is because the user puts it on purpose ... and I cannot imagine why someone should put valuable information on a temporary directory on purpose... So, again, why we should need to keep those directories without maintenance? Or if you prefers, why there could be on those directories files meant to be kept? And which are those important files? #18: Robert Davies (robopensuse) (2010-12-19 18:53:49) (reply to #12) As per FHS, I have used files in /tmp for the Use case, that I did not care about them, and wanted them automatically deleted. /tmp is expected to be a local filesystem with fast access, and not expected to be accessible from other hosts in network or backed up. The user Home Directory or administrator project data directories, are the sane locations for "retaining files". As /tmp is a special case and well documented, the automatic purging of temporary files, which are not wanted for retention, should as a "Use Case" over turn a poorly chosen historical default in SuSE Linux. #17: Sascha Peilicke (saschpe) (2010-05-28 16:33:05) Another pro here is performance, when /tmp is kept in RAM via tmpfs, access is blazingly fast (good for large compile jobs, etc.). One issue might be a lack of sufficient physical RAM, but if /tmp needs more than what is available swap is gonna be used anyways, so /tmp ends up on disc again and should have the same performance as before. Nonetheless on a netbook or a computer with only small physical RAM available, a tmpfs solution should avoid swapping. So a /tmp size limit might be necessary. #19: Robert Davies (robopensuse) (2010-12-19 19:08:49) (reply to #17) Non-temporary /tmp files, would be the ones most likely to end up as disk pages, freed from RAM. True temporary files, probably won't (with ext3 & ext4 anyway) actually be saved onto disk before being deleted. Actually with small RAM, you WANT pages evicted (contrary to received wisdom), all the little used pages, are better in swap partition. The draw back using TMPFS is the pressure it puts the Linux VM under, and file size limits don't work as well as they used to with huge media flash files (FLV) getting saved there. I switched back to using a disk filesystem for /tmp, which makes purging MORE (not less) important, because re-boots don't automatically clean it up. #20: Satoru Matsumoto (heliosreds) (2010-12-20 09:36:52) Since 11.3 has been already released, I've changed the product from 11.3 to distribution. Please continue further discussions. #21: Malvern Star (solaris444) (2011-01-18 07:40:22) The default partition-based layout for SuSE restricts the root partition to only 20GB and uses the rest for /home (excluding swap). I have had most customers' systems become unable to reach runlevel 5 at one time or another due to their root partition being full. On new installs, I now do not allow a separate home partition to be created during install for this very reason. Plus, we still should not be too assured that lots of disk space will always be available. Some programs create temporary files of size 4GB or more. This would quickly fill /tmp if in constant use. This really should be changed to support the FHS recommendation. #24: Robert Davies (robopensuse) (2011-06-28 14:50:02) (reply to #21) Why don't you just turn on the clean up yourself, it's couple of variables in 'cron' section of sysconfig. Depriving your customers of upgrade advantages of a seperate /home, seems a drastic choice, when /tmp can be cleaned by changing '0' to '7' in 1 textfile! #22: J. Daniel Schmidt (jdsn) (2011-02-04 12:46:27) Withing one week I had two different openSUSE 11.3 machines preventing me from logging in because GBs of garbage in /tmp filled up / to 100%. This definitely needs some kind of automatic cleanup, at least in 11.4. #23: Per Jessen (pjessen) (2011-02-04 14:14:19) (reply to #22) Sounds like bug, did you report this in bugzilla? It sounds a lot like bug 633106. #25: Robert Davies (robopensuse) (2011-06-28 15:03:14) Does an "alternative" default package satisfy everyone, as sanity & reason to respect FHS is not rapidly prevailing? cron_config_SuSE_legacy - "SuSE Legacy - Eventually Fill /tmp; select to increase Support costs" cron_config_FHS_clean_tmp - "FHS - Automatic /tmp Cleanup, like real traditional UNIX" At least then selection of alternative is a simple package selection choice. #26: Philippe Baril Lecavalier (p_barill) (2012-07-30 03:10:04) A default which would purge /tmp upon each restart? As long as there's a nice way to turn that off, it should make everyone happy. I don't know of any simple one-click trick to purge the system of it's temp stuff. /var/log and /var/tmp can have some build up too. If you really insist to clean /tmp upon boot, you can always add this line to your /etc/fstab as I did some time ago: tmpfs /var/tmp tmpfs defaults,noatime,mode=1777 0 0 Not a sexy solution to the layman (to me it is!!). My friend, new to Linux, replied boldly "this is nuts!". + #27: Peter Gumbrell (gumb) (2012-07-30 13:22:02) + I've run into the problem of the temp directories filling up the root + partition on older machines with smaller hard drives. I've tried to fix + it by setting the retention time of /tmp to 30 days and added /var/tmp + with a setting of 90 days to sysconfig via YaST. However, these + settings don't always seem to be obeyed. + On my previous 11.x installations the settings seemed to be ignored + completely, whilst on a fresh 12.1 install I can see that although the + directories are relatively clean size-wise, there are many small files + well over those 30- or 90-day limits. I've also sometimes resorted to + flushing the temp directories on boot via the sysconfig setting but + this still leaves many old files untouched. -- openSUSE Feature: https://features.opensuse.org/309448

1 0

[openFATE 313536] Get rid of SuSEconfig.fonts
by fate_noreply＠suse.de 30 Jul '12

30 Jul '12

Feature changed by: Petr Gajdos (pgajdos) Feature #313536, revision 16 Title: Get rid of SuSEconfig.fonts openSUSE Distribution: Implementation Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: There is no point to run that code after installation of every package (and it's not run when you use zypper or 3rd party tools anyways). That code should be only run as a part of post-install of the fonts packages as only those are affected. Relations: - Remove SuSEconfig (feature/id: 100011) Discussion: #1: Petr Gajdos (pgajdos) (2012-07-03 17:13:23) Added "fontpackage" package to the M17N:fonts. fontpackage is intended to common runtime deps of every font package (e. g. /usr/share/fonts/truetype) and fontpackage-devel for buildtime dependency of every font package. fontpackage-devel contains only one file for now, which installs on /etc/rpm/macros.fonts-config. For details see osc cat M17N:fonts fontpackage rpm-macros.fonts-config Example of modified font package is M17N:fonts/xano-mincho-fonts. Could you please express your opinion on this plan? #2: Petr Gajdos (pgajdos) (2012-07-04 09:39:25) (reply to #1) After rethinking I've choosen fontpackages-runtime and fontpackages- devel. #3: Thorsten Kukuk (kukuk) (2012-07-06 14:37:38) I'm not a fonts expert, but looks good to me, beside one thing I don't really like: fontpackages-runtime contains only one directory. I think we should drop that package and package the directory inside of the RPMs which contains fonts. This has the big advantage, that RPM will take care of the directory itself, if the last package using it is removed. Or the directory should be added to filesystem directory, which includes already the parent directory. #4: Petr Gajdos (pgajdos) (2012-07-10 21:32:54) Ok, submitted fontpackages package into factory. sr#127540. #5: Petr Gajdos (pgajdos) (2012-07-11 13:47:20) As far as I can tell, M17N:fonts are ready for removing SUSEconfig. fonts. There are few packages using %run_suseconfig_fonts macro: 844- ksc-pcf (forgotten font package to be moved to M17N:fonts) daps fonts- config plotutils susedoc texlive-bin tv-fonts (package maybe to be moved to M17N:fonts) x3270 xmahjong xorg-x11-fonts xterm Also ghostcript-fonts package is subject to change in this regard (% run_suseconfig -m fonts). Unfortunately I can do anything until fontpackages package is in factory, so this process is blocked by license issue of our own code :- / (see declined sr#127540). Maybe we could consider to accept package as is for now and change license later (of course Novell replaced by SUSE LINUX Products GmbH, Nuernberg, Germany or something like that). + #6: Petr Gajdos (pgajdos) (2012-07-30 09:22:45) + https://bugzilla.novell.com/show_bug.cgi?id=772595 -- openSUSE Feature: https://features.opensuse.org/313536

1 0

[New: openFATE 313287] Allow printer add and modification to users
by fate_noreply＠suse.de 30 Jul '12

30 Jul '12

Feature added by: Lars Müller (lmuelle) Feature #313287, revision 1 Title: Allow printer add and modification to users openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Lars Müller (lmuelle) Partner organization: openSUSE.org Description: This had been part of the discussion in this thread http://lists.openSUSE.org/opensuse/2012-02/msg01443.html At the moment you need to be root to add a printer. It would be of huge benefit to corporate, soho, and home users if there is an easy way from inside YaST or while the initial install to allow a non root user to add a printer. -- openSUSE Feature: https://features.opensuse.org/313287

1 9