March 2011 - openSUSE Users - openSUSE Mailing Lists

[opensuse] openSUSE Weekly News 165 is out!
by Sascha Manns 06 Mar '11

06 Mar '11

We are pleased to announce: Issue 165 of openSUSE Weekly News is out! [0] For a list of available translations see this page: http://en.opensuse.org/openSUSE:Weekly_news_translations [0] http://news.opensuse.org/?p=7246 (in HTML with Bento Theme) [0] http://saigkill.homelinux.net/pub/OWN/HTML/OWN-165.html Weekly News in HTML (Susebooks Theme) [0] http://saigkill.homelinux.net/index.php/download/download-weekly- news/file/10-opensuse-weekly-news-165-pdf-version (in PDF) -- Sincerely yours Sascha Manns open-slx.com openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com -- Sincerely Yours Sascha Manns open-slx Community & Support Agent openSUSE Membership Comitee openSUSE Marketing Team Blog: http://saigkill.wordpress.com German Community Portal: http://community.open-slx.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] openSUSE 11.4 in Amazon EC2
by James Tan 06 Mar '11

06 Mar '11

Hi all, You can now run openSUSE 11.4 in Amazon EC2, with this set of public AMIs (Amazon Machine Images): http://blog.susestudio.com/2011/03/opensuse-114-for-amazon-ec2.html Cheers, James T.

1 0

[opensuse] What were they thinking... ? "Ontologies necessary for the Nepomuk semantic desktop"
by David C. Rankin 05 Mar '11

05 Mar '11

Curious about a strange package name with an interesting definition prompted a bit of investigation: 20:48 zephyr:~> rpm -qa | grep ontologies shared-desktop-ontologies-0.3-1.6.noarch shared-desktop-ontologies-devel-0.3-1.6.noarch 20:49 zephyr:~> rpm -qi shared-desktop-ontologies Name : shared-desktop-ontologies Relocations: (not relocatable) Version : 0.3 Vendor: openSUSE Release : 1.6 Build Date: Mon 05 Jul 2010 05:10:38 PM CDT <snip> Summary : Shared Desktop Ontologies Description : Open Semantic Collaboration Architecture Foundation (OSCAF) ontologies and reference code development. This project is used by maintainers from open source projects to maintain standards for the interoperability of desktop and web applications. A bit of further looking disclosed: "Ontologies necessary for the Nepomuk semantic desktop" I'm all for having a rich and diverse vocabulary, but reaching so far back into the Greek vernacular... I just have to ask, "What were they thinking...?" Think about it - "Open Semantic Collaboration Architecture Foundation (OSCAF) ontologies and reference code development." -- That's a mouthful. What happened to simplicity? I have enough trouble remembering: 'at', 'grep', 'diff', 'sed', 'awk' and 'patch', much less "Open Semantic Collaboration Architecture Foundation (OSCAF) ontologies and reference code development." I take my hat off to the originator. That is one bit of creative linguistics -- second to none ;p -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

14 33

[opensuse] errors after update to 11.2
by Mike 05 Mar '11

05 Mar '11

I used zypper dup to upgrade from 11.1 to 11.2 After restarting it had another huge bunch of packages to update after restarting again I get this message when updater applet runs User is not permitted: org.freedesktop.packagekit.system-update -- Collector of vintage computers http://www.ncf.ca/~ba600 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 9

[opensuse] Screen saver and blanking
by C. Brouerius van Nidek 05 Mar '11

05 Mar '11

Having Googled for my problem and studied the wiki's etc. I am still dumbfounded that I am not able to get the screensaver running on my desktop for a period of time that I decide. In the Personal Settings (Configure Desktop) I did not find a possibility. Found somewhere via google that the file ~/.kde4/share/config/kscreensaverrc could be used to change the timing. The content of this file read as follows: [ScreenSaver] PlasmaEnabled=true Saver=krandom.desktop Timeout=420 The original timeout is 7 minutes so I just put two zeros at its end and expected to see a very long running sreensaver. No change. Seems to have to prolong the blanking of the screen. The screen time of the monitor is set to off. Where would I find a config file for the screen blanking? -- Linux User 183145 using LXDE on a Pentium IV , powered by openSUSE 11.3 (i586) Kernel: 2.6.38-rc6-16-desktop LXDE WM & KDE Development Platform: 4.6.00 (4.6.0) 17:19pm up 16:59, 3 users, load average: 5.62, 3.41, 2.29 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] YaST2 crash
by Patrick Shanahan 05 Mar '11

05 Mar '11

I am getting a crash w/YaST2 -> Software Management YaST got signal 11 at YCP file XML.ycp:3 /sbin/yast2: line 454: 15573 Segmentation fault $ybindir/y2base /$module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS openSUSE 11.2 x86_64 yast2-core-2.18.19-2.3.x86_64 yast2-2.18.25-2.5.x86_64 -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] IPv6, 11.3, YaST & maybe routers
by Dave Howorth 04 Mar '11

04 Mar '11

