July 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

[opensuse-factory] xgettext aborts [Fwd: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64]
by Bernhard Voelker 30 Nov '15

30 Nov '15

What happened to xgettext? [ 198s] /usr/bin/xgettext --default-domain=coreutils --directory=.. \ [ 198s] --add-comments=TRANSLATORS: --keyword=_ --keyword=N_ --flag=_:1:pass-c-format --flag=N_:1:pass-c-format --flag=error:3:c-format --flag=error_at_line:5:c-format --flag=asnprintf:3:c-f ormat --flag=asprintf:2:c-format --flag=error:3:c-format --flag=error_at_line:5:c-format --flag=vasnprintf:3:c-format --flag=vasprintf:2:c-format --flag=verror:3:c-format --flag=verror_at_line:5:c- format --flag=wrapf:1:c-format --flag=xasprintf:1:c-format --flag=xfprintf:2:c-format --flag=xprintf:1:c-format --from-code=UTF-8 --keyword=proper_name:1,'"This is a proper name. See the gettext ma nual, section Names."' --keyword=proper_name_utf8:1,'"This is a proper name. See the gettext manual, section Names."' ${end_of_xgettext_options+} --flag=error:3:c-format --flag=error_at_line:5:c-f ormat --keyword='proper_name:1,"This is a proper name. See the gettext manual, section Names."' --keyword='proper_name_utf8:1,"This is a proper name. See the gettext manual, section Names."' --flag =asprintf:2:c-format --flag=vasprintf:2:c-format --flag=verror:3:c-format --flag=verror_at_line:5:c-format --flag=xprintf:1:c-format --flag=xvprintf:1:c-format --flag=xfprintf:2:c-format --flag=xvf printf:2:c-format --flag=xasprintf:1:c-format \ [ 198s] --files-from=./POTFILES.in \ [ 198s] --copyright-holder='Free Software Foundation, Inc.' \ [ 198s] --package-name="${package_gnu}coreutils" \ [ 198s] --package-version='8.22' \ [ 198s] --msgid-bugs-address="$msgid_bugs_address" \ [ 198s] ;; \ [ 198s] esac [ 198s] *** Error in `/usr/bin/xgettext': realloc(): invalid pointer: 0x00000000018ff590 *** [ 198s] ======= Backtrace: ========= [ 198s] /lib64/libc.so.6(+0x7343f)[0x7fa6640e043f] [ 198s] /lib64/libc.so.6(+0x78cae)[0x7fa6640e5cae] [ 198s] /lib64/libc.so.6(+0x7bde5)[0x7fa6640e8de5] [ 198s] /usr/lib64/libgettextlib-0.19.1.so(xrealloc+0xe)[0x7fa66445b56e] [ 198s] /usr/bin/xgettext[0x40b301] [ 198s] /usr/bin/xgettext[0x40b38d] [ 198s] /usr/bin/xgettext[0x40b4e1] [ 198s] /usr/bin/xgettext[0x40b98e] [ 198s] /usr/bin/xgettext[0x40ba93] [ 198s] /usr/bin/xgettext[0x40c340] [ 198s] /usr/bin/xgettext[0x406953] [ 198s] /usr/bin/xgettext[0x4052cc] [ 198s] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fa66408eb05] [ 198s] /usr/bin/xgettext[0x405ba3] Have a nice day, Berny -------- Original Message -------- Subject: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64 Date: Wed, 11 Jun 2014 18:15:31 +0000 From: hermes(a)opensuse.org Reply-To: hermes(a)opensuse.org To: mail(a)bernhard-voelker.de Package coreutils-testsuite (version 8.22-248.68) of project Base:System failed to build for openSUSE_Factory / x86_64. Review the build log: osc remotebuildlog Base:System coreutils-testsuite openSUSE_Factory x86_64 | less Check out the package for editing: osc checkout Base:System coreutils-testsuite -- Hermes messaging (http://hermes.opensuse.org) openSUSE Build Service (https://build.opensuse.org/) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

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] Updating bind to 9.10?
by Johannes Kastl 30 Nov '14

30 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, is there any reason (other than "lack of time" or "no one did it", why there is no package for bind's latest version 9.10 on the OBS (except for one arch package)? I had a look at the spec and suddenly decided, that I lack the skills to update the package. Too many patches doing whatever it is, etc. 9.10 has some features, that would come in handy, so I would appreciate if someone had time to update (or guide me through updating...). Thanks in advance. Regards, Johannes - -- I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlPaZ9UACgkQzi3gQ/xETbKeYwCeLzq6umhcepTr8yoID64hmjdn GnQAnio6XDDvbvJ6eExyg0rG49aWeVNJ =VPXk -----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] 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] What happened to smb-krb-printing?
by Robert Munteanu 04 Sep '14

04 Sep '14

Hi, Just realized that I no longer have smb-krb-printing installed, last I used it was on 12.3 . Looking at [1], I see that while 12.3 is OK, 13.1 only has it in a home repo, while Factory only has it as an old 32-bit package. Is this intentional? Is there an alternative? Thanks, Robert [1]: http://software.opensuse.org/package/samba-krb-printing -- http://robert.muntea.nu/ -- 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] 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] factory oss and non-oss gpg keys expired
by Jon Nelson 06 Aug '14

06 Aug '14

I've seen this referenced a bunch of times, but I don't know how to resolve it. I've done this: zypper clean --all zypper -v up and I'm using factory (not 13.2) - per the wiki page of how to run Factory. These are the urls I'm using: http://download.opensuse.org/factory/repo/non-oss http://download.opensuse.org/factory/repo/oss How do I fix this problem? Why isn't it fixing itself? -- Jon -- 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] 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] VLC does not start up in KDE4.13.3
by Roman Bysh 03 Aug '14

03 Aug '14

Hello all, Recently I've been having problems with VLC initializing with it's interface. I can start it up using "cvlc" from konsole. Using openSUSE 13.1. This is copied from konsole: vlc VLC media player 2.1.5 Rincewind (revision 2.1.4-49-gdab6cb5) [0x7fd4b8021318] qt4 generic error: cannot start Qt multiple times [0x19f6828] skins2 interface error: no suitable dialogs provider found (hint: compile the qt4 plugin, and make sure it is loaded properly) [0x19f6828] skins2 interface error: cannot instantiate qt4 dialogs provider [0x19f6828] main interface error: no suitable interface module [0x19e23b8] main interface error: no suitable interface module [0x18a60b8] main libvlc error: interface "globalhotkeys,none" initialization failed [0x19f6828] [cli] lua interface: Listening on host "*console". VLC media player 2.1.5 Rincewind Command Line Interface initialized. Type `help' for help. > [0x18a60b8] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [0x19526d8] qt4 interface error: cannot start Qt multiple times Segmentation fault -- 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

