April 2014 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] acpid requires systemd?
by Felix Miata 25 Apr '24

25 Apr '24

Can this be true? If so, why? Zypper won't let me upgrade acpid without breakage unless systemd is installed too. I have systemd locked out, as I'd rather test things I can understand in Factory, not major overhaul stuff. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

Re: [opensuse-factory] repository priorities with Tumbleweed
by Thomas Langkamp 16 Jul '15

16 Jul '15

> No, please don't confuse people, if you add more repos than just > Tumbleweed you really had better know what you are doing or bad things > can, and will, happen :) I understand. I just would like to add the following to http://en.opensuse.org/Portal:Tumbleweed - between ## is the new stuff: "The only supported method of repo use for Tumbleweed is to have only the main repos (Oss, Non-oss, and Update) and the Tumbleweed repo active. ## If you use more repositorys you have to know how repo-priorities work, but even then Tumblweed does NOT support this ## " It would also be good to move this information to "Special concerns" and to move the whole "Special concerns"-section up. For example "Special Concerns Virtual Machines ... Third Party Drivers ... ## Non-Standard Repos: Only use Oss, Non-oss, and Update combined with the Tumbleweed-Standard repo. Everything else is not supported and might break the system ## " >You do know the legal reasons behind why packman is there, right? Yes. Then I do not whish you personaly to support Packman with TW - I understand now that this is not possible from your perspectivg. But...as the OS community discusses right now if/how to strengthen Tumbleweed... one way would be, that Packman+TW would be supported BY Packman. So I will ask the Packman-guys to do that... I hope this is possible for them. Without Packman Tumbleweed is so ... "anti-multimedia" ;) thanks anyway :D -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 18

[opensuse-factory] openSUSE:Factory:NonFree repository
by Kyrill Detinov 03 Jul '15

03 Jul '15

Hello. /factory/repo/non-oss/ isn't updated since September 23. -- WBR Kyrill

4 9

[opensuse-factory] Monospace font issue
by Kyrill Detinov 07 Apr '15

07 Apr '15

Hello. Recently updated my Factory running workstation (x86_64, Xfce). Monospace font interval is increased badly. I'm sure, I use DejaVu Sans Mono as a monospace font. I choose 'monospace 9' in programs settings. There is a screenshot: http://susepaste.org/view/simple/38919191 Changing to 'DejaVu Sans Mono 9': http://susepaste.org/view/simple/70371539 It looks like it was before. % fc-match Monospace Fontconfig warning: "/etc/fonts/conf.d/56-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. please move it to /home/kent/.config/fontconfig/fonts.conf manually Monospace: "Monospace" "Regular" -- WBR Kyrill

9 23

[opensuse-factory] Export broken for KinfoCenter
by Roger Luedecke 30 Jan '15

30 Jan '15

Export button is greyed out no matter what. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] systemd version 210 Heads Up
by Raymond Wooninck 22 Nov '14

22 Nov '14

Hi List Mates, Just a very early warning with regards to the latest released systemd version (version 210). In the release notes the following two items will have an effect on people that are utilizing laptops with a docking station and an external monitor. * logind is now a lot more aggressive when suspending the machine due to a closed laptop lid. Instead of acting only on the lid close action it will continuously watch the lid status and act on it. This is useful for laptops where the power button is on the outside of the chassis so that it can be reached without opening the lid (such as the Lenovo Yoga). On those machines logind will now immediately re-suspend the machine if the power button has been accidentally pressed while the laptop was suspended and in a backpack or similar. * logind will now watch SW_DOCK switches and inhibit reaction to the lid switch if it is pressed. This means that logind will not suspend the machine anymore if the lid is closed and the systemd is docked, if the laptop supports SW_DOCK notifications via the input layer. Note that ACPI docking stations do not generate this currently. Also note that this logic is usually not fully sufficient and Desktop Environments should take a lid switch inhibitor lock when an external display is connected, as systemd will not watch this on its own. The first item concerns a change that systemd is monitoring if the lid is closed or not. This monitoring starts already during the system boot process which would lead to the effect that the system is forced into suspend mode even before the login manager is reached. To prevent this, the second item was implemented, however as indicated current kernels (including the latest 3.14- rc4) do not support this yet for all laptops. The issue however is that the system will not reach the Desktop Environment yet as that this new principle already kicks in during the boot process. So implementing a lid switch inhibitor in GNOME/KDE/etc does not make any sense as that the system will never reach the desktop environment. I had a couple of email conversations with Lennart about this topic yesterday and finally with my last message he got the real issue that this happens during system boot and therefore systemd should handle this properly. He indicated that he will resolve the issue in one of the upcoming versions of systemd and also probably move the external monitor detection out of the DEs into logind. (The situation will then be that if the lid is closed and an external monitor is connected, then systemd will not suspend the system). If the decision is taken by the systemd maintainers, then in my opinion it would be good to revert the two commits in systemd version 210 that implement the two items mentioned so that the old lid switch behavior is restored. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

16 49

[opensuse-factory] Devel Project Virtualization: Not built against Tumbleweed?
by Johannes Kastl 15 Nov '14

