October 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] ERROR: /run/user/0/ does not exist
by lynn 08 Oct '13

08 Oct '13

Hi 13.1 beta 1 When trying to get Kerberos tickets, the directory does not exist e.g. as root: kinit Administrator kinit: Credential cache directory /run/user/0/krb5cc does not exist while getting default ccache If I now create the directory: /run/user/0 and now kinit, it works fine and I get a ticket. This is different behavior from 12.3, where the ticket cache was stored in /tmp Can I: 1. Get back to the 12.3 behaviour? 2. Adjust something to create the /run/user/0 directory if root attempts a kinit? Thanks, Lynn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 14

[opensuse-factory] GNOME 3.10 Software application vs. YaST?
by Andrey Borzenkov 08 Oct '13

08 Oct '13

According to 3.10 release notes: "GNOME 3.10 includes a brand new application for finding and installing applications, called Software. It provides an integrated place to do all your software related tasks, like browsing, installing and removing applications, and viewing and installing software updates." Is it supposed to be replacement for YOU and other software related tasks? -- 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] What is NET-Build0725?
by lynn 07 Oct '13

07 Oct '13

Hi A bit of confusion about the 13.1 beta. We're not quite sure what we have. On 2 October we installed an iso called: openSUSE-Factory-NET-Build0725-i586.iso after following the NET install link, here: http://software.opensuse.org/developer/en and hoping to get the 13.1 beta. We did a zypper dup today and it pulled in over 100 upgrades. We elected to go ahead with the dup. 1. Does our original download correspond to the 13.1 beta 1? 2. If we keep doing zypper dup, will we end up with beta 2 and then the rc's? 3. If (2) is yes, then do we eventually end up with the released version of 13.1? 4. If I send a bugzilla, what do version we put? NET-Build0725, 13.1 beta 1 or perhaps 13.1 beta 1 duped <date> I get the feeling that unless we all stick with the actual 13.1 beta 1 then any bug would be almost impossible to reproduce as we'd all be starting from a different point. Thanks, L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

Re: [opensuse-factory] Missing /usr/lib/udev/rules.d/80-btrfs.rules causes mkinitrd errors when upgrading to kernel 3.11.1-29
by Edward Reiss 07 Oct '13

07 Oct '13

So apparently btrfsprogs was updated, and over wrote the change I made to /lib/mkinitrd/setup/11-btrfs.sh, throwing up the same error as before. The "old" fix was to edit the file above by pointing it to 64-btrfs.rules. But that is obviously unstable, as a re-install or update to btrfsprogs will over write that file--my bad. So the new fix is this: sudo ln -s /usr/lib/udev/rules.d/64-btrfs.rules /usr/lib/udev/rules.d/80-btrfs.rule After doing this, I ran: sudo zypper in -f udev-195-13.45.1 without any errors. This adds a link to 64-btrfs.rules, so any script which calls 80-btrfs.rules will instead be pointed to 64-btrfs.rules. This is "better" than replacing the 80-btrfs.rules file or editing /lib/mkinitrd/setup/11-btrfs.sh in my opinion, because as 64-brtfs.rules is updated, so will the link be updated. And if 80-btrfs.rules ever returns, the link will be over written. But since 80-btrfs.rules is no longer in the btrfsprogs package, the link is in effect an "unsupported" fix. Can someone please fix /lib/mkinitrd/setup/11-btrfs.sh on a package level? -- Edward Reiss ebreiss(a)gmail.com Quis custidiet ipsos custodes? -- 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] What is the purpose of pulse-audio???
by Juan Erbes 07 Oct '13

07 Oct '13

Yesterday trying to record the contents of some cassettes, with audacity via a usb-audio device player (detected fine, without aditional drivers),, I lost almost two hours trying to solve the problem that after few seconds of started, the recording stopped all the times. The solution was to disable pulse-audio, and from there,appeared three times more mixer controls, and the recording worked fine. I'm using Opensuse 13.1 beta 1. -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- 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] login keyring prompt annoyance
by lynn 06 Oct '13

06 Oct '13

13.1 beta 1 Hi Each time certain users login, they get prompted: 'Enter password to unlock your login keyring' These users windows domain users and are Kerberos authorised via sssd. I've tried removing the keyring entry in: pam.d/common-auth but still the prompt appears. How can I get rid of it? Thanks, L x -- 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] nothing provides libpng12 needed by lsb
by Ilya Chernykh 05 Oct '13

05 Oct '13

Is it planned to be corrected? -- 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] No network devices in "Bottle"
by Jogchum Reitsma 04 Oct '13

04 Oct '13

I committed bug https://bugzilla.novell.com/show_bug.cgi?id=8444146. After upgrading to 13.1B1 (from the previous 13.1 version) there are no netwerk devices created. Jogchum Reitsma -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

Re: [opensuse-factory] Documentation for patching kernel
by Upscope 04 Oct '13

04 Oct '13