3 5

[opensuse-factory] Staging Dashboard
by Stephan Kulow 02 Aug '14

02 Aug '14

Hi, To illustrate the staging workflow, there is now a dashboard showing the various projects and their health status. As there are various components involved, the view obviously simplifies - but it should be good enough for everyone to see where we are: https://build.opensuse.org/factory/staging_projects Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 12

[opensuse-factory] About package inclusion request.
by jcsl 01 Aug '14

01 Aug '14

Hi. Can I request the inclusion of packages from user's projects? Are there any requirements to be met for a package to be taken into consideration? Greetings. -- 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] new package: evemu
by Stefan Brüns 01 Aug '14

01 Aug '14

Hi, I would like to add a new package to openSUSE Factory: evemu evemu includes several tools. One is evemu-record, which can serve as a better evtest, as it knows several event ids evtest does not know. Additionaly, it can record device information and events to a file, which can be later digested by evemu-device and evemu-play, which creates a virtual device and plays back the recorded events. More information can be found here: http://who-t.blogspot.de/2013/11/evtest-is-dead-long-live-evemu.html evemu has a runtime dependency on libevdev, which is currently packaged in X11:XOrg. Which development project would be best: 1. X11:Xorg, as it has libevdev, although evemu is not really X related 2. Base:System, like input-utils (evtest), which does not have libevdev currently. I have prepared a evemu package in https://build.opensuse.org/project/show/home:StefanBruens:evemu Kind regards, Stefan -- 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] GNOME Repo layout change & GNOME 3.13.x
by Dominique Leuenberger a.k.a. Dimstar 31 Jul '14

31 Jul '14

Hi GNOMEs! I know you have been patiently waiting for a sign of life from the GNOME Team.. sorry for the quietness, but we did not get lost; we are still here with you and for you. As the geeko following GNOME releases knows, GNOME 3.13.4 (the branch potentially leading to GNOME 3.14) has been released last Wednesday. As usual, the packages have been ready by that time in the Build Service, but you want to know HOW to get there, don't you? In line with the 're-targeting' of Factory, there are a few changes in repositories that you should be aware of: - openSUSE Factory => The 'Base' distribution repository we develop for - GNOME:Factory => latest STABLE GNOME Version, receiving regular updates of the stable branch, to keep GNOME in Factory 'up-to-date'; This is a small change, as it means you no longer get 'unstable' branches of GNOME in here. But it gets you (hopefully!) stable experience, which you can expect 'quickly' to land in openSUSE:Factory - GNOME:Next => This is where all the fun happens now: the NEXT release of GNOME is prepared here If it breaks, we're happy; if it works, we're even happier. In short: no 'guarantee' at any moment that this works; but I run it on my system. With this new layout, we believe to be able to better deliver upon the promise of a 'stable Factory'. Of course, this means lower speed of IN Factory, but users can rely on it. The GNOME Team runs as a bare minimum GNOME:Factory on top of that; in quiet times (between two major GNOME releases), this will be only very few differences, but we 'test' bug-fixes in here. And the crazy part of the GNOME Team is asked to run GNOME:Next (but is also asked to FIX stuff they break :) ) for you as User? Pick you poison! Carefully balance between new/stable and be prepared for an occasional break, the 'newer' you get. Users of GNOME:Next are most welcome, but encouraged to also hang around on IRC (#opensuse-gnome @ freenode) to have a short communication line to the team; and who knows? If you like it enough, you might be our new most active team member in no time! Special not when adding the repositories: GNOME:Next depends on GNOME:Factory depends on openSUSE:Factory; make sure to add THE FULL chain of repositories. Put the priorities right, so zypper dup knows what to do. All nice and good, you DO want to test GNOME 3.13.x, but for nothing on the world do you want to run Factory on your disk or mess with all those repositories? We are regularly building a live image, based on the GNOME:Next stack! there is NO QA (neither automatic nor manual) happening on it; at best, some of us might try to boot it every now and then. For the curious ones, it is available at http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME… Questions? Comments? As usual, simply approach us! Best regards, Dominique / DimStar openSUSE GNOME Team -- 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] Searching for command to check if a kernel is signed
by Roman Bysh 31 Jul '14