15 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, while updating lxc to the latest version I came across one question: Is there any particular reason, why the virtualization-project (https://build.opensuse.org/project/show/Virtualization) is not built against/for tumbleweed? If not, could one of the maintainers please correct that? Regards, Johannes - -- You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, the Swiss hold the America's Cup, France is accusing the US of arrogance, and Germany doesn't want to go to war. (aus alt.jokes) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlMh+nYACgkQzi3gQ/xETbKLxwCfajUC5ZU1bCAghqGNY1u5eOyO GFsAn3njjuzTONetwWTIaNAdNVVA0gSP =RhDV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 13

[opensuse-factory] Tumbleweed: systemd cannot start privoxy
by Patrick Shanahan 30 Oct '14

30 Oct '14

up to date Tumbleweed (13.1) systemctl start privoxy 18:26 Crash: ~ # systemctl start privoxy Job for privoxy.service failed. See 'systemctl status privoxy.service' and 'journalctl -xn' for details. 18:27 Crash: ~ # systemctl status privoxy privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; disabled) Active: failed (Result: exit-code) since Wed 2013-11-20 18:27:09 EST; 15s ago Process: 9430 ExecStart=/usr/sbin/privoxy --pidfile /run/privoxy.pid --user privoxy /etc/privoxy/config (code=exited, status=1/FAILURE) Nov 20 18:27:08 Crash systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Nov 20 18:27:09 Crash systemd[1]: privoxy.service: control process exited, code=exited status=1 Nov 20 18:27:09 Crash systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. Nov 20 18:27:09 Crash systemd[1]: Unit privoxy.service entered failed state. 18:27 Crash: ~ # journalctl -xn -- Logs begin at Sat 2013-03-30 18:27:22 EDT, end at Wed 2013-11-20 -- 18:27:35 EST. -- Nov 20 18:27:08 Crash systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... -- Subject: Unit privoxy.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit privoxy.service has begun starting up. Nov 20 18:27:09 Crash systemd[1]: privoxy.service: control process exited, code=exited status=1 Nov 20 18:27:09 Crash systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. -- Subject: Unit privoxy.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: -- http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba4… -- -- Unit privoxy.service has failed. -- -- The result is failed. Nov 20 18:27:09 Crash systemd[1]: Unit privoxy.service entered failed state. Nov 20 18:27:15 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=282 TOS=0x00 PREC=0x00 TTL=64 ID=51684 DF PROTO=UDP SPT=631 DPT=631 LEN=262 Nov 20 18:27:15 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=282 TOS=0x00 PREC=0x00 TTL=64 ID=51685 DF PROTO=UDP SPT=631 DPT=631 LEN=262 Nov 20 18:27:34 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=247 TOS=0x00 PREC=0x00 TTL=64 ID=51686 DF PROTO=UDP SPT=631 DPT=631 LEN=227 Nov 20 18:27:34 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=247 TOS=0x00 PREC=0x00 TTL=64 ID=51687 DF PROTO=UDP SPT=631 DPT=631 LEN=227 Nov 20 18:27:35 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=263 TOS=0x00 PREC=0x00 TTL=64 ID=51688 DF PROTO=UDP SPT=631 DPT=631 LEN=243 Nov 20 18:27:35 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=263 TOS=0x00 PREC=0x00 TTL=64 ID=51689 DF PROTO=UDP SPT=631 DPT=631 LEN=243 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 20

[opensuse-factory] New Package - libhal1-flash (re-enabling Flash-Player DRM content on Linux)
by Christopher Horler 13 Sep '14

13 Sep '14

Good afternoon! I've written and packaged a compatibility library for flash to enable playback of DRM content (this removes the dependency on the HAL package). I'd like to know what steps I can take to have the package considered for inclusion in openSUSE 12.3 and 13.1. Can I submit the package to devel:openSUSE:Factory, or is there another action I should be taking? Details of the bug and links to upstream are here (please briefly review): https://bugzilla.novell.com/show_bug.cgi?id=768562#c19 OBS location: https://build.opensuse.org/package/show?package=hal-flash&project=home%3Ach… I will maintain the package until such time that HTML5 Video content is a viable alternative or the Flash plugin is completely withdrawn. RPMs, debs... are all available on the build service. Three noteworthy points: - package naming (libhal1-flash) doesn't 100% align with the Shared Library Policy (I've suffixed -flash to make clear this is not a fully functional HAL layer and also to avoid naming conflicts as some distros seem to have a shared library package already named libhal1). - The packages depends on dbus and udisks. It seems to work find when udisks is launched on demand (as for openSUSE 12.3) - The flash-player package could have some kind of RPM dependency on this package to assist the user when looking in YaST (Install / Remove Software) / Package Manager. Chris -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] source_validator error: signature does not validate
by Kyrill Detinov 25 Aug '14

25 Aug '14

Hello. I can't build a package. Service source_validator failed. % osc build Run source service: /usr/lib/obs/service/format_spec_file --outdir /tmp/tmpVbBhay Run source service: /usr/lib/obs/service/source_validator --outdir /tmp/tmpIQYU6i /home/kent/rpmbuild/projects/M17N/i18nspector/i18nspector.keyring gpg: enabled debug flags: memstat gpg: keyring `/tmp/check_if_valid_source_dir-NL8Ezs/.checkifvalidsourcedir-gpg-keyring' created gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 00000000 occurs more than once in the trustdb gpg: key 015475F5: public key "Jakub Wilk <jwilk(a)jwilk.net>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks gpg: enabled debug flags: memstat gpg: Signature made Mon Jun 24 22:36:51 2013 MSK using RSA key ID 015475F5 gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 00000000 occurs more than once in the trustdb gpg: Good signature from "Jakub Wilk <jwilk(a)jwilk.net>" gpg: aka "Jakub Wilk <jwilk(a)debian.org>" gpg: aka "Jakub Wilk <ubanus(a)users.sf.net>" random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks (E) signature /home/kent/rpmbuild/projects/M17N/i18nspector/i18nspector-0.11.1.tar.gz.asc does not validate Aborting: service call failed: /usr/lib/obs/service/source_validator --outdir /tmp/tmpIQYU6i Source service run failed! As far as I can see, the signature is good. This also happens with another package (graphics/icoutils). What is the problem? -- WBR Kyrill

2 5

[opensuse-factory] what happened to fbset?
by Felix Miata 04 Aug '14

04 Aug '14

in 11.4: # fbset -i mode "1152x864" geometry 1152 864 1152 864 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name : radeondrmfb Address : 0xd80c0000 Size : 3981312 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 1 YPanStep : 1 YWrapStep : 0 LineLength : 4608 Accelerator : No In 13.1B1: # fbset -l if 'fbset' is not a typo, You can use... # zypper se -s fbset ... No packages found. # command-not-found fbset fbset: command not found -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 18

[opensuse-factory] OSEP: openSUSE Distribution Daemon User and Group Names
by Guido Berhoerster 29 Jul '14

29 Jul '14

Hello, after initial discussion on the -packaging list (see http://lists.opensuse.org/opensuse-packaging/2014-02/msg00136.html) and incorporating some of the feedback we would like to introduce the attached openSUSE Enhancement Proposal about creating a safe namspace of system user and group names. Further comments and reviews would be appreciated. Full text of the OSEP (currently maintained at https://github.com/lnussel/osep_opensuse_usernames/blob/master/opensuse_use…): _____________________________________________________________________ OSEP: XXXX Title: Informational proposal: openSUSE Distribution Daemon User and Group Names Version: 0.1 Last-Modified: 03 Mar 2014 Author: Guido Berhoerster <gber(a)opensuse.org>, Ludwig Nussel <ludwig.nussel(a)suse.de> Status: Draft Type: Informational Created: 28 Feb 2014 Post-History: _____________________________________________________________________ Abstract -------- This OSEP proposes a defined pattern for unprivileged system user and group names. Specification ------------- Packages that add unprivileged users to e.g. run daemons as need to use names that follow the following regular expression: ^_[0-9a-z][0-9a-z_]*$ This policy is meant to be applied to all packages that are new to openSUSE Factory. Existing packages are encouraged to switch to the new policy. An exception are legacy users with a static uid as created on first installation by aaa_base, like e.g. 'root' or 'nobody'. Motivation ---------- Many packages need to add user and group names for their unprivileged daemons. Currently openSUSE Factory has a known lists of more than 130<<A>> such daemon user names. Many names are short for convenience, e.g. 'pop', 'vdr', 'tor' or 'znc'. Since there is no separate name space for system users those names may collide with names of real persons. A common pattern for user names on unix systems also is to combine letters of the given names and the surname which may lead to combinations that may also collide with system user names. Sharing a user name between a system user and a normal user leads to surprising or even security relevant misbehavior as the daemon user may write to files in the real user's home or vice versa. Since introducing a separate namespace is not possible in the current name service model, separating system users and real users must be done by naming them differently. Rationale --------- A special prefix or suffix to user names is a straight forward solution to the same namespace problem. Since long user names may not fully be displayed by e.g. the ps tool the chosen method needs to be short. Therefore using a single letter character may be used. According to the recommended regular expression for usernames in the useradd manpage<<D>> of the shadow package, dollar could be used as suffix or underscore as prefix or suffix. OpenBSD already implemented a policy to use underscore (ASCII character 95) as prefix in 2003<<C>>. This method is therefore considered proven in practice. For symmetry reasons and because many packages also create groups with the same name as the user the same solution should be applied to groups as well. License ------- This document has been placed in the public domain. References ---------- [bibliography] - [[[A]]] current list of known user names in opensuse is maintained in link:https://build.opensuse.org/package/view_file/openSUSE:Factory/rpmlint/… - [[[B]]] link:http://anonscm.debian.org/viewvc/pkg-shadow/upstream/trunk/man/useradd… manpage] - [[[C]]] List of sytem users in link:http://www.openbsd.org/cgi-bin/cvsweb/\~checkout~/ports/infrastructure… with short sentence expressing the "policy" - [[[D]]] some link:http://lists.opensuse.org/opensuse-packaging/2014-02/msg00103.html[num… collected by Guido -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

20 64

[opensuse-factory] new package: Scilab
by Dmitry Roshchin 13 Jun '14

13 Jun '14

Scilab is an open source, cross-platform numerical computational package and a high-level, numerically oriented programming language. It can be used for signal processing, statistical analysis, image enhancement, fluid dynamics simulations, numerical optimization, and modeling, simulation of explicit and implicit dynamical systems and (if the corresponding toolbox is installed) symbolic manipulations. http://www.scilab.org/ Scilab in Science repository: https://build.opensuse.org/package/show/science/scilab Steps: - moving scilab-related java packages from Science to Java:packages repository - submitting this packages to Factory - submitting scilab to Factory -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] kswapd0 maxing CPU, kernel 3.14
by Tom Hardy 28 May '14

28 May '14

Using a laptop, AMD 64 dual core, 3.5 GiB available memory, typically 1.5 to 2.5 in use with no or low swap usage (2 GiB available), running KDE with multiple applications open. I am following Tumbleweed with multiversion kernel. Currently have kernel- desktop (X86_64) 3.11.10-7.1, 3.14.0-23.6.gfa168d7, and 3.14.1-24.1.geafcebd I've noticed with the 3.14 kernels and a late 3.13 one, with the above usage, that kswapd0 pegs a CPU for extended periods, as reported by KSysGuard. Actual swap usage doesn't change. Logging out of KDE and using a terminal with top has no problems. Kernel 3.11.10 has no problems. This appears to be in the form of a bug report. Did I find the right forum? -- Tom Hardy <rhardy702(a)gmail.com> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] libav and multimedia idea
by Tomáš Chvátal 14 May '14

14 May '14

Hello guys, I have created proof of concept libav library with disabled patented codecs in my home project [1]. This means that this library si up par with what we have in chromium and it should be legal to distribute. Apart from the library the repo contains vlc chromium and xbmc (built localy fails on obs, meh) which seems to run fine, just not to play almost anything ^_^. The possibility here is to include all the media players and stuff around it into openSUSE release, where one has to flip the switch in libav (see the spec file) and can build full-fledged-european-edition which can play our sweet movies. Let me know what you think about this plan and what would you use as base devel project for this. Cheers Tom [1] https://build.opensuse.org/project/show?project=home%3Ascarabeus_iv

8 11

[opensuse-factory] devel:languages:misc, please cleanup build config
by Ruediger Meier 30 Apr '14

30 Apr '14

Hi, could sombody with the right permissions please cleanup the build config in devel:languages:misc There are many archs wrongly enabled for certain repos. For example for openSUSE 13.1 it should be something like this <repository name="openSUSE_13.1"> <path project="openSUSE:13.1" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> </repository> <repository name="openSUSE_13.1_ports"> <path project="openSUSE:13.1" repository="ports"/> <arch>aarch64</arch> <arch>armv6l</arch> <arch>armv7l</arch> <arch>ppc</arch> <arch>ppc64</arch> </repository> thanks, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] GNOME appdata broken during zypper dup
by Olaf Hering 30 Apr '14

30 Apr '14