On Monday, September 30, 2013 01:28:59 PM Roman Bysh wrote: > On Mon 30 Sep 2013 01:25:30 PM EDT, Upscope wrote: > > On Sunday, September 29, 2013 05:46:30 PM Thomas Taylor wrote: > >> On Sun, 29 Sep 2013 08:58:54 -0700 > >> > >> Upscope <upscope(a)nwi.net> wrote: > >>> On Sunday, September 29, 2013 01:45:56 PM Sid Boyce wrote: > >>>> On 29/09/13 07:13, Thomas Taylor wrote: > >>>>> It has been many years since I had to patch a kernel and need to > >>>>> have a location for the requisite documentation. > >>>>> > >>>>> I have obtained "kernel_v3.11.patch" but in searching the SUSE > >>>>> documentation have not found the official procedure to apply > >>>>> this > >>>>> patch. Would someone please supply an URL or location where > >>>>> that > >>>>> patch application is provided? > >>>>> > >>>>> Thanks, Tom > >>>> > >>>> Are you sure that patch is a kernel patch? > >>>> The title seems to suggest it's a patch for the NVidia > >>>> proprietary > >>>> drivers and it would depend on which driver you need to patch. > >>>> > >>>> For the 325.15 driver package. > >>>> "sh NVIDIA-Linux-x86_64-325.15.run --apply-patch > >>>> kernel_3.11.patch" > >>>> > >>>> There are a couple of patches with that name, this is the > >>>> shortest > >>>> of > >>>> them. # less kernel_v3.11.patch > >>>> --- a/kernel/nv-linux.h > >>>> +++ b/kernel/nv-linux.h > >>>> @@ -957,7 +957,11 @@ static inline int nv_execute_on_all_cpus > >>>> > >>>> #endif > >>>> > >>>> #if !defined(NV_VMWARE) > >>>> > >>>> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 11, 0) > >>>> +#define NV_NUM_PHYSPAGES get_num_physpages() > >>>> +#else > >>>> > >>>> #define NV_NUM_PHYSPAGES num_physpages > >>>> > >>>> +#endif > >>>> > >>>> #define NV_GET_CURRENT_PROCESS() current->tgid > >>>> #define NV_IN_ATOMIC() in_atomic() > >>>> #define NV_LOCAL_BH_DISABLE() local_bh_disable() > >>>> > >>>> 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 > >>> > >>> Not sure if you can answer this. The patch I got for 325.15 has > >>> the > >>> following: > >>> CODE: > >>> ------------ > >>> nvidia-3.11.patch > >>> Index: NVIDIA-Linux-x86_64-325.15/kernel/nv-linux.h > > > > =================================================================== > > > >>> --- NVIDIA-Linux-x86_64-325.15.orig/kernel/nv-linux.h > >>> +++ NVIDIA-Linux-x86_64-325.15/kernel/nv-linux.h > >>> @@ -958,7 +958,11 @@ static inline int nv_execute_on_all_cpus > >>> > >>> #endif > >>> > >>> #if !defined(NV_VMWARE) > >>> > >>> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 11, 0) > >>> +#define NV_NUM_PHYSPAGES get_num_physpages() > >>> +#else > >>> > >>> #define NV_NUM_PHYSPAGES num_physpages > >>> > >>> +#endif > >>> > >>> #define NV_GET_CURRENT_PROCESS() current->tgid > >>> #define NV_IN_ATOMIC() in_atomic() > >>> #define NV_LOCAL_BH_DISABLE() local_bh_disable() > >>> > >>> ---------- > >>> Is the line starting with @@ correct in the your version or mine? > >>> My version works with 3.11.0 but not later3.11 versions. > >>> > >>> Thanks Russ > >>> Sorry first time I hit wrong button and sent this direct to Sid. > >> > >> Thanks for all the replies. Yes, it is a patch for the Nvidia run > >> file and not the kernel. My mistake. > >> > >> The version of the patch file is different from both of yours: > >> > >> My version: > >> 0f "kernel-v3.11.patch > >> > >> --- a/kernel/nv-linux.h > >> +++ b/kernel/nv-linux.h > >> @@ -957,7 +957,11 @@ static inline int nv_execute_on_all_cpus > >> > >> #endif > >> > >> #if !defined(NV_VMWARE) > >> > >> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 11, 0) > >> +#define NV_NUM_PHYSPAGES get_num_physpages() > >> +#else > >> > >> #define NV_NUM_PHYSPAGES num_physpages > >> > >> +#endif > >> > >> #define NV_GET_CURRENT_PROCESS() current->tgid > >> #define NV_IN_ATOMIC() in_atomic() > >> #define NV_LOCAL_BH_DISABLE() local_bh_disable() > >> > >> --- a/kernel/nv-drm.c > >> +++ b/kernel/nv-drm.c > >> @@ -106,7 +106,11 @@ static const struct file_operations nv_d > >> > >> .unlocked_ioctl = drm_ioctl, > >> .mmap = drm_gem_mmap, > >> .poll = drm_poll, > >> > >> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 12, 0) > >> +// .fasync = drm_fasync, > >> +#else > >> > >> .fasync = drm_fasync, > >> > >> +#endif > >> > >> .read = drm_read, > >> .llseek = noop_llseek, > >> > >> }; > >> > >> @@ -202,12 +206,16 @@ RM_STATUS NV_API_CALL nv_alloc_os_descri > >> > >> memset(&nv_obj->base, 0, sizeof(nv_obj->base)); > >> nv_obj->pages = pages; > >> > >> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 12, 0) > >> + drm_gem_private_object_init(nvl->drm, &nv_obj->base, size); > >> +#else > >> > >> ret = drm_gem_private_object_init(nvl->drm, &nv_obj->base, > >> size); > >> > >> if (ret) > >> > >> { > >> > >> status = RM_ERR_OPERATING_SYSTEM; > >> goto done; > >> > >> } > >> > >> +#endif > >> > >> ret = drm_gem_handle_create(file_priv, &nv_obj->base, > >> handle); > >> if (ret) > >> > >> --- a/kernel/nv.c > >> +++ b/kernel/nv.c > >> @@ -16,8 +16,12 @@ > >> > >> #include "rmil.h" > >> > >> #if defined(MODULE_LICENSE) > >> > >> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 12, 0) > >> +MODULE_LICENSE("GPL"); > >> +#else > >> > >> MODULE_LICENSE("NVIDIA"); > >> #endif > >> > >> +#endif > >> > >> #if defined(MODULE_INFO) > >> MODULE_INFO(supported, "external"); > >> #endif > >> > >> Not sure if you trimmed your listings or are there really different > >> versions floating around with the same title? > >> > >> Anyway, when II attempted to use either method suggested they both > >> failed with mainly "file not found" errors. > >> > >> Thanks, Tom > >> > >> -- > >> The foolish man seeks happiness in the distance. The wise man grows > >> it under his feet. > >> > >> - James Oppenheim > >> > >> ^^ --... ...-- / -.- --. --... -.-. ..-. -.-. > >> > >> ^^^^ > >> Tom Taylor - retired penguin - KG7CFC > >> AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata2 > >> openSUSE 13.1_M4-x86_64 > >> KDE 4.11.00, FF 22.0, claws-mail 3.9.2 > >> 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 > > > > Tom: I will try your much larger patch. The patch I used patch: > > CODE: > > --------- > > NVIDIA-Linux-x86_64-325.15/kernel/nv-linux.h > > _______ > > which is extracted from the NVIDIA-Linux-x86_64-325.15.run file. it > > works fine on 3.11.0. I will try your more complete patch on 3.11. > > latest update of the 12.3 kernel. If that works and I get my 13.1 > > Beta 1 to work I'll try it there. its on a seperate disk.. > > > > Will post result. > > > > Thanks for the quick response. > > Russ > > Are you using Tumbleweed kernels. What's the exact kernel? > > -- > Cheers! > > Roman This is the one that is working on 12.3 now, No Tumbleweed installed: CODE: ----------- uname -a Linux linux-rpl7 3.11.0-2.g0a1c41f-desktop #1 SMP PREEMPT Thu Sep 5 10:20:59 UTC 2013 (0a1c41f) x86_64 x86_64 x86_64 GNU/Linux _______ Others installed are from: http://download.opensuse.org/repositories/Kernel:/stable/standard/ There is an update waiting to download now: 3.11.1-3.1.gfeffbf9 (3.11.2-1.1.g4c1fc5a) I have two other 3.11.1-3 and 3.11.1-2 which I will uninstall. Thanks for your continuing input. Russ -- openSUSE 12.3(Linux 3.11.0-2.g0a1c41f-desktop)|KDE 4.11.1 |Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS (NVIDIA-Linux-x86_64-325.15 Patched) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

Re: [opensuse-factory] BlueZ 5
by Dominique Leuenberger a.k.a. Dimstar 04 Oct '13

04 Oct '13

Quoting Alin Marin Elena <alinm.elena(a)gmail.com>: > Hi Dominique, > > I am testing the thing in kde... ok... the mouse part as I have a bluetooth > one... > still not working. > I am using Raymond's packages which I suspect are not divergent form your > test bed. I don't think 'openobex' has anything to do with the mouse :) So this package should not do any difference. Can you pair the mouse using hcitool to verify if you see an 'underlying' issue on the BT stack as opposed to use the GUI tools? you schould be able to statr cluetoothctl (which is a 'shell' tool interacting with the stack): bluetoothctl [bluetooth]# list Controller <cmac> BlueZ 5.5 [default] [bluetooth]# select <cmac> [bluetooth]# power on [bluetooth]# scan on /// enable scanning mode on your mouse [bluetooth]# devices Device <mmac> Name: Bluetooth Mouse [bluetooth]# trust <mmac> [bluetooth]# pairable on [bluetooth]# pair <mmac> [bluetooth]# connect <mmac> That should confirm that the BT stack itself works as expected and would hint at anything GUI related 'not doing the right thing'. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4