February 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] 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] 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] 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] 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] Releases going forward
by Robert Schweikert 31 Mar '14

31 Mar '14

Hi, Releases going forward, or, how do we release without full time paid worker bees? With all the discussion toward the end of last year I suppose that today's e-mail "Timeline and roadmap V2" [1] finally shed light on the inevitable conclusion, the openSUSE team (@SUSE) will spend more time on other stuff and less time, if any, on turning the release crank. This is the team's prerogative just like everyone is free to work on the project, or not, in areas of interest to them. We can argue whether the way this is coming about is giving the project the best chance to succeed or whether the transition is being put worth in a nice and friendly way, but I think we should not go down that path. Thanks! to the openSUSE Team for the hard work they have put forth in the past to turning the release crank, it is much appreciated. I think the time has come to move forward and deal with the new situation. As of right now we still have a release cycle of 8 month. That would put us into May for openSUSE 13.2. This brings about two questions: - Given the current situation can we meet a May release date? - Do we skip the May release and move to a yearly cycle and release 13.2 in November of 2014? During last year's discussions there were a number of people favoring a yearly release cycle. We have to make a decision, - stick to 8 month or move to 12 month? Voice your opinion but stick to the point and please be concise. For simplicity lets just assume that there will be no full time paid help to turn the release crank and that the work is all on those that are not part of the openSUSE Team. Under any circumstances I'd say our first go around will be a bit rough around the edges and that's OK, we have to learn. What do I have to offer? After all stuff will not get done by me sending an e-mail into the world. I offer to take on part of the role of "Release Manager". I will not be able to do all of it and I have a new definition for the role (see below.) Stephan did way more and was always the tireless worker that brought everything together. No one that does not work on openSUSE full time can obviously fulfill that role, thus we have to split things up. I figure there are about 60 to 70 hours worth of work per week that we have to distribute. I'll define "Release Manager" as: The person or group that runs after people, keeps an eye on the schedule and tries to herd the cats to get the stuff fixed that is broken. I am willing to take part of that role, and with this mail hopefully be a rallying point to put openSUSE releases on a bit more of a solid footing than where we are today, after [1]. If we go this route it implies that everyone that has stuff in Factory, what will become the next release, nothing there changes, has more responsibility in helping out than they do today. We no longer have people that can fix everything and get to spend all their time on the distribution and integration of stuff. Every maintainer has more responsibility. So where do we go from here? Do we bootstrap an effort to get a release out the door without openSUSE @SUSE or do we drift along in the uncertainty of "maybe we know something in August"? I am happy to be a rallying point and fulfill part of the role of "Release Manager" as outlined above. Maintainers/Packagers be heard, speak up, but lets not drift into rat holes, the situation is actually quite simple. Later, Robert [1] http://lists.opensuse.org/opensuse-factory/2014-01/msg00350.html -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

30 62

[opensuse-factory] Virt-Manager 1.0
by Christian Grassi 22 Mar '14

22 Mar '14

Hi all, Is there any plan to have virt-manager 1.0 in Tumbleweed. Thanks Christian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 15

[opensuse-factory] New package apache2-mod_authn_otp
by Archie Cobbs 02 Mar '14

02 Mar '14

I'd like to add this package to factory. It's been in Apache:Modules and used in production for several years now. apache2-mod_authn_otp mod_authn_otp is an Apache web server module for two-factor authentication using one-time passwords (OTP) generated via the HOTP/OATH algorithm defined in RFC 4226. This creates a simple way to protect a web site with one-time passwords, using any RFC 4226-compliant hardware or software token device. mod_authn_otp supports both event and time based one-time passwords. It also supports "lingering" which allows the repeated re-use of a previously used one-time password up to a configurable maximum linger time. This allows one-time passwords to be used directly in HTTP authentication without forcing the user to enter a new one-time password for every page load. mod_authn_otp supports both basic and digest authentication, and will auto-synchronize with the user's token within a configurable maximum offset (auto-synchronization is not supported with digest authentication). mod_authn_otp is especially useful for setting up protected web sites that require more security than simple username/password authentication yet also don't require users to install special VPN software, and is compatible with software tokens that run on cell phones. Thanks, -Archie -- Archie L. Cobbs -- 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] bluetooth audio performance
by Alejandro Bonilla 02 Mar '14

02 Mar '14