Since a few weeks I get dependency errors like shown below. I'm sure they are self-healing. My question: what needs to be done to make them disappear with an upcoming 'zypper dup'? Up to now I used 'Solution 1'. ... Computing distribution upgrade... Force resolution: No Computing upgrade... 11 Problems: Problem: nothing provides appdata(gnect.appdata.xml) needed by application:Four-in-a-Row-.noarch Problem: nothing provides appdata(gnomine.appdata.xml) needed by application:GNOME Mines-.noarch Problem: nothing provides appdata(glines.appdata.xml) needed by application:Five or More-.noarch Problem: nothing provides appdata(gnobots2.appdata.xml) needed by application:GNOME Robots-.noarch Problem: nothing provides appdata(gcalctool.appdata.xml) needed by application:Calculator-.noarch Problem: nothing provides appdata(gnibbles.appdata.xml) needed by application:GNOME Nibbles-.noarch Problem: nothing provides appdata(mahjongg.appdata.xml) needed by application:GNOME Mahjongg-.noarch Problem: nothing provides appdata(gnotski.appdata.xml) needed by application:GNOME Klotski-.noarch Problem: nothing provides appdata(gtali.appdata.xml) needed by application:Tali-.noarch Problem: nothing provides appdata(glchess.appdata.xml) needed by application:GNOME Chess-.noarch Problem: systemd-210-6.1.x86_64 conflicts with sysvinit provided by sysvinit-2.88+-94.2.x86_64 Problem: nothing provides appdata(gnect.appdata.xml) needed by application:Four-in-a-Row-.noarch Solution 1: keep obsolete application:Four-in-a-Row-.noarch Solution 2: break application:Four-in-a-Row-.noarch by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): 1 zypper lr -d: # | Alias | Name | Enabled | Refresh | Priority | Type | URI --+---------------------------+---------------------------+---------+---------+----------+--------+------------------------------------------------------------------------------------ 1 | factory | factory | Yes | Yes | 66 | yast2 | http://download.opensuse.org/factory/repo/oss/ 2 | factory-debug | factory-debug | Yes | Yes | 66 | yast2 | http://download.opensuse.org/factory/repo/debug/ 3 | factory-non-oss | factory-non-oss | Yes | Yes | 66 | yast2 | http://download.opensuse.org/factory/repo/non-oss/ 4 | obs-network_wicked_master | obs-network_wicked_master | Yes | Yes | 66 | rpm-md | http://download.opensuse.org/repositories/network:/wicked:/master/openSUSE_… 5 | remote-packman-essentials | remote-packman-essentials | Yes | Yes | 66 | rpm-md | http://packman.inode.at/suse/Factory/Essentials Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Help needed with console issue
by Stephan Kulow 29 Apr '14

29 Apr '14

Hi, openQA sees a big issue in minimal installations - having no correct console setup. I reported it as https://bugzilla.novell.com/show_bug.cgi?id=875666 and Werner assumes it's something related to plymouth. It would be great if someone took over continueing to debug this. As the "kickoff 13.2 release team in Dubrovnik" plan kind of failed, I'll try to just send bug reports this way and we'll see how far it works out. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Updates to KDE:Current
by Raymond Wooninck 28 Apr '14

28 Apr '14

In the next hour a new update for KDE:Current will be published. This update contains the following: * kdebase4-workspace 4.11.9 with the latest bugfixes for plasma. * Baloo was aligned with the latest upstream patches for more stability with regards to the cleaner and Xapian connectivity. * Libxapian was build without SSE support for 32bit builds. It seems that quite a number of users are using systems that do not support these instruction sets and this causes crashes. This should now be fixed. * KDEPIM was updated with the fixes that were created upstream for the bug report https://bugs.kde.org/show_bug.cgi?id=333640 with regards to the knotes migration. Now the old notes should become visible after the migration, which should automatically start if you update from KDE:Current after 2pm CET. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Infinality (or similar software) in openSUSE 13.2
by Alan B 27 Apr '14

27 Apr '14

Hello all, First time using a mailing list so forgive me for any problems. I was just wondering if there were any plans to include some improvements (although I guess this is subjective) to the default font rendering in 13.2 by using something like Infinality or similar software. Regards, Alan Bortu -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 16

[opensuse-factory] GNOME 3.12 now in openSUSE:Tumbleweed
by Greg KH 27 Apr '14

27 Apr '14

If anyone has any problems with it, please let me know. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Milou fast
by Roman Bysh 25 Apr '14

25 Apr '14

Wow, Milou is very very fast when find files! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] GNOME 3.12.0 for TW
by Dominique Leuenberger a.k.a. Dimstar 24 Apr '14

24 Apr '14

