September 2015 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Developing Leap 42.1 Info
by Douglas DeMaio 30 Sep '15

30 Sep '15

The release date for Leap 42.1 is approaching and to make this release is as successful as the last, we could sure use your help. There are several things we can do as a community to improve awareness of Leap both inside and outside of the Free and Open Source Software community. I kindly ask everyone involved with the openSUSE project to update the wiki in preparation for the release at https://en.opensuse.org/Portal:42.1. Our last release, 13.2, was very successful and it would be great if we can replicate that effort by updating the information for 42.1, so it looks similar to https://en.opensuse.org/Portal:13.2 Developers, packages maintainers and anyone else knowledgeable about what has changed in the new versions could add information to https://en.opensuse.org/openSUSE:Major_features42.1, which we can use to replace https://en.opensuse.org/Features on the day of the release. Screenshots are also important and anyone can do it! Just help replace the 13.2 screenshots on https://en.opensuse.org/Portal:42.1/Screenshots/1 page with Leap 42.1 screenshots. It will replace the https://en.opensuse.org/Screenshots page on Nov. 4 with the updated screenshots. Media - Please retweet, +1 or share all info related to the release of Leap 42.1. Test the Beta, RC1 and release and express your opinion about it. Let people know what you like about it or what could improve for Leap 42.2. Submit articles to open source media outlets, write blogs and comment articles related to openSUSE. Attend FOSS and Open Source events to help others learn about openSUSE. If you want to represent openSUSE at these events, contact me and I?ll see what marketing material I can send you. Have a lot of fun! Doug -- 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] OpenSUSE Leap 42.1 B1 - Warning: Digest verification failed for file 'glibc-* packages
by André Verwijs 30 Sep '15

30 Sep '15

Retrieving: glibc-info-2.19-4.1.noarch.rpm ..........................................................................................[done] Warning: Digest verification failed for file 'glibc-info-2.19-4.1.noarch.rpm' [/var/cache/zypp/packages/openSUSE-42.1-0/suse/noarch/glibc-info-2.19-4.1.noarch.rpm] expected c714674122c759228543b35129ea9c7bc9352280 but got 0459ddacb9edad8acfeaa3eba9b3a8fe8ef007f8 Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise. However if you made certain that the file with checksum '0459..' is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file. Unblock or discard? [0459/? shows all options] (discard): -- 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] plasma lockscreen / xdm authentication failure
by Stefan Quandt 30 Sep '15

30 Sep '15

I'm running tumbleweed and just updated ('zypper up') and after that could no longer unlock my plasma5 session. This already happened a few days ago after installing plasma5 packages in favor of the KDE4 desktop shell. I both cases it helped to follow instructions https://bugs.kde.org/show_bug.cgi?id=337470 The update today did set permissions of /etc/shadow to 700 with the effect that e.g. /usr/lib64/libexec/kcheckpass yields "Authentication failure". My /etc/sysconfig/security contains PERMISSION_SECURITY="easy local" So I could resolve this for my case (again) but I'am wondering how many users will be affected from this. -- 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] [solved] tumbleweed update 2015-09-24 unlock screensaver failed
by Wilhelm Boltz 30 Sep '15

30 Sep '15

Today I did an update on Tumbleweed on my laptop from 2015-08-31 to 2015-09-24. Since it has been impossible to unlock the screen saver ("Permissions on the password database may be too restrictive"). I found the solution (consistent I hope) considering this bug report¹ and executing the following command (as root): chmod 4755 /usr/lib64/libexec/kcheckpass This may be the resurrection of a well known bug and should be solved then. Greetings Willi ¹ <https://bugzilla.novell.com/show_bug.cgi?id=931296> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 13

[opensuse-factory] Wayland profile
by Tomáš Čech 30 Sep '15

30 Sep '15

Hi, I'm trying to package and integrate into openSUSE tiling window manager Orbment. As the configuration is passed through environment variables I'm looking for the united way how to start such session. It's not only configuration of one wayland session where I could simply create wrapper for and read the necessary things from that. But I'm looking also for the right spot where to run ssh-agent, gpg-agent and similar once for the session (so something similar to ~/.xinitrc). Is there some united way how to do that? Is there some file which is sourced/loaded during wayland session startup? Thanks, Tomas Cech Sleep_Walker

1 0

Re: [opensuse-factory] Leap packagelist still incomplete!
by Johannes Meixner 30 Sep '15

30 Sep '15

Hello, On Sep 28 18:45 Greg Freemyer wrote (excerpt): > On Mon, Sep 28, 2015 at 5:46 AM, Johannes Meixner <jsmeix(a)suse.de> wrote: ... >> (provided I understand correctly how Leap is meant). ... > The core of SLE is used and is meant to provide a level of stability > in the core typically reserved for enterprise use. ... > The majority (at least 75%) of the Leap packages will come > from factory and meet the traditional openSUSE end-user use case. I can no longer understand how Leap is meant. For example I think I noticed that Leap may get a newer kernel. If this is true, the kernel is not "core". Strange... https://en.wikipedia.org/wiki/Wolpertinger Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Identity crisis for Leap and Tumbleweed?
by Graham P Davis 30 Sep '15

30 Sep '15