31 Jul '14

Hello All, What is the command to check if my kernel is signed? -- 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

5 8

[opensuse-factory] Status: Tests
by Stephan Kulow 31 Jul '14

31 Jul '14

Hi, lxde tests fail, e.g.: https://openqa.opensuse.org/tests/15587 xfce tests fail, e.g.: https://openqa.opensuse.org/tests/15588 btrfs on lvm crashes, e.g.: https://openqa.opensuse.org/tests/15588 dual_windows8 tests fail, e.g.: https://openqa.opensuse.org/tests/15550 kde/kwin crashes still more often than it should on kvm: https://openqa.opensuse.org/tests/15550 yast update from 12.3 fails: https://openqa.opensuse.org/tests/15571 console font on live cds hosed: https://openqa.opensuse.org/tests/15518 We need people to look into all of these if we want to get nearer a 13.2 Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 19

[opensuse-factory] "rolling release" 0728 won't http install
by Felix Miata 31 Jul '14

31 Jul '14

Intallation system cannot find repo, whether: download.opensuse.org or mirrors.kernel.org or using burned boot.iso or loading initrd & linux with grub -- "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 3

[opensuse-factory] vbox guest conflict
by Vahis 30 Jul '14

30 Jul '14

I get this with fresh factory install in VBox 4.3.14r95030 from Oracle: #### YaST2 conflicts list - generated 2014-07-30 10:24:07 #### nothing provides kernel-uname-r = 3.15.5-1.g01d2774-default needed by virtualbox-guest-kmp-default-4.3.12_k3.15.5_1.g01d2774-1.8.x86_64 [ ] do not install virtualbox-guest-tools-4.3.12-1.8.x86_64 [ ] break virtualbox-guest-kmp-default-4.3.12_k3.15.5_1.g01d2774-1.8.x86_64 by ignoring some of its dependencies #### YaST2 conflicts list END ### -- Vahis -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] php 5.6
by Petr Gajdos 30 Jul '14

30 Jul '14

Hello, please find RC2 of php 5.6 in devel:languages:php:php56. See http://php.net/manual/en/migration56.php I will replace 5.5 by it in factory once final is out, if there are no objections. Happy testing! Petr

1 0

[opensuse-factory] Migrate gitorious.org/opensuse/desktop-data and bugfix
by Guido Berhoerster 30 Jul '14

30 Jul '14

Hi, can someone from the gitorious opensuse maintainers please accept https://gitorious.org/opensuse/desktop-data/merge_requests/4 and migrate the repo over to github? The package is actually maintained by Will but he's been completely unresponsive to notifications, bugmail and personal mails and the fix is needed for Factory (bnc#871978). Thanks, -- Guido Berhoerster -- 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] 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] yast problem on Factory, bug?
by Patrick Shanahan 28 Jul '14

28 Jul '14