Hi all, and especially Greg, As you are surely aware, GNOME 3.12 has been released and all the work to include it in Factory has been prepared; we also released (so far without announcement.. ) a GNOME:STABLE:3.12 repository for openSUSE 13.1, so users can update (not advised for multi DE setups, as we have to replace upower). It would be nice if TW could as well start preparing for the inclusion of GNOME 3.12, in order to also have its users benefit from the work done. I suggest to use the packages maintained in GNOME:STABLE:3.12 for now (note: wayland is disabled there; we don't even have the right stack in Factory until a couple days ago..) Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 5

Re: [opensuse-factory] Asking for a new subproject
by Damian Ivanov 24 Apr '14

24 Apr '14

Now I saw the request and accepted it. FYI: I recently looked into indicators and talked to some unity developers (because I'm developing yet another desktop environment - yay! and wanted to use the indicators), most recent versions of the indicators depend on some retarded stuff like upstart (they are going to remove that dependency now again as Ubuntu is switching to the superior systemd though) 2014-04-24 19:48 GMT+02:00 denisart benjamin2 <p.drouand(a)gmail.com>: > Le 24/04/2014 19:25, Damian Ivanov a écrit : > >> Yes, obs was down the last hours. >> >> 2014-04-24 19:13 GMT+02:00 denisart benjamin2 <p.drouand(a)gmail.com>: >>> >>> Le 24/04/2014 15:58, Damian Ivanov a écrit : >>>> >>>> Weird, did you include me to the "Ayatana guys" ? I don't seem to have >>>> >>>> mail from you. BTW what for do you want to do with the indicators >>>> (for xfce or what?) >>>> >>>> 2014-04-24 13:29 GMT+02:00 denisart benjamin2 <p.drouand(a)gmail.com>: >>>>> >>>>> Hello, >>>>> >>>>> With another guy (i.e XRevan86), we wan't to maintain Ubuntu's >>>>> indicators >>>>> in >>>>> Gnome:Ayatana:Indicators but I have no answers from Ayatana guys so if >>>>> someone could help me... >>>>> >>>>> Regards. >>>>> Benjamin >>>>> -- >>>>> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org >>>>> To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org >>>>> >>> So do you agree to create Indicators subproject ? I won't be alone on it, >>> I'm mentoring a new guy and I think it would be a good point to start. >>> >>> Regards. >>> Benjamin > > Very good. Thanks you. > > Benjamin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] Asking for a new subproject
by Damian Ivanov 24 Apr '14

24 Apr '14

Yes, obs was down the last hours. 2014-04-24 19:13 GMT+02:00 denisart benjamin2 <p.drouand(a)gmail.com>: > Le 24/04/2014 15:58, Damian Ivanov a écrit : >> >> Weird, did you include me to the "Ayatana guys" ? I don't seem to have >> >> mail from you. BTW what for do you want to do with the indicators >> (for xfce or what?) >> >> 2014-04-24 13:29 GMT+02:00 denisart benjamin2 <p.drouand(a)gmail.com>: >>> >>> Hello, >>> >>> With another guy (i.e XRevan86), we wan't to maintain Ubuntu's indicators >>> in >>> Gnome:Ayatana:Indicators but I have no answers from Ayatana guys so if >>> someone could help me... >>> >>> Regards. >>> Benjamin >>> -- >>> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org >>> To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org >>> > So do you agree to create Indicators subproject ? I won't be alone on it, > I'm mentoring a new guy and I think it would be a good point to start. > > Regards. > Benjamin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Asking for a new subproject
by denisart benjamin2 24 Apr '14

24 Apr '14

Hello, With another guy (i.e XRevan86), we wan't to maintain Ubuntu's indicators in Gnome:Ayatana:Indicators but I have no answers from Ayatana guys so if someone could help me... Regards. Benjamin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Tumbleweed : wrong checksum
by ellanios82 22 Apr '14

22 Apr '14

Hello List, - in case of interest, i read : [Tumbleweed|http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/s…] Can't provide file './x86_64/kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm' from repository 'Tumbleweed' History: - kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm has wrong checksum Abort, retry, ignore? [a/r/i] (a): a ........................ regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] btrfs and samba acls
by lynn 22 Apr '14

22 Apr '14

Hi We're concerned about discussions where btrfs cannot lay down and retain samba induced acls e.g. https://lists.samba.org/archive/samba/2014-April/180747.html Will it be possible to mimic windows ntacls with btrfs as well as we currently do with ext4? ThanksL x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] BNC#874363 Dracut-037 Unbootable with LVM
by Shawn W Dunn 21 Apr '14

21 Apr '14

Right now, the -037 version of dracut that was pushed from Base:System is resulting in bootfailures on lvm installs. Would we prefer that I roll back to -036 until we can get some more testing done, or just let it ride while I(we) attempt to find a fix? Don't really have a solid timeframe on getting it fixed yet....

1 0

[opensuse-factory] GStreamer 1.0 status
by Wolfgang Rosenauer 21 Apr '14

21 Apr '14

Hi, since Firefox finally has official support for GStreamer 1.0 with version 30 (currently Aurora) I've been looking into switching to that. (my current system is 13.1 fwiw) While MP3 support works fine with Fluendo for GStreamer 1.0 I haven't found a way to enable H.264 at all. First it's not clear which plugins are needed at all. According to the developer it should be " gstreamer gstreamer-plugins-base gstreamer-plugins-good gstreamer-plugins-bad and either gstreamer-plugins-libav or some 3rd party h264 decoder (I believe Fluendo has one, but there are also others). " I've installed all of them but still does not work. So it might be that I need *-bad-orig-addon in addition but packman does not have the right versions and I'm not going to replace my full gstreamer infrastructure for that. Is the status better with Factory or is there still no usable way (for endusers w/o having to destroy their basesystem) to get H.264 support through GStreamer 1.0? Because then it makes no sense to switch Firefox to it yet. Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Probably Factory inconsistency
by Matwey V. Kornilov 17 Apr '14

17 Apr '14

Hi, When I build with openSUSE:Factory/snapshot erlang R16B is installed (current commited version in Factory is R16B03, version in 13.1 is R16B01). Why does the Factory stick on the one-year-old version, and how the version in the previous release (R16B01) is newer than in Factory snapshot (R16B)? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 7

[opensuse-factory] Bash 4.3 and readline libary 6.3 for testing
by Dr. Werner Fink 17 Apr '14

17 Apr '14

Hi, for those who are adventuresome may have a look at the package shells/bash43 as a replacement for the bash in Base:System/bash and its link shells/bash. There *are* changes, therefore I'd like to here some more reports and experiences before I replace the bash 4.3 and the corresponding readline libary 6.2. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

1 0

[opensuse-factory] Time to jettison the '2' in 'apache2' ?
by Nathan Cutler 17 Apr '14

17 Apr '14

Hi - It has been four years since Apache 1.3 went EOL. Is it time to get rid of the '2' in, e.g., 'apache2', 'httpd2', 'apache2ctl', etc.? The official docs at http://httpd.apache.org do not use it. Impact on users could be minimized by including symlinks from httpd2 -> httpd, etc. Nathan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 9

[opensuse-factory] [Tumbleweed] libkmod: conf_files_list: unsupported file mode /dev/null: 0x21b6
by Achim Gratz 16 Apr '14

16 Apr '14

I'm gettin reams of these messages whenever zypper creates new initrd. It looks like there's a patch for this problem available: http://www.spinics.net/lists/linux-modules/msg01240.html Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

Re: [opensuse-factory] Time to jettison the '2' in 'apache2' ?
by Nathan Cutler 16 Apr '14

16 Apr '14

> Nope, I am not changing this, unless you give me a damn good reason. it is just a distribution implementation detail and does not affect the functionality. The reason is to match upstream and minimize confusion for people who are trying to follow the upstream documentation. I agree that it does not affect functionality, as long as you exclude manpages from your definition of "functionality". I understand your reluctance to drop the '2' from the package name, even though we don't use the major version number in other packages that I am aware of and it gives people false hope that multiple versions of Apache can coexist on the same system. Personally I would be satisfied if you could at least include symlinks from the upstream binary/script names to the openSUSE-specific names. I.e. especially httpd -> httpd2 and apachectl -> apache2ctl. As for manpage functionality, I think it is seriously broken. Consider this, for example (with apache2 version 2.4.6-6.19.2): # httpd If 'httpd' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf httpd # man httpd ... read all about the httpd command that I can't run, no mention of httpd2 ... # apachectl If 'apachectl' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf apachectl # man apachectl ... read all about the apachectl command that I can't run, no mention of apache2ctl ... # man apachectl2 ... another way of displaying the apachectl manpage, but still no mention of apache2ctl... # apachectl2 If 'apachectl2' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf apachectl2 # man apache2ctl No manual entry for apache2ctl # man apxs ... read manpage ... # apxs If 'apxs' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf apxs # man apxs2 ... read apxs manpage ... # apxs2 If 'apxs2' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf apxs2 The manpages appear to be taken verbatim from upstream, with no mention of the openSUSE-specific name change. Also, there is a manpage for apachectl2, a command which doesn't exist, but none for apache2ctl, which does. And then there is a manpage for apxs which is not included in the package at all (under any name). Nathan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] [Yahoo!グループ]サービス終了のお知らせ（2014/4/15）
by Yahoo! Groups 15 Apr '14

15 Apr '14

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 　コミュニティサービス「Yahoo!グループ」（2014/4/15）パソコン版主要機能の停止・モバイル版サービス終了・過去メール提供の開始 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ※Yahoo!グループにメールアドレスをご登録いただいているすべてのお客様に送信しております。 ※このたびのお知らせはYahoo!メールなど、Yahoo! JAPANが提供するほかのサービスについての終了のお知らせではございません。いつもYahoo!グループをご利用くださいまして、誠にありがとうございます。先にお伝えいたしましたとおり、2014年5月28日（水）午後3時（予定）をもちまして、Yahoo!グループはサービスを終了いたします。サービス終了にあたり、2014年4月16日（水）午後3時より以下の対応を実施させていただきます。・パソコン版主要機能の停止・モバイル版サービス終了・過去メールダウンロード機能提供開始 ※グループの管理者は過去のメッセージのデータをブリーフケースに保存でき、　メンバーは管理者が保存したデータをダウンロードできる機能です。過去のメールダウンロード機能、保存可能なデータの詳細、ご質問への回答など、詳しくはこちらをご覧ください。 http://info.groups.yahoo.co.jp ※パソコン、スマートフォンでご覧ください。 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2014年5月28日（水）午後3時のサービス終了と同時に、Yahoo!グループへのアクセス、メールアドレスによる送受信、過去のご利用データの閲覧・ダウンロードなどは一切行うことができなくなります。サービス終了間際には、多くのお客様からのアクセスが集中することが予想されますため、余裕を持って、お早めにデータの保存を実施していただくことをお勧めします。 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━　【代替サービスのご紹介】 Yahoo!グループのようにグループコミュニケーションが可能なサービスをご紹介させていただきます。 ※ご利用方法などにつきましては、各サービスの提供元にお問い合わせください。 freeml（フリー・エムエル） http://www.freeml.com/service/yahoogroups/ らくらく連絡網 http://ra9.jp/docs/switch1 サイボウズLive http://page.cybozulive.com/yahoo-groups/ 恐れ入りますが、このメールアドレスはYahoo!グループからの送信専用のため、こちらのメールに返信をされましてもお問い合わせを受け付けることができません。 2004年2月のサービス開始より、10年の長きにわたり、多くのお客様のご利用いただきまして、誠にありがとうございました。サービス終了に伴い、皆様には多大なご迷惑をおかけいたしますことを深くおわび申し上げます。今後とも弊社サービスをご愛顧くださいますようお願いいたします。 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ □Yahoo!グループ： http://groups.yahoo.co.jp/ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1 0

[opensuse-factory] New package: Ceph
by David Disseldorp 14 Apr '14

14 Apr '14

Ceph is a distributed object store with support for a wide range of interfaces, including block-layer (rbd), filesystem (fuse, kernel), HTTP (REST), and client libraries. A full list of features is available via the project website: http://ceph.com/ The project is currently maintained upstream by a large collection of companies and individuals, and is carried by Debian and Fedora. The build service devel project has been present at filesystems:ceph for some time now. I'd like to submit it to openSUSE:Factory in the coming days, providing there are no objections from the community. This submission would not include the separately packaged quick-deployment utility ceph-deploy, which I'm not currently willing to maintain. Cheers, David -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Plymouth maintainer
by Mark van Tinteren 14 Apr '14

14 Apr '14

A while ago (more then a month) I announced that i would no longer be able to maintain Plymouth next to my current packages and development and did a call out for a new maintainer. So far no one has reacted or volunteered so with this i put it out there once again. Plymouth needs a maintainer if you are interested let me know. Mark -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] BTRFS and old 32-bit programs
by Lew Wolfgang 14 Apr '14

14 Apr '14

Hi Folks, I was bitten by the default XFS inode64 configuration again last week. To refresh memories, XFS now defaults to spreading its inodes out across the whole partition, which on partitions larger than 1-TB will break 32-bit applications. This time it was a FPGA compiler and acroread. XFS can be created/mounted so that all the inodes are clustered at the low end of the partition, but this can lead to other issues. I now wonder if BTRFS will have a similar issue with large filesystems? Will BTRFS treat old 32-bit programs well? About 30-minutes of searching on Google didn't answer the question. We're currently using partitions as large as 77-TB to store and process many thousands of 4-GB binary files. Regards, Lew -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] journald configuration defaults
by Achim Gratz 14 Apr '14

14 Apr '14

Some time ago I had a problem with slow boot. Once that was fixed I started to have the opposite problem, that is long delays with high disk activity during shutdown, getting much worse with time. Again this turns out to be triggered by journald: once the log file had grown past 20MiB or so there would be a noticeable delay when flushing the log to disk and it became unbearable at 80MiB. The time is superlinear with log size: a verify on the current 7MiB journal file takes roughly 1.5s (17s for a loop of 16 verifies), the 114MiB for the old file are already over 30s. The solution (for me) was to set SystemMaxFileSize=8M in /etc/systemd/journald.conf so that the active journal file gets rotated much earlier than with the built-in defaults. I have a rather small separate /var, but that file would have grown to about 300MiB. considering that most people probably have probably much larger /var partitions and the superlinear scaling characteristics, I think it would be advisable to provide more sensible defaults with the distribution. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 18

[opensuse-factory] low hanging fruit: packages with both init scripts and service files
by Ludwig Nussel 14 Apr '14

14 Apr '14

Hi, Scanning through Factory logs I see that rpmlint found the following packages that have both a systemd service file as well as an init script. Since the latter is useless in Factory as it's shadowed by the service file the init script can be removed resp not installed: apache2 atheme autofs avahi clamav collectd courier-authlib courier-imap dbus-1-x11 dovecot21 erlang glusterfs gnugk gnump3d greenbone-security-assistant icecast keepalived laptop-mode-tools memcached netatalk nut openslp openvas-administrator openvas-manager openvas-scanner pcsc-lite php5 postfix postgrey pptpd proftpd pure-ftpd rabbitmq-server radvd rsync sanlock spamassassin squid subversion ufw ulogd util-linux varnish xl2tpd cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 12

[opensuse-factory] VDR update in planning
by Stefan Seyfried 11 Apr '14

11 Apr '14