Hi there, I got a few bluetooth speakers that behave very well but not when the source is my laptop. I'm inclined to think there is either a power management issue or a degradation? of the bluetooth signal after several minutes (10-15). for which I need to go into the Control Panel, disable Bluetooth, set it back on and off it goes well. While misbehaving, the audio is cutting off and is pretty behind to my play/pause actions. Is there some performance tuning that could be done to fix this? Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] I don't see much help with btusb vermagic: 3.11.10-7-desktop SMP preempt mod_unload modversions parm: ignore_dga:Ignore devices with id 08fd:0001 (bool) parm: ignore_csr:Ignore devices with id 0a12:0001 (bool) parm: ignore_sniffer:Ignore devices with id 0a12:0002 (bool) parm: disable_scofix:Disable fixup of wrong SCO buffer size (bool) parm: force_scofix:Force fixup of wrong SCO buffers size (bool) parm: reset:Send HCI reset command on initialization (bool) and bluetooth parm: disable_esco:Disable eSCO connection creation (bool) parm: disable_ertm:Disable enhanced retransmission mode (bool) parm: enable_hs:Enable High Speed support (bool) I wonder if anyone else is having a similar problem and if any of these were any good? Thanks, Alejandro -- 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] LXC in factory/Tumbleweed?
by Johannes Kastl 01 Mar '14

