July 2012 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Help: Python GTK/Gobject problem with OpenSuSE 11.4
by Rodney Baker 02 Jul '12

02 Jul '12

Hi all. I'm have an ongoing problem with apps that use python-gtk under 11.4 / KDE 4.6.5 failing to run. The error message is as follows: Traceback (most recent call last): File "/usr/local/bin/chirpw", line 25, in <module> import gtk File "/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 40, in <module> from gtk import _gtk ImportError: could not import gobject (could not find _PyGObject_API object) Googling the last line has turned up several related threads in various mailing list archives (including oS factory) without any of them ever actually hinting at a solution. I can reproduce the problem at the command line using: python -c 'import gtk' Does anyone here have any clues on this? Thanks in advance, Rodney. -- ========================================================================== Rodney Baker VK5ZTV rodney.baker(a)iinet.net.au ========================================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Wifi broken after update: 12.1
by Odd Ball 02 Jul '12

02 Jul '12

Hi, I just installed 12.1 on a quadcore eeepc seashell series. While installing the option wpa(1,2)psk tkip was not present, so had to use a rope. When testing the network, both rope and wifi did not work. After login in the networkmanager did succeed in finding network, and accepting my passphrase, so it worked. I wifi-d the update: truckload of packages, after that wifi broken. Does not scan or see or find the network. The rope does work. *I forgot: what package did i have to update again to get it working again?* Oh and the security is tremendously overdone with network setting: twice rootpasword wallet, also twice, but still no connection. Maybe the attention got to the wrong stuff? As my network is already protected, why do i need root password, and kdewallet to get acces to these settings? I think it is very user-unfriendly this way... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] where should I put self-signed certificates for Apache 2 in OpenSuse 12.1
by Ted Byers 02 Jul '12

02 Jul '12

I tried Google, and found no consistency. I see directions, admittedly for older versions of Suse Linux, that claim enabling SLL on apache, using a2enmod ssl would create directories in certain places, and having executed the above command, the directories I was told to expect are not there. I found one set of instructions that were almost identical for Ubuntu 12.04 and Suse Linux and they both seemed to work. The httpd server restarted fine, but because these particular instructions said nothing about certificates, I did nothing to create new, self-signed certificates. Consequently, I got an error on both Suse and Ubuntu vis: SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long). A colleague pointed me to instructions he'd followed on Ubuntu, which did involve creating new self-signed certificates and configuring a virtual SSL host. Following those solved the problem on Ubuntu, but I can't use them on Suse as the programs don't appear to be available on Suse (such as apt-get). Since Apache 2 behaved in the same way on both systems, the problem was probably due to the certificates on both. That said, I figure that since I have openssl installed on my Suse VM, and I know how to use it from having created self-signed certificates for Apache2 on Windows, I ought to be able to use it to create them on Suse, but the problem remains were to put them so that Apache2 will find them, and what configuration file to edit to tell Apache2 where they are. While the same series of steps for enabling SSL on Ubuntu and Suse seemed to work the same, the result is a very different suite of directories between the two, and in very different places. Even the suite of configuration files is different. What gets confusing is that the different sets of instructions find by googling, even restricting the search to documents pertaining to Suse Linux, they differ WRT what directories ought to exist where. A perfect example. I do a lot of CGI programming. On Windows, in the root directory, I have an apache2 directory, and everything pertaining to Apache is in it, or a sub-directory thereof. Not so with any Linux I have looked at so far. On both Suse and Ubuntu, I find an apache2 directory in /etc/, but on Ubuntu, the cgi-bin is /usr/lib/cgi-bin while on Suse Linux, it is /srv/www/cgi-bin. On both VMs, I have found a bunch of 'certificate' directories all over the place, but which application installed and uses them I have no idea. I certainly do not want to be messing with them at least until I know why they exist and what uses them. I reasoned that a quick HOWTO document ought to address this, so I opened httpd.conf on the Suse box, and found the following: # Quickstart guide: # http://en.opensuse.org/Apache_Quickstart_HOWTO Alas, when I went to it, it was EMPTY! So much for being able to read useful documentation. The page actually directed me to search for the page and here is what I got from that: ==========Search results================================================================= tagline: From openSUSE Top of Form . Content pages . Multimedia . Help and Project pages . Everything . Advanced Bottom of Form There were no results matching the query. Create the page "All:Apache Quickstart HOWTO~" on this wiki! Retrieved from "http://en.opensuse.org/Special:Search/all:Apache_Quickstart_HOWTO%7E" ============================================================================ ============ BTW: I used yast to install all the servers I routinely work with, expecting it to put them in a relatively standard location (on the assumption the default locations would be reasonably secure), but finding stuff is proving to be a challenge. And I don't want to be putting stuff in the wrong places lest I compromise the security of the machines (i.e. I don't want to get used to having stuff in the wrong places lest, when I deploy my stuff to a production server, I compromise that machine). Might I suggest someone connected to opensuse.org start prodding people who know to put together some quickstart HOWTO documents for a suite of 'tasks', such as setting up a LAMP machine (perhaps with an extended version dealing with setting up SVN and Redmine on a LAMP server), improving the security of a system using snort and/or apparmour (but that I mean either individually or a combination of the two), setting up Wordpress on a LAMP machine, or osCommerce (or competing online commerce product), just to name a few I would be interested in reading (and if you want someone to test a procedure, I'd be happy to set up a virgin VM with a vanilla install of either Gnome or KDE, and apply the procedures described, and provide feedback to the authors of such documents. I'd start writing them up, if I had the knowledge, but I don't have that knowledge, yet. In the meantime, a little wisdom WRT where to put the self-signed certificates I can make using openssl and what configuration file in /etc.apache2 to edit in order to tell apache about them, would be greatly appreciated. Cheers Ted -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] osc commit command error
by flash yan 02 Jul '12