Tried adjusting a user group via "YaST2 users". YaST2 opens and selecting "User and Group Management" opens a window which shows a loading bar (30%), idle for 30 seconds or so and closes/crashes. So I tried as root, "yast users" which presents a similar situation. I get: Unknown config. Invalid snapshot ''. y2log for the "yast users" is at: http://wahoo.no-ip.org/~pat/y2log.txt bug report? against? to attention of? rpm -qa yast*|sort yast2-3.1.85-1.2.x86_64 yast2-add-on-3.1.8-1.2.noarch yast2-apparmor-3.1.2-1.2.noarch yast2-auth-client-3.1.17-1.1.noarch yast2-backup-3.0.0-2.1.4.noarch yast2-bootloader-3.1.67-1.2.x86_64 yast2-control-center-3.1.3-1.3.x86_64 yast2-control-center-qt-3.1.3-1.3.x86_64 yast2-core-3.1.7-1.2.x86_64 yast2-country-3.1.9-1.2.x86_64 yast2-country-data-3.1.9-1.2.x86_64 yast2-firewall-3.1.1-2.6.noarch yast2-hardware-detection-3.1.3-1.2.x86_64 yast2-http-server-3.1.0-1.7.noarch yast2-inetd-3.1.5-1.2.noarch yast2-inetd-doc-3.1.5-1.2.noarch yast2-installation-3.1.101-1.1.noarch yast2-iscsi-client-3.1.14-1.2.noarch yast2-ldap-3.1.11-1.2.x86_64 yast2-mail-3.1.2-1.5.noarch yast2-mail-plugins-3.0.0-2.1.4.noarch yast2-metapackage-handler-3.1.3-1.1.noarch yast2-network-3.1.70-1.2.x86_64 yast2-nfs-client-3.1.6-1.1.noarch yast2-nfs-common-3.1.7-1.2.noarch yast2-nfs-server-3.1.7-1.2.noarch yast2-nis-client-3.1.8-1.3.x86_64 yast2-ntp-client-3.1.9-1.2.noarch yast2-online-update-3.1.5-1.2.noarch yast2-online-update-frontend-3.1.5-1.2.noarch yast2-packager-3.1.30-1.2.x86_64 yast2-pam-3.1.1-1.6.noarch yast2-perl-bindings-3.1.2-1.1.x86_64 yast2-pkg-bindings-3.1.15-1.3.x86_64 yast2-printer-3.1.1-1.7.x86_64 yast2-proxy-3.1.1-1.2.noarch yast2-qt-branding-openSUSE-13.2-2.57.noarch yast2-restore-3.0.0-2.1.4.noarch yast2-ruby-bindings-3.1.21-1.2.x86_64 yast2-samba-client-3.1.9-1.2.noarch yast2-samba-server-3.1.9-1.2.noarch yast2-scanner-3.1.1-1.8.x86_64 yast2-schema-3.1.0-1.5.noarch yast2-security-3.1.3-1.3.noarch yast2-services-manager-3.1.21-1.1.noarch yast2-slp-3.1.6-1.2.x86_64 yast2-snapper-3.1.3-1.3.x86_64 yast2-sound-3.1.4-1.5.x86_64 yast2-storage-3.1.37-2.2.x86_64 yast2-sudo-3.1.1-1.8.noarch yast2-sysconfig-3.1.1-1.3.noarch yast2-theme-openSUSE-3.1.21-1.1.noarch yast2-trans-en_US-3.0.0-13.1.noarch yast2-transfer-3.1.1-1.7.x86_64 yast2-trans-stats-2.19.0-15.6.noarch yast2-tune-3.1.3-1.2.x86_64 yast2-update-3.1.18-1.2.x86_64 yast2-users-3.1.27-1.2.x86_64 yast2-vm-3.1.15-1.2.x86_64 yast2-x11-3.1.3-1.3.x86_64 yast2-xml-3.1.1-1.5.x86_64 yast2-ycp-ui-bindings-3.1.7-1.2.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

2 2

[opensuse-factory] Published Factory
by Stephan Kulow 28 Jul '14

28 Jul '14

Hi, There are still bugs shown in the test (e.g. mkfs.btrfs crashing the kernel on LVM setups), but I dared to push the button. As usual, for details - click around on https://openqa.opensuse.org/tests/overview?distri=opensuse&version=FTT Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

19 36

[opensuse-factory] Cups Monospace preferred to industry fontconfig's generic monospace
by Felix Miata 28 Jul '14

28 Jul '14

I thought this got fixed 6 months ago in the Cups BS repo, which should have passed into Factory by now. https://bugzilla.novell.com/show_bug.cgi?id=856731 is marked fixed, but it is also marked 12.3. When an application specifies monospace, it should get the generic monospace, not Cups' "Monospace". Do those of us who want to have the generic monospace when expected need to have a cron job deleting /usr/share/fonts/ghostscript/Monospace* periodically? -- "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

1 0

[opensuse-factory] Synaptics Gesture Suite for openSUSE 13.2?
by Roman Bysh 26 Jul '14

26 Jul '14

Hello all, Is it possible to have the Synaptics Gesture Suite included with openSUSE 13.2? According to Synaptics it's included with SLED 11. http://www.synaptics.com/en/gesture-suite-linux.php#info_content -- 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 2

[opensuse-factory] Migrating from Tumbleweed to Factory
by Patrick Shanahan 26 Jul '14

26 Jul '14

Took the plunge and migrated my production maching from Tumbleweed to Factory. Mind I have quite a few extra "Tumbleweed build" repos enabled. I made a copy of /etc/zypp/repos.d and edited all active to reflect the correct locations for openSUSE-Factory, including renaming for identity purposes. I backed up the current /etc/zypp and replaced repos.d with the edited copies. Major conflict/resolution list primarly between perl 5.20 and yast packages. Found easiest solution to singularly install perl 5.20 and allow a few package downgrades. Only took two steps and entire system appears as one would expect,ie: no conflicts New kernel 3.16 boots fine. Major Problems With Graphical Display: I have nVidia 450 GTS Had NVIDIA-Linux-x86_64-331.49-custom.run active but was unable to get it to work with kernel 3.16. Dl'd NVIDIA-Linux-x86_64-340.24.run and it installed fine, but... Now the graphic display was sunk in ~1 inch on all four sides and streatched widthwise Have now recovered the Graphical Display, found the /etc/X11/xorg.conf file was not good for the system for some unknown reason. It had been fine for 13.1/Tumbleweed and Tumbleweed previous from the beginning of Tumbleweed. I generated a new xorg.conf with nvidia-xconfig. But I do not know why this was necessary. I found the zypper locks have changed and I cannot figure how to lock multiple repos for a particular package so I made individual locks. The old locks were not correct for openSUSE-Factory. The Graphical Display really had me stumped and I really only recovered due to educated guesses. Life goes on. tks, questions welcome. -- (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

1 0

[opensuse-factory] humongous /var/log/pbl.log
by Felix Miata 24 Jul '14

24 Jul '14

