November 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Realtime Permission for Jack/Ardour3
by Benjamin 24 Nov '13

24 Nov '13

Hallo everybody! I have spent some time on googeling arounf and trying around to get Ardour3 running, but with no luck. The Error Ardour gives out is the following: [ERROR]: JACK: Cannot create thread res = 1 [ERROR]: JACK: Cannot use real-time scheduling (RR/5)(1: Die Operation ist nicht erlaubt) [ERROR]: JACK: JackClient::AcquireSelfRealTime error Actually this should be a common failure while starting jack, when the user does not have realtime permission, so I changed /etc/security/limits.conf and added the follwing: #@realtime - rtprio 99 #@realtime - memlock unlimited THen i created a group called realtime,to which i added me as a user. After that a rebooted. But still ARdour gives out exactly the same failure, so my question: How can i set realtime permission, so that i can use Audio-Software (Ardour3) and jack? My system: Opensuse 13.1. x86_64 Kernel: 3.11 i also started a discussion in, but so far no useful replies! https://community.ardour.org/node/7237?destination=node%2F7237 Thanks, Benjamin.

1 0

[opensuse] Trapping Ctl-Alt-Shift
by James Knott 23 Nov '13

23 Nov '13

Is there any way to trap and discard Ctl-Alt-Shift? I use Ctl-Shift to switch keyboard layouts and my KVM uses Ctl-Alt-Shift to change inputs. However, that also triggers a layout switch. Is it possible to map C-A-S to do nothing, rather than switch layouts? Running 12.3 & KDE4. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] ssh yast module
by Alex Angerhofer 23 Nov '13

23 Nov '13

Dear List, The other day I upgraded to 13.1 without much trouble. I am still missing the nvidia repository but that will probably come online sometime in the future. My question here is about the yast module for sshd. It has gone missing in opensuse 13.1. Is there any particular reason for that? I always found it convenient to set it up in yast. To get sshd started at boot I had to set it up in system services manager which appears to be a new module, or I haven't paid attention. Best regards, Alex. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

[opensuse] trouble starting privoxy
by Patrick Shanahan 23 Nov '13

23 Nov '13