Hi all, i'm finally trying to tackle https://bugzilla.novell.com/836149 -- that is, update VDR to version 2.x My plan is to use a mix of home:balta3:vdrdevel and home:frispete:vdr2 (which partly links to the former). Hans-Peter has kept the vdr.spec based on the one in the vdr repo, making the history more obvious. I additionally plan to integrate runvdr-extreme-systemd directly into the vdr package and get rid of the original runvdr, along with the /etc/sysconfig/vdr and /etc/init.d/vdr The problem: this will break the configuration after updating from VDR-1.6.x. If I don't find an easy way to convert /etc/sysconfig/vdr to /etc/runvdr.conf on update, I'll probably just print a warning during update to let people know that the VDR configuration needs manual review. I'll add a README.SUSE which will explain how to move from the old config to the new one. Another option would be to just call the new package "vdr2" and make it conflict with vdr, so that it is not silently installed as an update and people immediately notice that they need to do something. We could also copy the old packages to vdr:legacy or such, for people who rather use the old version (if you don't have HD capable hardware, vdr 1.6 might be "good enough") Any ideas? People who want to suggest "create a sophisticated update process that makes sure that the update does work and the config is converted" are welcome to take over VDR maintainership and do that. I personally have planned to do this for a very long time now (even when VDR-2.0 was still 1.7.xx) and finally realised that I'll never have enough time to do this. That's why I'm now opting for the above approach, which will be less work (and which will make use of the work that Marcel and Hans-Peter have already done, thanks for that). Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 5

[opensuse-factory] enabling trusted local DNS resolver by default
by Felix Miata 11 Apr '14

11 Apr '14

Some here may recall I started http://lists.opensuse.org/opensuse/2014-01/msg00008.html on Jan 1 and a long discussion following. I wound up setting up dnsmasq on my LAN server. An extended power outage last month left me with Samba/CIFS problems on the LAN. In the process of finding a solution I disabled dnsmasq and changed resolv.conf on all Linux installations booted since to use the IP of my router. I still have dnsmasq turned off. The fedora-devel list just had https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver announced. I searched openFATE for anything similar and recognized nothing. Is this something 13.1 and/or 13.2 already has? If not, is it planned and Google just failed to locate anything about it on opensuse.org for me? If not already existing or planned, shouldn't it be? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Tubleweed: Problem with radeon driver
by Stefan Zimmer 11 Apr '14

11 Apr '14

hi, I have 2 different AMD-APU'a, one older A8, and a brandnew A10-6800K with an integrated AMD HD8670D. Both systems have problems with the graphics driver radeon. When boting with a fresh tumbleweed, the KDM login screen is shown, and after around 10 seconds, the system crashes, and resets. it means, the screen is getting black, and the system is booting. Booting the 3.14 - recovery kernel, everything works, but without graphics acceleration. Booting an older 3.11 kernel, everything works fine. What I did: - Install 13.1 => Reboot: everything works fine - Update => Reboot: everything works fine - Switch to tumbleweed => Reboot: error happens Greetings, Stefan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] German Umlauts displayed wrong
by Johannes Kastl 10 Apr '14

10 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Evening everybody, one issue, that I keep getting intermittently and which I now had time to look into. I did a search in bugzilla, but found nothing relevant, maybe because of the wrong keywords... On the ttys (CRTL+ALT+1 to 6, I forgot the exact name) the german umlauts öÖüÜäÄ are displayed wrong, when I hit those keys. Seems like two characters each are displayed, as I end up with 'undeletable' characters on the prompt: I type in three ä's, which get displayed as six characters. I can press delete more three times, but only three characters are getting deleted. But those visible are not being 'used', I can type in 'ls' after them and ls is being called. Happens with root and normal users. I set everything to english via yast (System -> Language), just kept the german keyboard layout. No change. Set root to have no CTYPE. No change. Now, funny thing: Logging out and in again, wrong umlauts displayed. localectl says keyboard-layout is de-latin1. # localectl set-keymap de-latin1-nodeadkeys -> works Next time this happens with de-latin1-nodeadkeys, and setting to de-latin1 fixes it, but only in this tty. Not in others. Happens a lot, only in ttys, not in KDE konsole/xterm or similar. The multiple-characters-per-keystroke-thingy sounds to me like some UTF-8-issue, but thats way out of my league.. Can anyone help? Anyone else seeing this? Systems used are tumbleweed installations, the one normal 13.1 has not been used that much, so maybe I have just not seen it there. Regards, Johannes P.S.: Sorry if the description is a bit confusing, but its just too late... ;-) - -- Obscene? Obscene is young men being trained to drop fire on people, but their commanders not allowing them to write 'fuck' on their airplanes because it's obscene. (unknown) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlNFqroACgkQzi3gQ/xETbJEyQCdH2Q2vpHU43Qu3dbTKgCeINhY TngAn2F3ITLKJmaTmfu8Gibzy8evFq4v =kmPE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] Apache:Modules need more active maintainership
by Tomáš Chvátal 10 Apr '14

10 Apr '14

Hello guys, after checking review queue for various devel projects I noticed the Apache:Modules project is not geting enough love. Currently just 2 requests that are open for >2 months, but I closed (merged) quite few. Usually this falls under factory-maintainer group when we know what to do there after such long period of time. But when the requests get complex or there are quite few of them it would be nicer to have more interested and dedicated maitnainers on the topic. Any takers that want to play with Apache? Cheers Tom

4 7

[opensuse-factory] Re: Fwd: FLASH NewsBites - Heartbleed Open SSL Vulnerability
by Sid Boyce 10 Apr '14

10 Apr '14

There is a webinar which appears to be accessible only to members of the SANS Institute - details of the bug below. http://www.computerweekly.com/news/2240217841/EFF-calls-for-rapid-mitigatio… Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Secure Boot Keys
by Günther J. Niederwimmer 09 Apr '14

09 Apr '14

Hello, can any tell me the place I can found the openSUSE / SUSE Secure Boot Key files ? After export the certificate from the Bios I found only ASUS, Microsoft and Canonical (?) Keys / Certificate in the files. I never install a Ubuntu (?). I like to install this files manually, I hope afterward I can test with Secure Boot ;). - mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] TW zypper dup wants to change packages to openSUSE repo
by Ken Schneider - Factory 08 Apr '14

08 Apr '14

openSUSE 13.1 using TumbleWeed Today's zypper dup results in the following: ************************************* toshiba-lt:~ # zypper dup Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... The following 7 NEW packages are going to be installed: kernel-default-devel-3.14.0-23.3.gfa168d7 kernel-desktop-3.14.0-23.3.gfa168d7 kernel-desktop-devel-3.14.0-23.3.gfa168d7 kernel-devel-3.14.0-23.2.gfa168d7 kernel-source-3.14.0-23.2.gfa168d7 kernel-syms-3.14.0-23.2.gfa168d7 kernel-xen-devel-3.14.0-23.2.gfa168d7 The following 3 packages are going to be REMOVED: kdeconnect-kde libpublictransporthelper11 plasmoid-flights The following 142 packages are going to be upgraded: MPlayer amarok branding-openSUSE digikam-doc elfutils gfxboot-branding-openSUSE gmplayer gstreamer gstreamer-0_10 gstreamer-0_10-plugins-base gstreamer-lang gstreamer-plugins-bad gstreamer-plugins-base gtk2-engine-oxygen gtk2-theme-oxygen k3b kde-gtk-config-lang kdeartwork4-icons kdeartwork4-wallpapers kdeartwork4-wallpapers-weather kdebase4-openSUSE kdebase4-runtime-branding-openSUSE kdebase4-workspace-branding-openSUSE kdegames4-carddecks-default kdelibs4-branding-openSUSE ... The following 123 packages are going to be downgraded: NetworkManager-kde4-libs NetworkManager-kde4-libs-lang NetworkManager-novellvpn-kde4 NetworkManager-openconnect-kde4 NetworkManager-openvpn-kde4 NetworkManager-pptp-kde4 NetworkManager-strongswan-kde4 NetworkManager-vpnc-kde4 akonadi akonadi-runtime ... The following 127 packages are going to change vendor: NetworkManager-kde4-libs obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-novellvpn-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-openconnect-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-openvpn-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-pptp-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-strongswan-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-vpnc-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE ... 142 packages to upgrade, 123 to downgrade, 7 new, 3 to remove, 127 to change vendor. Overall download size: 534.6 MiB. After the operation, additional 685.8 MiB will be used. Continue? [y/n/? shows all options] (y): n toshiba-lt:~ # Is it normal for packages to be changed back to the "current" repo after having been moved to TW? I have set the TW repo to a higher priority so I would expect packages once moved to TW to stay there. -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 9

[opensuse-factory] PPC builds stuck
by Andrey Borzenkov 08 Apr '14

08 Apr '14

For several days ppc/ppc64 builds are stuck with openSUSE_Factory_PowerPC ppc64le building: building on build90:5 bor@opensuse:~/obs/home:arvidjaar:grub2-next:libgcc/grub2> osc results -v openSUSE_Factory_PowerPC ppc unresolvable: have choice for libblkid.so.1 needed by systemd-mini: libblkid1-64bit libblkid1 have choice for libblkid.so.1(BLKID_2.15) needed by systemd-mini: libblkid1-64bit libblkid1 have choice for libblkid.so.1(BLKID_2.17) needed by systemd-mini: libblkid1-64bit libblkid1 have choice for libuuid.so.1 needed by util-linux: libuuid1-64bit libuuid1 have choice for libuuid.so.1(UUID_1.0) needed by util-linux: libuuid1-64bit libuuid1 have choice for libblkid.so.1 needed by util-linux: libblkid1-64bit libblkid1 have choice for libblkid.so.1(BLKID_1.0) needed by util-linux: libblkid1-64bit libblkid1 have choice for libblkid.so.1(BLKID_2.15) needed by util-linux: libblkid1-64bit libblkid1 have choice for libblkid.so.1(BLKID_2.17) needed by util-linux: libblkid1-64bit libblkid1 have choice for libmount.so.1 needed by util-linux: libmount1-64bit libmount1 have choice for libmount.so.1(MOUNT_2.19) needed by util-linux: libmount1-64bit libmount1 have choice for libblkid.so.1(BLKID_2.18) needed by util-linux: libblkid1-64bit libblkid1 have choice for libmount.so.1(MOUNT_2.20) needed by util-linux: libmount1-64bit libmount1 have choice for libblkid.so.1(BLKID_2.20) needed by util-linux: libblkid1-64bit libblkid1 have choice for libblkid.so.1(BLKID_2.21) needed by util-linux: libblkid1-64bit libblkid1 have choice for libmount.so.1(MOUNT_2.21) needed by util-linux: libmount1-64bit libmount1 have choice for libmount.so.1(MOUNT_2.22) needed by util-linux: libmount1-64bit libmount1 have choice for libmount.so.1(MOUNT_2.23) needed by util-linux: libmount1-64bit libmount1 have choice for libmount.so.1(MOUNT_2.24) needed by util-linux: libmount1-64bit libmount1 have choice for libmount.so.1(MOUNT_2.25) needed by util-linux: libmount1-64bit libmount1 have choice for libblkid.so.1 needed by udev-mini: libblkid1-64bit libblkid1 have choice for libblkid.so.1(BLKID_2.15) needed by udev-mini: libblkid1-64bit libblkid1 have choice for libblkid.so.1(BLKID_2.17) needed by udev-mini: libblkid1-64bit libblkid1 have choice for libblkid.so.1(BLKID_2.18) needed by udev-mini: libblkid1-64bit libblkid1 ppc64le works. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] HEADS-UP: logrotate changes
by Cristian Rodríguez 08 Apr '14