64 bit host big31: 12.3: total size 14,075K tail, all lines for most recent day's activity 992,744 bytes, 9553 lines 13.1: total size 38,404K tail, all lines for most recent day's activity 221,134 bytes, 2133 lines 13.2: total size 79,629K tail, all lines for most recent day's activity 682,444 bytes, 9001 lines Are these expected sizes? Shouldn't they be rotated out as .xz like happens to zypper.log and messages? -- "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

5 8

[opensuse-factory] The future of Tumbleweed
by Greg KH 24 Jul '14

24 Jul '14

Hi all, This came up on the linux-kernel mailing list in a side thread, and I have since had a few people ask me about this on IRC, so I'd like to just consolidate all of the questions here into one thread. I no longer run openSUSE Tumbleweed on my main machines as it is not useful to me anymore. This is not to say that I am no longer maintaining Tumbleweed, thanks to the magic of obs, I am able to keep it up to date just fine by using the obs command line tools from any Linux distro. In fact, most of all of the updates in the past 6 months have been made from a server running Gentoo[1] :) But what this does mean is while I keep checking to see if I made any _major_ mistakes with it, by keeping a virtual machine up to date, and a spare laptop working with it, I am much less likely to notice any problems that occur when running the distro. So, what's my future plans with it? I don't know. I can keep on keeping it up to date as-is, which seems to work as I haven't had any complaints in the past 3-4 months, as no one seems to have noticed... Ideally, Tumbleweed will die with the use of Factory in its place. Factory is a great goal, and one that I really want to see happen, as it fits into my working model (constantly updating stable distro), but from what I have been told, it's just not quite there yet. 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

19 42

[opensuse-factory] Java:repositories cleanup
by Tomáš Chvátal 24 Jul '14

24 Jul '14

Hello guys, as I got the lucky task of playing with our Java packages I started bit of a late spring cleanup. From the list [1] I am going to reduce all the repos to following list: Java:packages Java:packages:maven Java:Factory Java:esemeska If you by any chance have package in any of those repositories that are going away, copy the package to your home and resubmit to Java:packages. There were quite few usefull packages I copied out so I might've overlook some :) So please let me know if you find something worth preserving, otherwise wave the remaining repositories good bye :) Cheers Tom [1] https://build.opensuse.org/project/subprojects/Java

1 0

[opensuse-factory] yast2 sw_single failing
by Felix Miata 23 Jul '14

23 Jul '14

> Removing libproxy1-config-kde4 makes software management in YaST work. > It seems that YaST was rewritten in QT5 and crashes when it tries to > access QT4 libraries. > Now to make Chrome WebGL work again with Mesa 10 and Intel GM45... > - [1601:1601:0722/054908:ERROR:context_group.cc(193)] : > ContextGroup::Initialize failed because too few texture units. > - [1601:1601:0722/054908:ERROR:gles2_cmd_decoder.cc(2355)] : > GpuScheduler::InitializeCommon failed because group failed to > initialize. 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) On 20140721 updated just minutes ago, trying to run YaST2 software in KDE4 I get this instead: Run command: /sbin/yast2 sw_single & terminate called after throwing an instance of 'YUIPluginException' what(): Couldn't load plug-in qt YaST got signal 6 at file /usr/share/YaST2/modules/Wizard.rb:836 /sbin/yast2: line 434: 1565 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Changing to rv380 radeon on same installation it's slightly different: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV380 [Radeon X600] Run command: /sbin/yast2 sw_single & terminate called after throwing an instance of 'YUIPluginException' what(): Couldn't load plug-in qt YaST got signal 6 at file /usr/share/YaST2/modules/Wizard.rb:836 /sbin/yast2: line 434: 1450 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS -- "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

1 0

[opensuse-factory] Mobile broadband suddenly broken
by Richard Weinberger 22 Jul '14

22 Jul '14