Anyone running privoxy having a problem since upgrade to 13.1 ??? -- (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+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 13

[opensuse] a note on systemd systemctl syntax
by Istvan Gabor 23 Nov '13

23 Nov '13

Hello: It seems systemd is unstoppable. It gets into every linux distro sooner or later. Apart from that we have to learn it, find its syntax awkward, very awkward. What I mean: The syntax, if I know correctly is: systemctl action(enable/disbale/start/stop etc.) service-name.service I am using bash shell as, I guess, many of you too. In bash you can press upward cursor to get to the previous command you entered. You can edit that command by going back with the cursor. By pressing enter you apply the new (edited) command. Now, with the current systemd syntax this is very tedious. If I want to apply different operations I have to go back to the middle of the line to edit action. Same with service-name service. If I want to edit service name I have to go back a lot to change it. The logical sysntax, at least in my opinion, would be: systemctl service.service-name action Then it would be simpler to edit previous command lines. Practically this worked like this with initv boot scripts: /etc/init.d/service-name start/stop etc. Wasn't it easier an more logical and easier to use? What do you think? Istvan ps: Please do not ask what is my point. The answer: this syntax is a good current example of "ain't fix what's not broken". I am talking only about the command syntax, not systemd. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 24

[opensuse] 13.1 fails to boot with kernel 3.11.6-4
by Stephen Berman 22 Nov '13

22 Nov '13

Today I updated from 12.3 to 13.1 using the DVD from box but I cannot boot using the default 13.1 kernel. Here are the details: 12.3 was installed on /dev/sdb6. I cloned it to /dev/sdb7 as a backup and ran the update on /dev/sdb6. The update appeared to complete successfully, but on booting it immediately went to emergency mode. The log showed several failures: Failed to insert module 'autofs4' Failed to open /dev/autofs: No such file or directory Failed to initialize automounter FATAL: Could not load /lib/modules/3.11.6-4-desktop/modules.dep: No such file or directory as well as several mount failures with these messages: Dependency failed for Local File Systems mount process exited, code=exited status=21 The log also showed that the system root was mounted to /dev/sdb7 instead of /dev/sdb6. I don't understand why this happened, but it explains why /lib/modules/3.11.6-4-desktop/modules.dep could not be found, since that exists only on /dev/sdb6. But from the Grub2 menu I can select the cloned 12.3 on /dev/sdb7, and it boots fine (with kernel 3.7.10-1.16). And if I select, from the Advanced options section of the Grub2 entry for 13.1, kernel 3.7.10-1.16, which the update left installed on /dev/sdb6 (as well as adding the newer kernel), then I can boot 13.1 -- but, again, only with the 12.3 kernel. So why is /dev/sdb7 mounted as root when I try to boot the default 13.1 kernel, and what do I need to fix that and use the newer kernel? Thanks for any help. Steve Berman -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 12

[opensuse] gnome-color-manager requires PackageKit ???
by Patrick Shanahan 22 Nov '13

22 Nov '13

Why does gnome-color-manager require PackageKit ?? -- (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+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

Re: [opensuse] Ah, now we can install it?
by AP 22 Nov '13

22 Nov '13

On Fri, Nov 22, 2013 at 8:52 PM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > If you favor stability, give it a couple months. There is a lot of > testing, but sometimes a decision has to be made that affects multiple > packages and they simply aren't all available on release day. This > time the main culprit is bluetooth. Gnome and KDE got out of sync, > but they share the bottom of the bluetooth stack. > 13.1 was shipped with a broken KDE bluetooth stack. This was expected > weeks (or even months) ago due to schedule issues. Well, in this scenario, I must wait. But anyways, why I am least worried because 12.3 would be supported. > For smaller projects, they tend to ship based on new features being ready. > For distros (and the linux kernel) there are so many component pieces > that it makes better sense to set routine schedule. openSUSE is using > 8 months between releases. There was a slip of a couple months in > summer 2012. OH I see. > openSUSE supports 2 concurrent releases, with a 2-month overlap at > each transition. > Thus last month 12.2 and 12.3 were supported. > We are now in the 2-month transition to 13.1, so 12.2, 12.3 and 13.1 > will be supported for 2 months. > After that, 12.2 will be dropped. And it would dropped by the end of Jan'14. We would have 12.3 to be supported till Sep'14. > Separately there is the Evergreen team which picks releases to support > for 3 years. 11.4 is the current evergreen supported release. 13.1 > will be the next one, so if you want to stay on a release for up to 3 > years, 13.1 is a great choice. I forget when 11.4 evergreen support > drops, but I think it is next summer (6-9 months from now) > Major desktop updates like for KDE / Gnome are not done via the normal > updates channel. > Thus 2 options: > - routine core distro updates > - support updates via a add-on repo in OBS > openSUSE is currently doing both. There has been some discussion of pulling some of the packages out of core and just having them in add-on repos. Okay. But I heard that there is some difference between Evergreen and the regular openSUSE (which is not long supported), like there are some programs which are not upgraded but only the security fixes....Though I would stick with the 18 month's support openSUSE unless especially some reason(s) exist(s). Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Can't install 13.1 on Netfinity server
by James Knott 22 Nov '13

22 Nov '13

I've been trying to install opensusE 13.1 i586 on an IBM Netfinity server, but it fails with an error message: "Unable to create repository from URL 'cd:/?devices=/dev/sr0'. Details: [|] Valid metadata not found at specified URL History: - Can't hardlink/copy /var/adm/mount/AP_0x0uZ040/media.1/media to /var/cache/zypp/raw/cd-6e2e8d40v8pDTq - Can't provide /media.1/media" It doesn't make any difference whether I start with blank disks or previously formatted in 11.4. I can install 11.4 on this system. It has 4 146.8 GB SCSI drives in RAID & LVM. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 12

[opensuse] Ah, now we can install it?
by AP 22 Nov '13

22 Nov '13

Hello, First of all, I am happy that the launch of 13.1 has taken place. I have some queries related with the same. These are as follows: (i) Installation: Now, I know that I can install it right now. But I just want to confirm that I can go ahead with it? Because right now 12.3 is working very well and would be supported, and installing the latest one won't have anything unexpected...? (ii) The New Release: This is the general doubt. Every time the new release comes after a fixed interval of time. Just wanted to know if this cycle is a sort of fashion in free software market? Means, when many things can be patched from YaST, still the newer version come so early, so this is followed because it is in term and condition or this cycle can be made flexible also so that the newer releases can be delayed or the cycle be increased in time...? I know though, the versions like Tumbleweed are there. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1