01 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, as LXC got quite a lot of attention in the last weeks, I thought I would give it a spin. But I do not find any recent lxc in tumbleweed, and factory still has beta1 (AFAICS). Before I try building it myself, are there any plans to upgrade/add a package for the latest stable release? Maybe I am missing a repo, if so please tell me to RTFM. ;-) Regards, Johannes - -- `You place too much importance, and you always have done, on the so-called purity of blood. You fail to recognise that it matters not what someone is born, but what they grow to be!´ (Albus Dumbledore, Harry Potter and the Goblet of Fire) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlMPks0ACgkQzi3gQ/xETbJ5/QCbBYOeFuI2zT83Fjvt7RLoQhi6 iVAAniw0EWtgPKFOZLdqo6LA0oXkKaJH =Jii+ -----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

2 2

[opensuse-factory] Fedora exploring using XFS as it's default filesystem
by Greg Freemyer 28 Feb '14

28 Feb '14

I don't know if anyone cares, but I was surprised to see: <http://oss.sgi.com/pipermail/xfs/2014-February/034582.html> It looks like early phase exploration on the one hand, but on the other hand Red Hat Beta 7 is already using XFS as the default filesystem: <http://www.internetnews.com/ent-news/red-hat-enterprise-linux-7-beta-uses-x…> Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 24

[opensuse-factory] Re: [opensuse-buildservice] CI rights management
by Jos Poortvliet 28 Feb '14

28 Feb '14

On Monday 24 February 2014 09:37:52 Sascha Peilicke wrote: > On Sunday 23 February 2014 16:06:26 Jos Poortvliet wrote: > > On Feb 19, 2014 5:32 PM, "Sascha Peilicke" <speilicke(a)suse.com> wrote: > > > Hi guys, > > > > > > since more and more openSUSE projects start to make use of our CI > > > infrastructure, we have to organize who's allowed to do what. In the > > > past > > > > we > > > > > just added more and more people with rights to organize everything. So > > > I > > > > tried > > > > > to reduce the global list of users with admin rights. Instead, we now > > > > have a > > > > > per-project (translates to Jenkins job) ACL matrix where each project > > > can > > > organize stuff themselves. In simple words, you now can configure per > > > job > > > who's allowed to change things. There should be no need to bug me again > > : > > :-) > > : > > > That said, the list of ci.o.o admins now is: > > > coolo, jdsn, bmwiedemann and saschpe (me). > > > > > > The following openSUSE projects currently use ci.opensuse.org: > > > - Open Build Service / osc > > > - OpenStack > > > - Yast / libyui > > > > > > The first two projects have per-job based access rules set already. If > > > you > > > have a ci.o.o job and want to grant somebody the right to modify it, > > > just > > > check "Enable project-based security" and add the (already registered) > > > > user in > > > > > question. > > > > > > And if you want to add your openSUSE-related project to our CI, please > > > > get in > > > > > touch with any of the guys mentioned above. That's it. > > > > I am guessing there is a wiki page where this is documented, perhaps it > > would be possible to link to that page from http://ci.openSUSE.org? > > I have to admin that ci.opensuse.org is slightly under-documented. However, > I'd like to avoid creating huge wiki pages that run out of sync. Instead, > the CI boys already agreed to add/extend Jenkins job descriptions and > similar things so that this is more obvious. I guess having a small wiki > page about "how to get your stuff tested" wouldn't hurt... Yeah, I'm not a big fan of huge wiki pages either... More than something like: --- If you have a ci.o.o job and want to grant somebody the right to modify it, just check "Enable project-based security" and add the (already registered) user in question. And if you want to add your openSUSE-related project to our CI, please get in touch on openSUSE=packaging (?). --- is probably not needed... Might even fit on the jenkins page.

1 0

[opensuse-factory] Tumbleweed and NetworkManager
by Ken Schneider - openSUSE 28 Feb '14

28 Feb '14

Running 13.1 TumbleWeed with latest updates. Toshiba laptop L75D-A7288 toshiba-lt:~ # lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Complex 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8550G] 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Port 00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Port 00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 16) 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11) 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40) 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 5 01:00.0 Ethernet controller: Qualcomm Atheros AR8162 Fast Ethernet (rev 10) 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01) toshiba-lt:~ # I have been having problems with the NM widget not showing available networks whether it be wired or wireless. Works fine when logged in as root. Found the following errors in /var/log/messages; ************************************************** Feb 22 17:42:08 toshiba-lt systemd: pam_unix(systemd-user:session): session opened for user ken by (uid=0) Feb 22 17:42:08 toshiba-lt systemd[2340]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socke t: No such file or directory Feb 22 17:42:09 toshiba-lt systemd[2340]: Stopped target Sound Card. Feb 22 17:42:09 toshiba-lt systemd[2340]: Starting Default. Feb 22 17:42:09 toshiba-lt systemd[2340]: Reached target Default. Feb 22 17:42:09 toshiba-lt systemd[2340]: Startup finished in 300ms. Feb 22 17:42:09 toshiba-lt systemd[1]: Started User Manager for 1000. Feb 22 17:42:09 toshiba-lt checkproc: checkproc: can not get session id for process 1371! Feb 22 17:42:10 toshiba-lt dbus[537]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.69" (uid=1000 pid=2476 co mm="kdeinit4: kded4 [kdeinit] ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=555 comm="/usr/sbin/NetworkManager --no-daemon ") Feb 22 17:42:10 toshiba-lt dbus[537]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.69" (uid=1000 pid=2476 co mm="kdeinit4: kded4 [kdeinit] ") interface="org.freedesktop.NetworkManager" member="GetDevices" error name="(unset)" requ ested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=555 comm="/usr/sbin/NetworkManager --no-daemon ") Feb 22 17:42:11 toshiba-lt dbus[537]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Feb 22 17:42:11 toshiba-lt dbus[537]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Feb 22 17:42:13 toshiba-lt dbus[537]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.69" (uid=1000 pid=2476 co mm="kdeinit4: kded4 [kdeinit] ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=555 comm="/usr/sbin/NetworkManager --no-daemon ") Feb 22 17:42:13 toshiba-lt dbus[537]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.69" (uid=1000 pid=2476 co mm="kdeinit4: kded4 [kdeinit] ") interface="org.freedesktop.NetworkManager" member="state" error name="(unset)" requested _reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=555 comm="/usr/sbin/NetworkManager --no-daemon ") Feb 22 17:42:13 toshiba-lt dbus[537]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.73" (uid=1000 pid=2516 co mm="kdeinit4: plasma-desktop [kdeinit] ") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_ reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=555 comm="/usr/sbin/NetworkManager --no-daemon ") Feb 22 17:42:13 toshiba-lt dbus[537]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.73" (uid=1000 pid=2516 co mm="kdeinit4: plasma-desktop [kdeinit] ") interface="org.freedesktop.NetworkManager" member="state" error name="(unset)" requested _reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=555 comm="/usr/sbin/NetworkManager --no-daemon ") Feb 22 17:42:13 toshiba-lt dbus[537]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.73" (uid=1000 pid=2516 co mm="kdeinit4: plasma-desktop [kdeinit] ") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_ reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=555 comm="/usr/sbin/NetworkManager --no-daemon ") Feb 22 17:42:13 toshiba-lt dbus: Last message '[system] Rejected se' repeated 4 times, suppressed by syslog-ng on toshiba-lt *************************************** Not sure if it is a dbus problem or not. Problem seems to come and go depending on updates that get installed. I install updates, the applet works fine - install next batch of updates the applet is empty again. -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.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

[opensuse-factory] new font{,s-}config
by Petr Gajdos 27 Feb '14

27 Feb '14

Hi list, please take a look on these two packages located in home:pgajdos. (Non)changes ============ 1. SUSE specific configuration is there exclusively provided by fonts-config package. 2. Default configuration and configuration options is somewhat based on infinality-fontconfig ideas (some points are not though): a. Families with good instructions (based on infinality database) are grouped together in 10-group-tt-hinted-fonts.conf. b. For this group, autohinter defaults to off, for other families is autohinter on. This is most significant change to previous default configuration, where autohinter was turned on only for enumerated families. c. Hinting default remains same, hintfull (=on) for BCI, hintslight for autohinter. d. Antialias remains of course on by default. e. lcdfilter is set to lcdnone, rgba is set to none. This is subject to change if we will find an agreement, but keep in mind that this configuration depends for example on display rotation and, to my knowledge, can't be changed in majority of running applications. f. When ms fonts are not installed, default families are DejaVu Sans, Liberation Serif and Liberation Mono, which is recommended by infinality. g. 10-rendering-options.conf contains possible modifications of the above default, for example (i) force autohinter for all fonts (to my testing only, can produce more thick glyphs, but some glyphs can be more blurred) (ii) force nonsmoothed black and white rendering (without antialias). Default sans font then changes to Liberation Sans, which gives quite readable results for latin, cyrillic and greek. I have not elaborated for other scripts so far, help is appreciated. (iii) infinality-like option to force black and white rendering for good hinted monospaced fonts (e. g. Liberation Mono) (iv) more, like embedded bitmap, lcdfilter, rgba, hinstyle setup. 3. 10-rendering-options.conf is generated from template though; it is created depending on new sysconfig variables in /etc/sysconfig/fonts-conf. In this sysconfig, you can even choose prefered sans, serif and monospaced families. (All is prepared to create a yast module :).) Statistics ========== See the attachment created as diff of fontinfo output. There are many changes with signature '-bci -3 +autohint +1' which basically means 'use autohinter with hintslight(1) instead of native hinter with hintful(3)'. This is related to 2.b. and expected. When you grep out these lines, you get AnonymousProBold -autohint -1 +bci +3 AnonymousProBoldItalic -autohint -1 +bci +3 AnonymousProItalic -autohint -1 +bci +3 AnonymousProRegular -autohint -1 +bci +3 CantarellBold -3 +1 CantarellRegular -3 +1 ElhamRegular -3 +1 HomaRegular -3 +1 IPAGothicBoldBold -bci +autohint IPAGothicBoldItalicBoldItalic -bci +autohint IPAGothicItalicItalic -bci +autohint IPAGothicRegular -bci +autohint IPAMinchoRegular -bci +autohint IPAPGothicBoldBold -bci +autohint IPAPGothicBoldItalicBoldItalic -bci +autohint IPAPGothicItalicItalic -bci +autohint IPAPGothicRegular -bci +autohint IPAPMinchoRegular -bci +autohint IPAUIGothicRegular -bci +autohint IPAexGothicRegular -bci +autohint IPAexMinchoRegular -bci +autohint KoodakRegular -3 +1 Migu1MBold -bci +autohint Migu1MRegular -bci +autohint NazliBold -3 +1 NazliRegular -3 +1 RoyaBold -3 +1 RoyaRegular -3 +1 TerafikBold -3 +1 TerafikRegular -3 +1 TitrBold -3 +1 WenQuanYiMicroHeiRegular -bci +autohint IPA* families changes can be ignored because they are rendered with hintstyle=hintnone by special fontconfig anyway. But otherwise, if you see something odd, please let me know. Please dispute, comment and TEST! Thanks, Petr

2 4

[opensuse-factory] Thread Break, re: openSUSE Cheat Sheet - Technical Input Needed
by Patrick Shanahan 27 Feb '14

27 Feb '14

* Jan Engelhardt <jengelh(a)inai.de> [02-15-14 16:30]: > On Saturday 2014-02-15 20:31, Bruno Friedmann wrote: > >> > >> http://en.opensuse.org/Cheat_openSUSE_13.1 > > > >excellent thanks for the page. > >One question, shouldn't we advertise parted in place of fdisk which > >doesn't know how to handle GPT disk ? > > fdisk 2.24 knows GPT. parted does not know sectors apparently :) I have a 4T seagate drive formatted GPT by yast and family which works fine in openSUSE 13.1 as long as I do not try to reboot the box with the drive set to auto-mount. It is lvm one partition ext4 and when trying to boot 13.1 with the drive auto-mount, boot fails with lvm problem and reports it is in "maintenance mode" but never provides a prompt to log in. Almost pulled my remaining hairs out before realizing that drive was the problem rather than my lvm ssd system drive. The new speedy boot makes err msgs fly by quite quickly. I can boot with a "live" cd/dvd and the lvm is "Active" and I can mount it w/o any action other than creating a mount point and: mount -t ext4 /dev/mapper/<lvm-name> mount-point I realize that this undoubtedly deserves a bug report. What should be reported against what and what logs provide relative info? kernel-desktop-3.11.10-7.1.x86_64 -- (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

6 14

[opensuse-factory] networkd and wicketd
by Matwey V. Kornilov 26 Feb '14

26 Feb '14

Hi, I've read that systemd 210 is supplied with networkd for network configuration. There are .link unit files where one can configure his network. How is it related to wicketd? Will they both be able to work on the same PC not interfering each other? Or networkd to be disabled in opensuse? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 10

[opensuse-factory] apache2 fails to start
by Sid Boyce 25 Feb '14

25 Feb '14

Bug #865567 submitted. slipstream:/home/lancelot # systemctl start apache2.service Job for apache2.service failed. See 'systemctl status apache2.service' and 'journalctl -xn' for details. slipstream:/home/lancelot # systemctl status apache2.service -l apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled) Active: failed (Result: exit-code) since Tue 2014-02-25 13:21:30 GMT; 16s ago Process: 7030 ExecStop=/usr/sbin/start_apache2 -D SYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=1/FAILURE) Process: 6978 ExecStart=/usr/sbin/start_apache2 -D SYSTEMD -DFOREGROUND -k start (code=exited, status=1/FAILURE) Main PID: 6978 (code=exited, status=1/FAILURE) Feb 25 13:21:30 slipstream start_apache2[6978]: Module "systemd" is not installed, ignoring. Feb 25 13:21:30 slipstream start_apache2[6978]: Check the APACHE_MODULES setting in /etc/sysconfig/apache2. Feb 25 13:21:30 slipstream start_apache2[6978]: httpd2-prefork: Syntax error on line 177 of /etc/apache2/httpd.conf: Syntax error on line 99 of /etc/apache2/default-server.conf: Syntax error on line 1 of /etc/apache2/conf.d/mod_evasive.conf: Cannot load /usr/lib64/apache2/mod_evasive20.so into server: /usr/lib64/apache2/mod_evasive20.so: cannot open shared object file: No such file or directory Feb 25 13:21:30 slipstream systemd[1]: apache2.service: main process exited, code=exited, status=1/FAILURE Feb 25 13:21:30 slipstream start_apache2[7030]: Module "systemd" is not installed, ignoring. Feb 25 13:21:30 slipstream start_apache2[7030]: Check the APACHE_MODULES setting in /etc/sysconfig/apache2. Feb 25 13:21:30 slipstream start_apache2[7030]: httpd2-prefork: Syntax error on line 177 of /etc/apache2/httpd.conf: Syntax error on line 99 of /etc/apache2/default-server.conf: Syntax error on line 1 of /etc/apache2/conf.d/mod_evasive.conf: Cannot load /usr/lib64/apache2/mod_evasive20.so into server: /usr/lib64/apache2/mod_evasive20.so: cannot open shared object file: No such file or directory Feb 25 13:21:30 slipstream systemd[1]: apache2.service: control process exited, code=exited status=1 Feb 25 13:21:30 slipstream systemd[1]: Failed to start The Apache Webserver. Feb 25 13:21:30 slipstream systemd[1]: Unit apache2.service entered failed state. /etc/apache2/conf.d/mod_evasive.conf ------------------------------------------------- LoadModule evasive20_module /usr/lib64/apache2/mod_evasive20.so <IfModule mod_evasive20.c> # l /usr/lib64/apache2/mod_evasive* -rwxr-xr-x 1 root root 19008 Dec 8 06:00 /usr/lib64/apache2/mod_evasive24.so* 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

2 1