Hi! I'm on 13.1+Tumbeweed and mobile broadband stopped working a few days before. I don't exactly know when as I don't use it every day. This is the output of the NetworkManager log: ---cut--- 2014-07-21T16:16:17.003299+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) starting connection 'A1/Telekom Austria - A1 Breitband' 2014-07-21T16:16:17.004086+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0] 2014-07-21T16:16:17.005044+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... 2014-07-21T16:16:17.008557+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... 2014-07-21T16:16:17.009246+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: prepare -> need-auth (reason 'none') [40 60 0] 2014-07-21T16:16:17.009845+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. 2014-07-21T16:16:17.021023+02:00 sandpuppy NetworkManager[963]: get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed 2014-07-21T16:16:17.106087+02:00 sandpuppy NetworkManager[963]: message repeated 18 times: [ get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed] 2014-07-21T16:16:17.140734+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... 2014-07-21T16:16:17.143215+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... 2014-07-21T16:16:17.154112+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: need-auth -> prepare (reason 'none') [60 40 0] 2014-07-21T16:16:17.154754+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. 2014-07-21T16:16:17.159736+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2) modem state changed, 'registered' --> 'connecting' (reason: user-requested) 2014-07-21T16:16:17.197258+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2) modem state changed, 'connecting' --> 'connected' (reason: user-requested) 2014-07-21T16:16:17.197792+02:00 sandpuppy NetworkManager[963]: <warn> (ttyUSB2): failed to look up interface index 2014-07-21T16:16:17.198256+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) scheduled... 2014-07-21T16:16:17.198701+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) starting... 2014-07-21T16:16:17.216351+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: prepare -> config (reason 'none') [40 50 0] 2014-07-21T16:16:17.216866+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) successful. 2014-07-21T16:16:17.217392+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) scheduled. 2014-07-21T16:16:17.218061+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 2 of 5 (Device Configure) complete. 2014-07-21T16:16:17.218620+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) started... 2014-07-21T16:16:17.219016+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: config -> ip-config (reason 'none') [50 70 0] 2014-07-21T16:16:17.219581+02:00 sandpuppy NetworkManager[963]: <info> using modem-specified IP timeout: 20 seconds 2014-07-21T16:16:17.220212+02:00 sandpuppy NetworkManager[963]: <info> starting PPP connection 2014-07-21T16:16:17.221205+02:00 sandpuppy NetworkManager[963]: <info> pppd started with pid 3014 2014-07-21T16:16:17.221705+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... 2014-07-21T16:16:17.222148+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 3 of 5 (IP Configure Start) complete. 2014-07-21T16:16:17.222896+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv6 Configure Timeout) started... 2014-07-21T16:16:17.223911+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv6 Configure Timeout) complete. 2014-07-21T16:16:17.224339+02:00 sandpuppy NetworkManager[963]: <warn> pppd pid 3014 exited with error: pppd options error 2014-07-21T16:16:17.224923+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... 2014-07-21T16:16:17.225522+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv4 Configure Timeout) started... 2014-07-21T16:16:17.226128+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] 2014-07-21T16:16:17.227762+02:00 sandpuppy NetworkManager[963]: <warn> Activation (ttyUSB2) failed for connection 'A1/Telekom Austria - A1 Breitband' 2014-07-21T16:16:17.228595+02:00 sandpuppy NetworkManager[963]: <info> Activation (ttyUSB2) Stage 4 of 5 (IPv4 Configure Timeout) complete. 2014-07-21T16:16:17.229424+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): device state change: failed -> disconnected (reason 'none') [120 30 0] 2014-07-21T16:16:17.230159+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2): deactivating device (reason 'none') [0] 2014-07-21T16:16:17.231608+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2) modem state changed, 'connected' --> 'disconnecting' (reason: user-requested) 2014-07-21T16:16:19.248718+02:00 sandpuppy NetworkManager[963]: <info> (ttyUSB2) modem state changed, 'disconnecting' --> 'registered' (reason: user-requested) 2014-07-21T16:16:36.266449+02:00 sandpuppy NetworkManager[963]: get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed ---cut--- Any ideas? -- Thanks, //richard -- 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] Factory as a distro factory
by Felix Miata 22 Jul '14

22 Jul '14

As a rolling distro, I can't see Factory as the apropos name it was. It's now just an assembly plant, not a manufacturing plant, roughly equivalent to Fedora's post-branching TS builds. IMO, Tumbleweed, or something entirely different, ought to be the name applied going forward to the rolling release Factory. No longer will Factory be a good way to discover bugs, since ostensibly all but inconsequential or undiscoverable bugs have been squashed before acceptance of newer versions from BS into Factory. What the name "Factory" ought to be now is (a) recommended collection(s) of BS repos designed to do one of the things the old Factory did, enable user-testers to find the problems the builders missed or couldn't have found using the hardware at their disposal. Even without any name changing going forward, there still needs to be something describing a or several recommended BS repo collection(s) for those wishing to remain testers, at least a wiki page with a suitable name nicely describing what it's for, so people so desiring can continue to do everything they had been doing with Factory past (and still can with such as Cauldron, Rawhide or Sid). -- "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

10 19

[opensuse-factory] submitrequest about etckeeper (was: Do you know about the cause by which the zypper-etckeeper.py does not operate ?)
by 1xx 21 Jul '14

21 Jul '14

2014-06-25 9:13 GMT+09:00 1xx <itsango(a)gmail.com>: > 2014-06-22 8:18 GMT+09:00 1xx <itsango(a)gmail.com>: >> 2014-06-20 11:22 GMT+09:00 1xx <itsango(a)gmail.com>: >>> https://build.opensuse.org/package/show/home:Mitsutoshi:branches:utilities/… >>> >>> I am testing etckeeper 1.12 now, it seems to work normally. >>> >>> Are there those who want to test new etckeeper? >>> It can download from the following. >>> http://software.opensuse.org/download.html?project=home%3AMitsutoshi%3Abran… >> >> >> I submitrequested it. >> https://build.opensuse.org/request/show/238255 It was declined. So I changed comments (etckeeper,changes, etckeeper.spec, and etckeeper-zypp.patch). And I re-submited a request. https://build.opensuse.org/request/show/239404 Please review it and accept or decline it. -- 1xx <ItSANgo(a)gmail.com> <https://twitter.com/ItSANgo> Mitsutoshi NAKANO <bkbin005(a)rinku.zaq.ne.jp> <http://d.hatena.ne.jp/Itisango/> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 22

[opensuse-factory] Factory broken
by Stephan Kulow 21 Jul '14