Just been installing the latest TW and Leap from DVD. When the installation of software etc. kicked in, the slide show for Tumbleweed consistently said it was Leap 42.1 whilst Leap insisted it was openSUSE 13.2. Oops? ;-) -- Graham Davis, Bracknell, Berks. openSUSE 13.2 (64-bit); KDE 4.14.9; AMD Phenom II X2 550 Processor; Kernel: 4.2.0; Video: nVidia GeForce 210 (using nouveau driver); Sound: ATI SBx00 Azalia (Intel HDA) -- 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] New Tumbleweed snapshot 20150924 released!
by Andrei Dziahel 30 Sep '15

30 Sep '15

Hi list, TL; DR: latest snapshot basically broke nodejs for me. I am forced to report this bug here because boo replies with 404 on attempt to file it (it shows bug form on /enter_bug.cgi alright, but replies with 404 on post_bug.cgi when I press "Submit"). Steps to reproduce: * install nodejs v4.0.0 of latest snapshot and nodejs-npm/npm (both fit well) * point * run npm install --global babel (any package name works actually) Expected: named package is installed Instead: npm (well, nodejs) terminates with SIGSEGV. Note: nodejs interpreters installed with nvm (https://github.com/creationix/nvm) are not affected by this issue. Backtrace: $ gdb /usr/bin/node usr.bin.node.core […skip copyrights…] warning: core file may not match specified executable file. [New LWP 1680] [New LWP 1688] [New LWP 1692] [New LWP 1691] [New LWP 1687] [New LWP 1681] [New LWP 1694] [New LWP 1693] [New LWP 1690] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `npm '. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000000000 in ?? () >>> bt #0 0x0000000000000000 in ?? () #1 0x0000000000bd6996 in node::crypto::Hash::HashUpdate(v8::FunctionCallbackInfo<v8::Value> const&) () #2 0x00000000006a006b in v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) () #3 0x00000000006cb432 in v8::internal::MaybeHandle<v8::internal::Object> v8::internal::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::(anonymous namespace)::BuiltinArguments<(v8::internal::BuiltinExtraArguments)1>&) [clone .constprop.66] () #4 0x00000000006cb88e in v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) () #5 0x00002250cdb060bb in ?? () #6 0x0000098de41db889 in ?? () #7 0x00002250cdb06001 in ?? () #8 0x00007ffd76342d80 in ?? () #9 0x00007ffd76342de0 in ?? () #10 0x00002250cdcfdbe9 in ?? () #11 0x0000098de41db889 in ?? () #12 0x0000201d8da65759 in ?? () #13 0x00002d4fb6522369 in ?? () #14 0x0000246228746689 in ?? () #15 0x0000098de41db889 in ?? () #16 0x0000098de41e70e9 in ?? () #17 0x00002d4fb6530a51 in ?? () #18 0x00007ffd76342e20 in ?? () #19 0x00002250cdb19494 in ?? () #20 0x0000201d8da65759 in ?? () #21 0x00002d4fb6522369 in ?? () #22 0x0000246228746629 in ?? () #23 0x0000000100000000 in ?? () #24 0x0000098de41e70e9 in ?? () #25 0x0000000a00000000 in ?? () #26 0x00007ffd76342e70 in ?? () #27 0x00002250cdcfd59c in ?? () #28 0x00002d4fb6522369 in ?? () #29 0x0000246228746629 in ?? () #30 0x0000098de41e70e9 in ?? () #31 0x0000000000000000 in ?? () >>> If it's my fault that bug can't be properly reported, I kindly ask you to copy&paste this report to BOO for me. Thank you in advance. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

Re: [opensuse-factory] URGENT: ACTION NEEDED: LAST CHANCE - Make sure the packages you need are in openSUSE Leap
by stakanov＠freenet.de 29 Sep '15

29 Sep '15

p, li { white-space: pre-wrap; }In data lunedì 28 settembre 2015 15:01:08, Richard Brown ha scritto: > Got your attention? T Yes Richard, and there are at least two packages that I would like to have in leap (actually one that I would effectively need(!) in leap, that is blender) But: I am honest, I did not understand about how to do that, when you say: "To submit a package from Tumbleweed to Leap run... a) run where? b) maybe I am not even eligible to do that? c) I would have a few question for some of these (to anybody): e.g. kchmviewer - does calibre have the capacity to show these files? If not this would IMO still be useful. kmymoney: is this left out because not maintained any more? I know quite some people who use it on a regular basis. Or is it supposed to be obsoleted by another package (e.g. scrooge?). milou: I do not know if this works again? I found it interesting and useful but then it was broken, so I discontinued using it. Is this still maintained? If anybody has some answers on these, feel free to tell me. Thanks. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 9

RE: [opensuse-factory] [solved] tumbleweed update 2015-09-24 unlock screensaver failed
by Howard Guo 29 Sep '15

29 Sep '15

Morning . If you set file system permissions to paranoid instead of easy (default), a package upgrade will sometimes trigger the change on kcheckpass permission . I have also noticed the same behaviour with sudo . under paranoid permission setting, sudo does not have suid. I was one locked out of root access after sudo was upgraded and paranoid permission sets it to 0700. Regards, Howard ---- Wilhelm Boltz wrote ---- >Today I did an update on Tumbleweed on my laptop from 2015-08-31 to >2015-09-24. > >Since it has been impossible to unlock the screen saver >("Permissions on the password database may be too restrictive"). > >I found the solution (consistent I hope) considering this bug >report¹ and executing the following command (as root): > > chmod 4755 /usr/lib64/libexec/kcheckpass > >This may be the resurrection of a well known bug and should be >solved then. > >Greetings >Willi > >¹ <https://bugzilla.novell.com/show_bug.cgi?id=931296> >-- >To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org >To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > >

2 1