02 Jul '12

Hi all, When I run "osc commit",I get the following problem: Server returned an error: HTTP Error 401: basic auth failed How to solve this problem? Thanks. Flash Yan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Suse 11.4 Kernel update
by Smartysmart34 01 Jul '12

01 Jul '12

Hi all, just wanted to let you know: on my machine the last kernel patch from last week did not remove the old kernel from the grub-menu. So that patch doubled the grub-entries. This is kind of odd, because sometimes (most of the times) the update removes old versions, and sometimes it doesn't. Regards, Martin -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] problems building perl 5.14.2 or 5.16.0 using RPMBUILD, build from tar or perlbrew (a cpan util)
by Linda Walsh 01 Jul '12

01 Jul '12

I run into the same problems building 5.16.0 whether I run from perlbrew or rpmbuild. I'm sorta wondering how perl is built for the distribution if I am having such a hard time rebuilding it or building it on a suse system. This points to a problem I mentioned a few years back with the build system. If something only builds on a remote build system -- you end up with a proprietary build system that can't easily be reproduced to rebuild products. The whole idea of open source was to be able to fix things in it that were broken by building your own. If I can't do that -- easily -- on my own system, I'm beginning to wonder how well that fits the definition of 'open source'. Right now, I have 2 main failure modes depending on how I build. If I build from a fresh login -- a default config: sh Configure -de make make test That doesn't work -- Configure gets confused and drops in 'null' for programs (like make, rm, and maybe a few others). If I build from env -i (shell-dash/sh/bash) -- Configure will build, but the C compiler (cc or gcc) is broken: make `sh cflags "optimize='-O2'" perlmini.o` -DPERL_IS_MINIPERL -DPERL_EXTERNAL_GLOB perlmini.c CCCMD = gcc -DPERL_CORE -c -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -std=c89 -O2 -Wall -ansi -W -Wextra -Wdeclaration-after-statement -Wendif-labels -Wc++-compat -Wwrite-strings gcc: error trying to exec 'cc1': execvp: No such file or directory cat >lin.c #include <stdio.h> main() { printf ("Hello World\n"); } $ gcc lin.c gcc: error trying to exec 'cc1': execvp: No such file or directory $ set IFS=' ' LINENO='' OLDPWD='/home/tools/perl' OPTIND='1' PATH='/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' PPID='27167' PS1='$ ' PS2='> ' PS4='+ ' PWD='/home/tools/perl/perl-5.16.0' _='lin.c' My path looks normal -- so what's the problem -- why can't I run the C compiler? Who knows why a normal login run of configure ends up with this: End of configuration questions. Stripping down executable paths... Creating config.sh... ./Configure: line 22748: -f: command not found ./Configure: line 23838: -f: command not found ./Configure: line 23844: -f: command not found Doing variable substitutions on .SH files... Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Not re-extracting config.h Extracting makedepend (with variable substitutions) Extracting Makefile (with variable substitutions) ./Makefile.SH: line 1600: -f: command not found Extracting myconfig (with variable substitutions) Extracting pod/Makefile (with variable substitutions) Extracting Policy.sh (with variable substitutions) ./Policy_sh.SH: line 147: -d: command not found ./Policy_sh.SH: line 174: -d: command not found Extracting runtests (with variable substitutions) Extracting utils/Makefile (with variable substitutions) Extracting x2p/cflags (with variable substitutions) Extracting x2p/Makefile (with variable substitutions) Run depend now? [y] ./Configure: line 23924: depend: command not found ./Configure: line 23937: -f: command not found ./Configure: line 23947: -f: command not found ./Configure: line 23953: -f: command not found ./Configure: line 23954: -rf: command not found I asked on the perl list, and they are confounded. FWIW,,, zypper ve, shows all dependencies are verified -- that my system is 'coherent'... So won't this build? (Have had problems rebuilding samba as well, so I don't think it is just perl). Building 5.14.2 --- fails in a different but consistent way -- one of the files processed when building a ".xs" file from a .c file puts a bogus "#line file" line in that is missing the line number.... Ideas? Time to get a new distro?....(that would suck!).... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 19