21 Jul '14

Hi, There are various problems shown on https://openqa.opensuse.org/tests/overview?distri=opensuse&version=FTT The most prominent is the btrfs crash on i586 filed as https://bugzilla.novell.com/show_bug.cgi?id=887046 But there are various others - not affecting the staging prjs for some unclear reason. One reason for this is that kernel on i586 is less stable, but we have no resources to stage also i586. Another bug is seen at - the upgrade path is now broken for a while ;( https://openqa.opensuse.org/tests/11570/modules/upgrade_select/steps/5 So don't wonder why there are no factory updates... Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- 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] o:F/icu failure (Re: Reminder for openSUSE:Factory work)
by Jan Engelhardt 21 Jul '14

21 Jul '14

On Monday 2014-07-21 12:26, Stephan Kulow wrote: > >Dear openSUSE contributor, >Project X11:common:Factory > > icu fails for 27 days (time dependent failure): > http://s.kulow.org/bf-icu Hm. openSUSE:Factory/icu still contains 52.1. Has the LibreOffice team addressed their issues with the pending 53.1 (where there is a fix)? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

Re: [opensuse-factory] empty tty10
by Dale Ritchey 21 Jul '14

21 Jul '14

On 07/18/2014 08:20 AM, Dale Ritchey wrote: > > On 07/18/2014 04:37 AM, Felix Miata wrote: >> On 2014-07-18 09:35 (GMT+0200) Bruno Friedmann composed: >> >>> Felix Miata wrote: >> >>>> Anyone know why post-13.1 vtty10 is nothing but black instead of >>>> kernel >>>> messages, if it exists at all? The system I have currently booted >>>> to Factory >>>> won't let me get past vtty6 (in runlevel 3). Others I can get >>>> there, but it's >>>> empty, or I can get there only if in runlevel 5, where it's still >>>> only black. >> >>> don't know if factory has totally switched to journald but if it the >>> case >>> by defaut in >>> /etc/systemd/journald.conf >>> those 2 lines are commented >>> ForwardToConsole=yes >>> TTYPath=/dev/tty10 >> >>> uncomment them >> >> had only >> >> #ForwardToConsole=no >> >> With first splash=verbose noplymouth boot to multi-user.target with: >> >> ForwardToConsole=yes >> TTYPath=/dev/tty10 >> >> boot messages stalled at [41.64...] without producing a visible login >> prompt on tty1, but login prompts appeared on tty2-tty6. tty7-tty12 >> are unreachable. Login prompt on tty6 had this appended: >> >> [247.656605] systemd-logind[613]: Failed to start >> autovt(a)tty6.service: Unit autovt(a)tty6.service failed to load: File >> exists. >> >> On each return to tty6 after going to another an additional instance >> of that message appears on tty6. >> >> On finally logging in on tty3 @[515...], roughly 20 additional login >> and systemd messages appeared on lines between "Password:" and the >> shell's MOTD. While typing here, more messages on tty6 followed. >> Logging in on tty2 produced another splash of messages. > > /etc/systemd/journald.conf > line 28 uncomment and change to ForwardToConsole=yes > line 29 uncomment and change to line 29 uncomment and change toTTYPath=/dev/tty10 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 8

[opensuse-factory] New package: libressl
by Jan Engelhardt 21 Jul '14

21 Jul '14

>can you please introduce the package on factory ml? LibreSSL is a fork of OpenSSL which has been stripped of old, unused code and code for defunct/historic OSes. The plan is increased auditability and security. (You probably already heard in the news.) There is a conference video on LibreSSL at http://www.youtube.com/watch?v=GnBbhXBDmwU for interested parties. From that presentation, I also gather: - openssl implements its own meomry allocator which defeats valgrind's memory leack checker because that allocator never frees anything - new features added to libressl: ChaCha stream cipher, poly1305 (MAC) Packaging-wise, I find the style of libressl(-portable) to be a win over openssl. It is autotooled and needs just a quarter of the instructions found in openssl.spec. >I don't see any motivation why we need yet another ssl implementation There are certainly factors that would make a package unfit for inclusion, like unacceptable license, or overly trivial software, obvious trash software, or certain unmaintained software. LibreSSL does not fail at any of these basic checks. Other than that, I remember it such that openSUSE became open to all submissions and dropped the requirement that the package had to be useful _for the distribution_ (rather than the user). tl;dr: libressl makes a lot of people sleep better at night. ;) -- 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] Broken Fonts in system settings -> Fonts and Mozilla
by Freigeist 21 Jul '14

21 Jul '14

Hello Listmates, I recently installed/upgraded to factory on two machines. On machine #1 I did a new installation from DVD using snapshot 20140630. On machine #2 I had openSUSE 13.1 running, using Tumbleweed and did a zypper dup after enabling the factory repos. On both machines the fonts in system settings -> Fonts and in Mozilla are unreadable. Here is a screenshot: http://susepaste.org/51783997 I filed a bug report under: https://bugzilla.novell.com/show_bug.cgi?id=888061 Besides fixing the bug does anybody know a quick workaround for this? Thanks, Andreas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] gpg-offline issues
by Wolfgang Rosenauer 20 Jul '14

20 Jul '14