OK, so I've had a problem with my home machine that I think started with 11.2 and certainly is present after I upgraded to 11.3. The problem is a delay of a few seconds (5?) whenever I access a web site that I haven't just previously accessed. It's mainly noticeable as a delay in loading pages in Firefox but also occurs with other programs (e.g. wget). My working hypothesis has always been that this is some DNS issue probably causing a timeout, and my guess was that it's somehow related to IPv6. But I know nothing about IPv6 and not a lot about modern DNS and the delays weren't hugely annoying so I haven't investigated. But yesterday I had an epiphany. I clicked on a link to a forum how-to[1], that led me to another[2], that led me to a bugzilla[3] and an opensuse-kernel thread[4]. So last night I conducted an experiment and discovered how to make my problem go away. Hurray! The reason for this mail is that I now think there's a *bug in YaST* but I'm not confident that I really understand the issues properly. I know there are people here who understand these issues and won't bite my head off if I've got the wrong end of the stick. So I thought I'd try to clarify my understanding before deciding on the appropriate action. YaST is involved because I used it to check that IPv6 was *not* causing my problem. And it falsely told me that IPv6 was disabled. Specifically, YaST/Network Settings/Global Options/Enable IPV6 showed an empty checkbox. That is, it said IPv6 is disabled. But now I have learned an independent way to check: # cat /proc/sys/net/ipv6/conf/all/disable_ipv6 0 That is, IPv6 is NOT disabled in reality. Further checking indicated that it was not disabled in /etc/sysctl.conf either[5]. So I used the command-line to disable it and my problem was immediately cured: # echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6 I also uncommented the relevant line in /etc/sysctl, which I hope will make the change persist across a reboot. So, now to the areas where I'd like clarification if anybody can help: (1) Are those two changes all I need to do/ the best way to disable IPv6? (2) Is the original problem actually indicative of some more fundamental misconfiguration either on my PC, my router or in my ISP's systems? (3) My reading of the YaST situation is: (a) the opensuse kernels were changed so that ipv6 is always built-in rather than loaded as a module (b) there was a period when YaST still tried to use module control to disable ipv6, which didn't work, but that problem in YaST was subsequently fixed and YaST should now be able to change the ipv6 state properly (c) BUT it is incorrectly reporting the state for some reason. Evidently it isn't looking in /proc or /etc/sysctl so I believe it must be trusting some other source of information that is no longer accurate. (d) Perhaps the inaccuracy occurs because of some flaw in the upgrade logic? If I'm right in my understanding, then I guess YaST should get it's status information from somewhere different and I should raise a bug against it? Cheers, Dave [1]<http://forums.opensuse.org/english/get-technical-help-here/how-faq-forums/u…> [2]<http://forums.opensuse.org/new-user-how-faq-read-only/unreviewed-how-faq/43…> [3]<https://bugzilla.novell.com/show_bug.cgi?id=539869> [4]<http://lists.opensuse.org/opensuse-kernel/2010-11/msg00071.html> [5] /etc/sysctl.conf # Disable response to broadcasts. # You don't want yourself becoming a Smurf amplifier. net.ipv4.icmp_echo_ignore_broadcasts = 1 # enable route verification on all interfaces net.ipv4.conf.all.rp_filter = 1 # disable IPv6 completely #net.ipv6.conf.all.disable_ipv6 = 1 # enable IPv6 forwarding #net.ipv6.conf.all.forwarding = 1 # increase the number of possible inotify(7) watches fs.inotify.max_user_watches = 65536 # avoid deleting secondary IPs on deleting the primary IP net.ipv4.conf.default.promote_secondaries = 1 net.ipv4.conf.all.promote_secondaries = 1 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 3

[opensuse] Looking for noveau kernel driver on onenSUSE 11.2
by Roger Oberholtzer 04 Mar '11

04 Mar '11

I have an up-to-date openSUSE 11.2 system. Last week's update of the nvidia driver is causing me problems with frequent freezes (max cpu time) and rather frequent server crashes. Until I sort this out, I would like to use the nouveau driver. I have the X11 driver, and can make sure the nouveau driver is not blacklisted. However, I don't seem to find the nouveau.ko driver. X fails claiming it could not be found. I expected this to be in the kernel-xxx package, as are the other drivers, and as it is on openSUSE 11.3. But alas the nouveau.ko kernel driver is not there. My installed kernel is: kernel-desktop-2.6.31.14-0.6.1.i586 My nouveau X server is: xorg-x11-driver-video-nouveau-0.0.16_20110115_b795ca6-22.1.i586 Shouldn't the nouveau.ko kernel driver be in one of these? Although not my real question, the troublesome nvidia drivers are: x11-video-nvidiaG02-256.53-16.1.i586 nvidia-gfxG02-kmp-desktop-256.53_2.6.31.5_0.1-15.1.i586 Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] non-parallel boot, or?
by Roger Oberholtzer 04 Mar '11

04 Mar '11

I am trying to sort out a delay that happens when I am booting openSUSE 11.2 in some systems. The delay seems to be when it is dealing with the rtc. However, I am not sure that is really where the delay is. I am guessing that the default boot does things in parallel when possible. Or, at least, things that can be done in the background are done there. Is this correct? If so, perhaps some other thing is delayed (20 minutes...) and I see this when the rtc stuff is done. My question is, is there a boot option (via grub options, for example) that makes the boot happen in order, one thing at a time? The 20 minute delay I see sounds like the usual network thing. I do not think it is. But I cannot tell. I cannot think anything related to the rtc during boot can cause a delay. I asked this a bit back and got the impression that nothing there could delay so long. As the problem persists (only on a certain class of hardware...) I need to see how best to identify the culprit. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] writing udev rules
by Per Jessen 04 Mar '11

04 Mar '11

I'm new to writing udev rules, so although this works as expected, I'd like a double check: SUBSYSTEM=="block", ENV{ID_PATH}=="ip-192.168.2.151:3260-iscsi-iqn.2011-03.net.local:5269f78b-84d9-4de2-8093-b6dd0678d694-lun-1", OWNER="per", GROUP="users" Is this sufficient/accurate/appropriate for setting the ownership of /dev/sdx (which the /dev/disk/by-path/path symlinks to) to per.users? thanks -- Per Jessen, Zürich (0.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0