08 Apr '14

Hi: Today an update to logrotate has hit the factory repositories and I think it is prudent to inform you all about some changes I added to the package and its side effects, either for documentation purposes or JFYI. ;) - Logrotate no longer runs as a cronjob but as a systemd.timer(5) - You can enable/disable log rotation by issuing systemctl enable/disable logrotate.timer - It continues to run just like "cron.daily" with the following bonus perks: * Log rotation will be postponed until your are connected to AC power, in order not drain your precious battery time. * The task will run as soon as possible in case your system was turned off, suspended or otherwise inactive at the time the process was scheduled (requires systemd 212 or later) * If any error is found, the results will be found in the journal (and/or syslog if installed) to see what's going on issue: systemctl status logrotate.service logrotate.timer Observed problems/gotchas: zypp installs packages in an unsuitable order, systemd-presets that enable the timer by default may be installed after the logrotate update. thus it does not get automatically enabled. to ensure things keep running smoothly in your factory installation: $ systemctl enable logrotate.timer $ systemctl start logrotate.timer Have a lot of fun :-) -- Cristian Team PITA -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 41

[opensuse-factory] Switch to ifup from NetworkManager make system unusable
by Ken Schneider - Factory 07 Apr '14

07 Apr '14

Due to on going problems with NetworkManager not working for /me/ I changed to ifup method. The results created a system that was */NOT/* usable. I could not login to tty1 at all. Trying to use root resulted in an error that the login name was invalid. Trying to use my login name would not accept my password. Login via tty[2-6] would let me login but I would get auto-logged out after approximately 30 seconds making any effort to trouble shoot the problem fruitless. Fortunately I was able to ssh to the problem laptop and yast to change back to NetworkManager for the network and the system booted properly. openSUSE 13.1 --> Tumbleweed Toshiba Satellite L75D-A7288 Is anyone else seeing this problem? -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] XWayland
by Dominique Leuenberger a.k.a. Dimstar 07 Apr '14

07 Apr '14

Hi all! GNOME 3.12.0 has been integrated into GNOME:Factory (submission to openSUSE:Factory due in time), and we started looking at the 'next wish on the list', coming from users, which happens to be GNOME on Wayland. In a branch, I configured the entire GNOME stack as required, without any big issues. There is one very important component missing though: * XWayland Seems our X Server in Factory does not know the -wayland parameter, and as a consequence, it is not possible to trigger a whole GNOME Session on top of wayland (using weston, it remains possibly to launch parts of it, but that's no fun). Are there any plans already to get XWayland into Factory as well? AFAIK, the code base has been merged into X Codebase after a three year effort (Kudos to the people hanging in there for so long). If this is no target for 13.2, then there won't be any reason for the GNOME Team to enable the stack neither of course; Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Tumbleweed: libvirtd dead/inactive after laptop suspend?
by Johannes Kastl 06 Apr '14

06 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, can someone using Tumbleweed and libvirt confirm, that the libvirtd.service is not restartet after suspending a laptop? It starts ok when shut down and restarted, but is inactive after the laptop went to sleep and is woken up... Regards, Johannes - -- There are only two kinds of music: Rock and Roll. (Keith Richards) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlM/4FoACgkQzi3gQ/xETbLizACfUGNkXASxvm8k6klwZrvS2Sk8 V4sAoIvuPdkGaQCmgkh5Mg54hU0X0tYM =aUpE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 6

[opensuse-factory] pulsaudio, broken after kernel update
by C. Brouerius van Nidek 05 Apr '14

05 Apr '14

After the last zypper dup in Tumbleweed which mainly got me the latest kernel (see signature) my sound has gone. Pulseaudio is there, uses a lot of my cpu (22 to 60%). On my KDE desktop I have standard running kmail, chromium and skype (which of course is also not working) Remembering from the past i played around with Yast, sound and alsaconf. alsactl kill and alsactl start did nothing. A reboot with the second last kernel ( 3.14.0-22.g79de0a7-default) gave me my sound back and pulseaudio without cpu use. Am I the only one with this problem? A bug report? - - Linux User 183145 using KDE4 and LXDE on a Pentium IV , powered by openSUSE 13.1 (i586) Kernel: 3.14.0-23.gfa168d7-default KDE Development Platform: 4.12.3 14:54pm up 0:45, 4 users, load average: 2.80, 3.95, 4.64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 8

Re: [opensuse-factory] Re: grub2 vs. by-label
by Andrey Borzenkov 04 Apr '14

04 Apr '14

[sorry for accident off-list copy] В Wed, 2 Apr 2014 18:34:45 +0200 Olaf Hering <olaf(a)aepfle.de> пишет: > On Wed, Apr 02, Andrey Borzenkov wrote: > > > В Wed, 2 Apr 2014 18:23:08 +0200 > > Olaf Hering <olaf(a)aepfle.de> пишет: > > > On Wed, Apr 02, Andrey Borzenkov wrote: > > > > How exactly MBR signature or GPT GUID help here? > > > Not at all. At least grub has no concept of "use partition where the > > > files actually reside". Instead it has some odd device.map. > > > grub2 is (most likely) not any better. > > grub2 is using filesystem UUID to find partition where files actually > > reside. > > grub2 is the thing in /usr/*bin, not what runs in firmware context. > It is using OS device names. It will consult device.map only if called with deprecated (hdX) disk designation. openSUSE today puts /dev/disk/by-id in bootloader configuration. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 17

[opensuse-factory] HEADS up: GNOME:Factory breakae
by Dominique Leuenberger 04 Apr '14

04 Apr '14

Hi all, Just want to inform you that GNOME:Factory is currently seeing the integration of GNOME 3.12.0 (Factory targeted) and is due to this not in the best of shapes; I expect the builders to catch up shortly and have a stable repository published soon. The integration work had been done earlier in GNOME:Next, so in general we know what is coming and what is missing. Ensure to already read up on all the goodies GNOME 3.12.0 will bring you, like some redesigned apps (like gedit, videos, pocket integration into gnome-online-accounts...) Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] grub2 vs. by-label
by Sascha Peilicke 04 Apr '14

04 Apr '14

Hi guys, our default grub2 configuration always uses UUIDs. For several reasons, I'd like to use labels instead but when looking at the scripts that generate /boot/grub2/grub.cfg it looks like UUID is more or less the only thing that works. So before I start tinkering with the scripts I'm curious if there is some prior art around already. -- Viele Grüße, Sascha Peilicke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 16

[opensuse-factory] tumbleweed: cannot build nvidia 331.49 for kernel 3.14.0
by Patrick Shanahan 04 Apr '14

04 Apr '14

kernel-desktop 3.14.0-23.1.g79de0a7 kernel-desktop-devel 3.14.0-23.1.g79de0a7 kernel-devel 3.14.0-23.1.gfa168d7 cannot build nvidia driver 331.49 for this kernel ??? test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; full err logs @ http://wahoo.no-ip.org/~pat/nvidia-installer.log Anyone able? How? tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 11

[opensuse-factory] network install, but no network interfaces configured? iproute2 wasn't even installed?
by Per Jessen 04 Apr '14

04 Apr '14

I'm guessing that Factory is now supposed to work as a single-phase installation? Or do I still run /usr/lib/Yast/startup/Yast.ssh when the system boots the first time? On this system, no interfaces were configured on the first boot-up, and /usr/lib/Yast/startup/Yast.ssh didn't want to run because run_me_at_boot wasn't found. I tried "ip addr" to check the network interfaces, but iproute2 wasn't even installed? -- Per Jessen, Zürich (16.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 10

[opensuse-factory] manpage for 'lvcreate' -- does factory have info for thinpools?
by Linda Walsh 04 Apr '14

04 Apr '14

The utility 'lvs' has [--alloc AllocationPolicy] [--thinpool ThinPoolLogicalVolume{Name|Path}] [--poolmetadatasize Size[bBsSkKmMgG]] That don't seem to be in the manpage in 13.1... Is this fixed in factory? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] Installation - no option to change hostname and domain?
by Per Jessen 04 Apr '14

04 Apr '14

I've just realised - yesterday when I installed Factory, I did not see the yast window which would enable me to set the hostname and domain. I think it also enables me to check the "change hostname via DHCP" box. Was this removed intentionally? -- Per Jessen, Zürich (11.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Re: Mesa for Tumbleweed
by Greg KH 03 Apr '14

03 Apr '14

On Thu, Apr 03, 2014 at 12:12:36PM +0200, langkamp(a)tomblog.de wrote: > > Greg KH <gregkh(a)linux.com> hat am 2. April 2014 um 00:37 geschrieben: > > > > > > On Wed, Apr 02, 2014 at 12:25:04AM +0200, Tobias Klausmann wrote: > > > (snip) > > > >>I'd suggest: > > > >> > > > >>X11:XOrg for Mesa 10.1 > > > >>https://build.opensuse.org/package/show/X11:XOrg/Mesa > > > >$ osc whatdependson openSUSE:13.1 Mesa standard i586 | wc -l > > > > 2003 > > > > > > > >Hah, yeah right, I'm not going to do that, sorry. > > > > > > > >>devel:tools:compiler for llvm 3.4 > > > >>https://build.opensuse.org/package/show/devel:tools:compiler/llvm > > > >I can add this, but is is really used by anyone? > > > > > > It is used to compile parts of/for Mesa, but with you not adding Mesa, it > is > > > more or less pointless to add it. > > > > Ok, I'll go remove it then, thanks. > > > > greg k-h > > Thanks greg for looking into this. I understand that it's too much work? It means I would have to have _all_ of 13.1 in the Tumbleweed repo. Things would be constantly rebuilding. I would have to do a lot more work, and Tumbleweed would be a stand-alone distro image at that point in time. And that's something I've said I was NOT going to do at all every time this has come up in the past. > Maybe the work would seem worthwhile when we know how many people would like > this update. So I opened a request on openFATE: > > https://features.opensuse.org/317173 > > I'll be back when a "reasonable" number of supporters votes this up :) So, it will somehow, because people want this, become more "managable"? That's not how things work, sorry. If you want the latest Mesa, try it in your own private repo and let me know how it goes. Or use the X11:XOrg repo. But given that this is a low-level library, with almost everything depending on it one way or the other, it is going to be tough going, sorry. best of luck, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 6

[opensuse-factory] net+ssh install - running yast just gives me .... yast ?
by Per Jessen 03 Apr '14

03 Apr '14

Previously, when installing over ssh, one only had to type/run 'yast', but this just ends up in the normal YaST menu. It looks like I now need to run 'yast.ssh', is that correct? -- Per Jessen, Zürich (16.5°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] Mesa for Tumbleweed
by Thomas Langkamp 03 Apr '14

03 Apr '14

Would it be possible to have Meas 10.x and LLVM 3.4 in Tumbleweed? That would be really good for radeonSI users (OpenGL 3.1 instead 2.1) and is would be much appreciated since openSUSE 13.2 is delayed... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 9

[opensuse-factory] Grub2-EFI and GOP Support for UEFI Systems and 13.2
by Roman Bysh 03 Apr '14

03 Apr '14

Hello List mates, Now that new laptops and motherboards have switched to UEFI it is essential that GOP should be supported. Does any one know that Grub2-EFI for openSUSE 13.2 will add GOP support in the Yast Boot Loader? At the moment most people must add this manually to grub.cfg: insmod efi_gop insmod efi_uga insmod font if loadfont ${prefix}/unicode.pf2 then insmod gfxterm set gfxmode=auto set gfxpayload=keep terminal_output gfxterm fi Any thoughts? Cheers! Roman -------------------------------------------- openSUSE -- Get it! Discover it! Share it! -------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] Inclusion of Pitivi 0.92 and its dependencies to Tumbleweed
by Yonsung Lee 02 Apr '14

02 Apr '14

Hi all (first time mailing here, so pardon me if mistakes are made), The current version of Pitivi available for OpenSUSE:Stable is 0.15. It's buggy and limited, and was released in 2011. Since then, Pitivi has switched to using Gstreamer Editing Services (GES) as its platform, and its performance and stability has improved *exponentially*. The current stable release (0.92) is much more usable than 0.15. As far as I remember, there are two dependencies that need to be added as well, gstreamer-editing-services and GNonLin 1.1.90. Links to factory: https://build.opensuse.org/package/show?project=openSUSE% 3AFactory&package=pitivi https://build.opensuse.org/package/show?project=openSUSE% 3AFactory&package=gstreamer-editing-services https://build.opensuse.org/package/show?project=openSUSE% 3AFactory&package=gnonlin It would be great if this could be added to Tumbleweed, as we all know Linux users are in need of an intuitive yet versatile video editor. Thanks in advance, Y.L. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 6

[opensuse-factory] Finding a home for frescobaldi
by Cor Blom 02 Apr '14

02 Apr '14

Hi, For some time I am building frescobaldi[1] in my home project. I would like to move it on the road toward factory and am looking for a suitable devel project. Although the origin lies in KDE it is nowadays a Qt app. I would say multimedia:apps is a good project. If no-one objects or has other ideas, I will prepare a SR. Frescobaldi is a lilypond editor. Thanks, Cor [1] http://www.frescobaldi.org/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] Base:System util-linux, regarding sr 226509
by Stanislav Brabec 02 Apr '14

02 Apr '14

Ruediger Meier wrote: > On Friday 21 March 2014, Stanislav Brabec wrote: > > Ruediger Meier wrote: > > > Hi, > > > > > > The ChangeLog is almost useless since none of the referenced bug > > > reports is readable for non-suse people. > > > > These changelogs were taken from the original changelog. Many of > > openSUSE changelogs refer to bugs that are not accessible. In ideal > > case, people working on SLES fix would post the same patch to > > openSUSE, and make a public clone of the bug report. It did not > > happened, and a review found these patches, where the patch was not > > posted to Factory nor upstream. > > > > > At least one of the added patches ("umount-avoid-readlink.patch") > > > has no effect because it patches a deprecated and unused subdir > > > which will be removed in next release anyway. > > > > Yes, it is deliberate. The patch was created for SLE11 and affects > > the code, which is now deprecated and not used. I did not want to > > lose this patch and save it for upstreaming. > > Upstream has already removed the whole code. If upstream dropped "mount-deprecated" completely, then the patch as is is obsolete, and can be dropped now (or in the next version that will have no "mount-deprecated" code). > > Collecting upstream-able patches will take some time. Hopefully these > > patches will disappear from the Factory then. > > I'd like to help to get useful patches upstream. But it's hard if I'm > not allowed to know anything about the fixed issues. Well, there is also a lot of openSUSE patches, that need to check its universal validity. Regarding the SLES11 patches: sfdisk-warn-about-2TB-limit.patch: The msdos partition table is suppose to address up to 2 TB LUNs. Sfdisk didn't stop (or warning) the user about this limitation and went ahead created partition beyond 2 TB. After the reboot, the device node for the partition starting above 2TB was not created. Fix is impossible, but sfdisk should warn about it. The same bug in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=324525 util-linux-ng-2.16-squashfs3-detect.patch: Detection of squashfs3 filesystem was requested. util-linux-ng-2.19.1-barrier_documentation.patch: The description of the 'barrier' mount option was request. Patch was written by Jan Kára. He wrote in the bug, that he sent the patch to the upstream as well. Maybe it was lost. util-linux-update-default-commit-interval.patch: Customer pointed out with the inclusion of the linux-2.6.29-jbd-longer-commit-interval.patch, changing "kjournald starting. Commit interval 15 seconds" from the long standing default "5 seconds", the "mount" man pages are no longer correct. Obsoleting of uuid-runtime: That package existed between SLE11 SP1 and SLE11 SP3 and probably sometimes in past. I failed to track the package origin, but it is safe to keep Obsoletes in the spec file. umount-avoid-readlink.patch: The problem existed (exists?) on NFS (reproduced on SLE11 SP2 on s390x, but probably was (is?) reproducible on all platforms): 1) sudo mount -t nfs4 -o sec=sys,intr,noac,nordirplus machine:/dir,binary /mnt 2) stop/reconfig NFS server 3) sudo umount -f /mnt umount2: Stale NFS file handle umount.nfs4: /mnt: Stale NFS file handle umount2: Stale NFS file handle umount.nfs4: /mnt: Stale NFS file handle sudo umount /mnt umount.nfs4: /mnt: Stale NFS file handle umount.nfs4: /mnt: Stale NFS file handle File conflict: Package s390-32 contains files s390 and s390x conflicting with util-linux and breaks installation on System Z. uname26: There was a request to support uname26 in PAM (it already is) and have a simple to use uname26 binary. > > > Please somebody have a look at the last changelog and either make > > > the bug reports world-readable or fix the changlog to explain the > > > purpose of these patches: > > > > SLES bug reports that contain sensitive customer data cannot be > > opened for public. > > Have you really checked all the bug reports and they all contain > sensitive data? Well, if the bug is reported against SLES, there is no way to make it public in Bugzilla. The only way is making an openSUSE clone. Most of SLE bugs contain commercial support information, machine configurations and similar sensitive data. > > Most of these patches are self descriptive. Well, this one is > > probably not true for umount-avoid-readlink.patch: > > > > It's purpose is avoiding a readlink() failure when umount'ing stale > > NFS volumes. > > But today your patch only changes unused code. If this is still an issue > in the new code then your patch will not fix it. Volunteer reviewers > (like me) cannot really check if there is still an issue or not. Also > I'd like to check whether this patch would be good for Evergreen 11.4. I know. The code of umount is completely rewritten, and I was not able to determine, whether it is still needed. I plan to do test of these problems and then either port them or drop. > > > * lscpu: improve hypervisor detection (puzel(a)novell.com, > > > fate#310255) > > This patch for example breaks a test in the test suite. None of us can > read the discussion about this new feature. non-SLE people had no > chance to say their opinion about it. Patch was written by Petr Uzel. There was requested detection of all Hypervisors on x86_64, System Z and Power in lscpu and detect virtual graphic adapters. Adding him to Cc. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +49 911 7405384547 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 8

[opensuse-factory] wow
by Peter Czanik 02 Apr '14

02 Apr '14

Hello, I just did a fresh installation of factory. Network manager in KDE displays an error, but networking seems to work fine. $SUBJECT is "wow" because I don't recall openSUSE booting ever so fast! What was changed? I did not check with a timer, but it seems to be faster now than other distros, while earlier openSUSE was among the slow starters. Not that it matters on a machine I turn on only once a day, but still :-) Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 25

[opensuse-factory] Re: Security issue: Proposal to revert to '/' on sep. part. from /usr,/home,/tmp,/var, etc
by Linda Walsh 02 Apr '14

02 Apr '14

Claudio Freire wrote: > Excuse the top posting, on a cell here and it's difficult to bottom post. --- Most gui email programs make it easier to put the most recent stuff at the top -- organizing a timeline from most-recent - older as you go down. Professions that need things organized chronologically tend to use this (medical, legal). Only those who think every detail is important, all the time, for everyone, force bottom posting. > I don't think patching the bare minimum is a good idea in this case... > the more restricting the rules are the less likely the issue remains > exploitable in yet unknown ways. --- Get rid of root entirely -- no exploits... Maybe cut the power as well. Let's take no halfway measures, eh? Um... you are changing system wide security policy. It seems like doing the minimum necessary to disable your exploit(s), is the best idea since every little bit that you change will cause more incompatibility for some program(s) somewhere -- not to mention this breaks posix rules, linux DACL rules, normal unix access restrictions, to name a few. > But maybe restrictions can be relaxed a bit to allow for your use case, > if it is common enough. Can you show an application that is broken by > current rules and that cannot be fixed without changes to the rules? ---- Can you show that your changes break no existing applications? You are proposing the changes but there's been no proof that any compatibility testing was done other than "ubuntu did it". Ubuntu, of course, is known to cater to the technically sophisticated users... who would be likely to use a variety of security scheme, right? Noooop. Ubuntu was designed for those coming from windows -- designed to take away decision points and make things simpler -- which I AGREE with -- but not at the expense of flexibility. I know the features can be turned off, BUT, Some vendors are designing new distro features based on the reduced functionality offered by the increased restrictions -- like putting everything on 1 partition. That used to be considered "bad system administration" and a bad practice for security, maintenance and reliability. It still is, but convenience is trumping everything else. > What you mentioned in the op seems a rather niche use you scripted > yourself and unlikely to be common. ---- Now here's where you are way off, as well as trying to create a self-fulfilling trap. ANY time you script something, it means you have a custom solution -- that by definition is a 'niche use'. If it could be done without a script, it would be a general use case implemented as a feature. Well guess what. There is no script involved. It's a general use case: "cp -al". I've been on many projects where one copy of the source was the pristine, read-only source, and people used links to create a low-space usage copy. This allowed them to create files as 'new files' where they made changes -- everything else was a read-only link enforced by it being a different UID. It may not be a common use case for home users, but for anyone who does development, it's among the simplest and easiest way to create a local "copy" that you can make changes to while keeping the overall disk cost low where you are re-using the original code. > For those cases specifically, there's a sysctl to disable hardlink > protection. ---- Actually, having the hardlink protections disabled are the default case. Opensuse turned them on in /usr/etc/sysctl.conf. Why wouldn't less overwhelming patch work? Specifically w/r/t prot.hardlinks: 1) cannot hard link to a setXID file unless you could create it yourself. 2) cannot link to/from a file in a world-writable sticky-directory. 3) Root privileges will not override sticky bit rules in the case of opening w/write. I.e. if a file already exists in temp owned by another user, root cannot open the file for write in 1 step. They must first either move or remove the sticky file. The latter step (3) makes the system safer than your proposed solution -- since as it is now, root can overwrite (accidently) any user created tmp file in /tmp, possibly destroying valuable work. ========================= Conversely -- specific criticisms of the new implementation: users can hardlink only to writable, regular files. The reasoning is to prevent race conditions and users writing into files expected to be used by root; BUT -- the new restrictions disable hardlinking to other file system objects -- in ALL CASES except where their UID=the object's UID. This disables Group control as well as control by access lists. A great deal of work has gone into making access lists viable -- and work went into making group access viable as well -- yet this disables both of those access methods for controlling hardlinking to writable objects (other than regular files). The irony, is that you can't have setXid objects other than *files* -- and the TOU exploits don't apply, EXCEPT to files... (i.e. they don't apply to hardlinking to symlinks, as you can't rewrite the symlink, they don't apply to other objects either -- named pipes? sockets? semaphores? None of those suffer from the TOU exploits -- yet they were all disabled unilaterally -- and don't even work when you have write access to those objects. ???? That doesn't make sense. If the idea was to protect against TOU problems, why disable linkability to other objects (besides files)? > If you can show a more widespread use case that is similarly affected, > that will encourage kernel developers to come up with less restrictive rules ---- The onus should be on those proposing the wide-ranging and incompatible new rules to prove why they are needed to the extent implemented. If no proof is needed, then just eliminate root, or pull the plug -- the former is practical with FLASK/SeLinux. But the problem is the bigger the change, the more things you break -- which is why I argue for the minimal change necessary. If you want a maximal solution, SELinux is already available. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] libwrap still broken over 2 years later...
by Linda Walsh 01 Apr '14

01 Apr '14

Just rebooted (it had been 60 days since last reboot), and it picked up the new tcpd/libwrap0 files from 13.1 (am pretty sure it's not fixed in factory, given it hasn't been fixed in over 2 years)... This is still a problem: http://lists.opensuse.org/opensuse/2011-10/msg00351.html Thought it was reported as I have a patch file... making sure it is reported here: https://bugzilla.novell.com/show_bug.cgi?id=861989 (had problems w/attachment, so am including it here as well..).

4 4

[opensuse-factory] Security issue: Proposal to revert to '/' on sep. part. from /usr,/home,/tmp,/var, etc
by Linda Walsh 01 Apr '14

01 Apr '14

WTF? Am I crazy? Following is a chain of logical events that have happened and are likely to happen that will cause even more security patches to compensate for the merge of '/' with other partitions (include /usr/share -- which was supposed to be independently sharable, yet the keyboard services needs it to load 'locales'). The conclusion is at the end, if you are one of those who are impaired with the TLDR disease. Well, yeah, and? The new setup is being used as a justification for a need for a new and ill designed security feature: "protected_hardlinks" that disables standard, legacy linking ability. In 13.1, this feature is turned on by default. That causes side effects, like not being able to copy a R/O source-tree with "cp -al", into a 2nd copy of symlinked dirs w/hard-linked file objects. To me, that was a basic source control mechanism -- anything that was the same between the two (or 20 trees) shared the same file and was read-only as someone other than the owner of the original source tree (often root). Local mods in source files could be made in your source tree but they wouldn't propagate to to the source copy. Now, such a setup is impossible in the default suse config unless a user has access to root and/or is willing to risk overwriting the original source. The main justification for protected_hardlinks was to protect users from linking to files that used to be on *separate* file systems (/etc/{shadow,group,passwd}) to use for some further exploit -- claim a lost of files and a need for their homedir to be restored via some util that writes to a hardlinked file w/root privs, for example. But now, along comes the protected_hardlinks feature which doesn't do the same job. It allows linking, only, to _regular files_ that you have write access to. Logically, to get around the inability to link w/o write access, one might think to make sure the copying user is in the same group as the target files and use group write access. That causes 2 problems: 1) it doesn't solve the original requirement of keeping the original source tree read-only to other users (i.e. if the users have write access through the group, they can overwrite the original, but worse, 2) protected_hardlinks was implemented to inconsistently allow hardlinking to objects in in the source tree. While it used to be the case that one could hardlink to any readable non-directory on the same device, protected_hardlinks changes that to allow hard-linking not just to "writeable" files, but only *regular files*. This means for example, that the kernel source tree can no longer be copied by anyone other than the tree owner due to symlink usage in the kernel (that were previously hardlinked to): > find . -type l|xargs ls -dgGl|cut -c30-999 ./arch/arm/boot/dts/include/dt-bindings -> ../../../../../include/dt-bindings ./arch/metag/boot/dts/include/dt-bindings -> ../../../../../include/dt-bindings ./arch/microblaze/boot/dts/system.dts -> ../../platform/generic/system.dts ./arch/mips/boot/dts/include/dt-bindings -> ../../../../../include/dt-bindings ./arch/powerpc/boot/dts/include/dt-bindings -> ../../../../../include/dt-bindings Of less commonality, but also affected were hardlinks to named pipes, sockets, -- any other file system object -- except for dirs which, on linux, have pretty much always been disallowed. Notably, now, we have a broken workaround to re-create security lost by previously having a separate root (broken in that it only partly works for some objects), but it's already being discussed how utility (applications will have to follow) progs will deal with making copies when "cp -al" is used -- i.e. it is likely that linux will fall back to DOS-level functionality where copies are made for any file object that doesn't support linking. This has a further security impact: any ACL's or security labels on a readable file will be stripped unless the copying user has the ability to recreate them (often not true if the source tree was designed to be read-only to the copier). I found that to already by a problem when 'mv'ing files -- a few samba versions mistakenly put NT-acl's in the 'security' or 'system' namespace, when such ACL's are not native acls, but a user-app (samba) level data-blob. That issue was raised with the samba team, and it appears it will be addressed, though no official statement was made about the security hole (a Windows user who has login access to the domain will be able to, by default, strip the file of it's NT-ACL just by moving it to another partition or by copying it (whether they intend this or not -- it's not a good side-effect). ========================= **TLDR: In short, the joining of the partitions has already caused broken security workarounds to go into the kernel (that still need to be fixed), and is in the process of requiring system utils and applications to invent workarounds for the security implications -- that themselves cause their own set of security issues that will need more patches, and likely cause more rounds. I.e. this is a case of a bad decision causing a chain of worsening and growing side effects. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 7