Hi, I've prepared a new package of enigmail and wanted to add gpg source verification. The package is in mozilla/enigmail currently but gpg verification disabled because it fails with an error I don't really understand. When I just use gpg to verify the signature everything is fine. When I use gpg-offline it shows an error. recommends to run --refresh but when I do that the error just stays the same. Could someone please have a look and check what's going wrong? I need to put that package into Factory pretty soon and would like to have the gpg check if possible. 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] Unable to add attachments to bugzilla
by Andrey Borzenkov 20 Jul '14

20 Jul '14

As requested: Software error: DBD::mysql::db do failed: Lock wait timeout exceeded; try restarting transaction [for Statement "INSERT INTO attachments (bug_id, creation_ts, modification_time, filename, description, mimetype, ispatch, isurl, isprivate, submitter_id) VALUES (?,?,?,?,?,?,?,?,?,?)"] at Bugzilla/Attachment.pm line 885 Bugzilla::Attachment::create('Bugzilla::Attachment', 1, 'Bugzilla::Bug=HASH(0x27b0d90)', 'Bugzilla::User=HASH(0x26e4340)', '2014-07-20 13:25:47', 'HASH(0x63c3f0)') called at /shared/bugzilla/docroot/attachment.cgi line 476 main::insert() called at /shared/bugzilla/docroot/attachment.cgi line 121 For help, please send mail to the webmaster (webmaster(a)novell.com), giving this error message and the time and date of the error. Happened at Sun Jul 20 13:27:58 UTC 2014 multiple times, for https://bugzilla.novell.com/show_bug.cgi?id=862403. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Package Request: Add bullet physics to openSUSE:Factory
by Simon 19 Jul '14

19 Jul '14

Hi All, I would like to request the addition of bullet physics http://bulletphysics.org/wordpress/ to openSUSE:Factory, it is currently developed in the games repo, https://build.opensuse.org/package/show/games/bullet Bullet physics is a real time physics simulation library, I am not currently the maintainer of bullet or anything in the games repo, the reason i wish to push bullet to factory is that the enlightenment foundation libraries (efl) http://www.enlightenment.org/ which i do maintain have a wrapper around bullet (ephysics), currently this is a optional dependency and is only really used in one game "escape from booty bay", (efbb) http://brunodilly.org/blog/escape-from-booty-bay/ In the future however there are plans to use this in the enlightenment window manager theme for desktop effects (think similar to compiz) and as such at some point upstream will be turning this into a mandatory requirement so i'm trying to be organised before then. If a existing maintainer is happy to push this to factory thats fine, otherwise if no one else volunteers i will be quite happy to do this, i've cc'd the last 3 people to make changes to the bullet packages. Cheers, Simon Lees ~~~ openSUSE maintainer for Enlightenment. -- 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] Grub?
by Thomas Taylor 18 Jul '14

18 Jul '14

During the initial installation of OS 13.2 (snapshot 20140630 x86_64) when choosing boot options legacy grub is not offered, only grub2. Yet legacy grub is offered as a software package option. Why is installation of legacy grub offered if it can't be used as the boot loader? Is it finally time that I'm forced to change boot loaders and to learn a new method? I like legacy grub as it is easy to modify menu.lst but grub.cnf appears to be much more complex. Thanks, Tom -- "To be free is not merely to cast off one's chains, but to live in a way that respects and enhances the freedom of others." - Nelson Mandela ^^ --... ...-- / -.- --. --... -.-. ..-. -.-. ^^^^ Tom Taylor KG7CFC openSUSE 13.1 (64-bit), Kernel 3.11.6-4-default, KDE 4.11.2, AMD Phenom X4 955, GeForce GTX 550 Ti (Nvidia 337.19) 16GB RAM -- 3x1.5TB sata2 -- 128GB-SSD FF 27.0, claws-mail 3.10.0 registered linux user 263467 -- 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] Installation question
by Thomas Taylor 18 Jul '14

18 Jul '14

I typically install new versions several times trying out various programs/features/settings in both real and virtual systems. I've noticed that starting with the 13.x series each install has slightly different results for some items (locations of a very few programs, clock settings. languages). None of the differences seem to change the operation of the system. Might this have something to do with changing to systemd or possibly a race condition during installation with a quad core system? I've previously used sysvinit only. Thanks, Tom -- "To be free is not merely to cast off one's chains, but to live in a way that respects and enhances the freedom of others." - Nelson Mandela ^^ --... ...-- / -.- --. --... -.-. ..-. -.-. ^^^^ Tom Taylor KG7CFC openSUSE 13.1 (64-bit), Kernel 3.11.6-4-default, KDE 4.11.2, AMD Phenom X4 955, GeForce GTX 550 Ti (Nvidia 337.19) 16GB RAM -- 3x1.5TB sata2 -- 128GB-SSD FF 27.0, claws-mail 3.10.0 registered linux user 263467 -- 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] empty tty10
by Felix Miata 18 Jul '14

18 Jul '14

Anyone know why post-13.1 vtty10 is nothing but black instead of kernel messages, if it exists at all? The system I have currently booted to Factory won't let me get past vtty6 (in runlevel 3). Others I can get there, but it's empty, or I can get there only if in runlevel 5, where it's still only black. -- "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

4 5