July 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] python/Linux 3 incompatibilities
by todd rme 25 Jul '11

25 Jul '11

It looks like a number of Linux-specific python modules are not being built with Linux 3. There is a fix for the 2.7 branch available, but I don't know if it will be making it into the version that openSUSE will be shipping with openSUSE 12.1. If not, I would strongly consider including them, since breaking Linux python interfaces seems like a pretty serious problem. The problem also exists with python 3.x, so it would probably need to be included there as well. Here is the link to the comment in the bug report including the fixes: http://www.gossamer-threads.com/lists/python/bugs/931878#931878 -Todd -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] Why does flash fail
by Donn Washburn 25 Jul '11

25 Jul '11

Why is it that Firefox will not see a flash document. In 11.4 it worked correctly and in 12.1 it fails This is a 64bit machine and I have tried openSuSE flash in /usr/lib64/browser-plugin and it never has worked here. So I have downloaded a flash plugin that works like crazy as "root" but not as a "user". My guess is it is a permission issue. Has anyone fixed this issue. Well at this point I have replaced many things thought off as possible defective software like flash and firefox as tests. Made sure perrmissions and chmod was allowing it to work. Problem is nothing has changed it still is a permission problem as proven by the root user is working and all users are not able to see any flash type files. The browser comes up and all you see is a black small screen with no image. I have even completely tarred up and removed all /usr/lib64/browser-plugins only leaving libflashplayer.so with root.root and 755. Nothing seems to change the image. This is a recent 12.1 M2 The libflashplayer.so (64bit) version is the same one that works for another openSuSE user. -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Skype:n5xwbg BMWMOA #:4146 Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Booting 12.1 M3 succeeds only with nomodeset
by Jogchum Reitsma 24 Jul '11

24 Jul '11

Hi, I upgraded 12.1 M2 to M3 with Yast2. Kernel is now 3.0.0-rc7-2-desktop Booting it succeeds only using bootparameter nomodeset, otherwise a blank screen is the result. M2 booted OK, as does 11.4. Graphics hardware is a GeForce 8600 GT. I entered bug 707148 for this one. regards, Jogchum Reitsma -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 9

Re: [opensuse-factory] Booting 12.1 M3 succeeds only with nomodeset
by Jogchum Reitsma 24 Jul '11

24 Jul '11

Op 24-07-11 17:27, Donn Washburn schreef: > On 07/24/2011 08:39 AM, Jogchum Reitsma wrote: >> Hi, >> >> I upgraded 12.1 M2 to M3 with Yast2. Kernel is now 3.0.0-rc7-2-desktop >> >> Booting it succeeds only using bootparameter nomodeset, otherwise a >> blank screen is the result. >> >> M2 booted OK, as does 11.4. >> >> Graphics hardware is a GeForce 8600 GT. >> >> I entered bug 707148 for this one. >> >> regards, Jogchum Reitsma >> > Try booting up in Failsafe. I had the same problem with a NV card and > the Default, Desktop and Vanilla kernels from openSuSE > I did (of course, I would almost say :-)), and gradually deleted all the parameters from Failsafe, until I could nail it down to "nomodeset". regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] Factory 12.1 : trouble with pam_apparmor
by Bruno Friedmann 23 Jul '11

23 Jul '11

I log lot's of Jul 17 21:33:42 localhost su: pam_apparmor(su-l:session): Unknown error occurred changing to postgres hat: Operation not permitted Jul 17 21:34:08 localhost login[3497]: pam_apparmor(login:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:36:00 localhost login[4656]: pam_apparmor(login:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:37:56 localhost login[4884]: pam_apparmor(login:session): Unknown error occurred changing to ioda hat: Opération non permise Jul 17 21:41:35 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:41:50 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:42:18 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:42:35 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:42:50 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:43:39 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:44:00 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:44:15 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:44:18 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:44:30 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:44:44 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:44:55 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:44:55 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:46:47 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:47:23 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:48:17 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:48:59 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:49:15 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:49:21 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:49:58 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:50:03 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:50:10 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:50:17 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 17 21:52:27 localhost login[3499]: pam_apparmor(login:session): Unknown error occurred changing to ioda hat: Opération non permise Jul 17 21:54:09 localhost kdm: :0[6271]: pam_apparmor(xdm:session): Unknown error occurred changing to ioda hat: Operation not permitted Jul 18 08:14:08 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 18 08:14:43 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 18 08:14:47 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 18 08:15:00 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 18 08:17:33 localhost su: pam_apparmor(su-l:session): Unknown error occurred changing to root hat: Opération non permise Jul 18 08:20:54 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Opération non permise Jul 18 08:25:17 localhost su: pam_apparmor(su-l:session): Unknown error occurred changing to root hat: Opération non permise Jul 18 08:26:13 localhost su: pam_apparmor(su-l:session): Unknown error occurred changing to root hat: Opération non permise Jul 18 08:48:32 localhost su: pam_apparmor(su-l:session): Unknown error occurred changing to root hat: Opération non permise Opération non permise = Operation non permitted When I've tried the new F5 -> systemd boot I just get a console and when I try to login I just get also this message and cannot boot. Anybody see that too ? Disabling apparmor seems to help in that case, but should be considered as a bad idea no ? ps : proper systemd trace and log will follow -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 4

[opensuse-factory] Milestone 3 install testing
by Robert Schweikert 22 Jul '11

22 Jul '11

Some observations: Put the ISO file onto a USB stick via dd and tested install on a Dell Mini 10. - Network cards not detected during install (bug filed) ~ neither the Realtek Ethernet card nor the Broadcom wireless card were picked up - GDM does not work when trying to log in as "Other" (bug filed) - Install procedure drops out of YaST and puts me into some kind of "secondary" mode where I have to select the device to install from and specify the location of the sources. Not sure whet to do with this one. I suppose it should be a bug but it is hard to explain what's going on and I have no time to reproduce the steps to give better explanation, sorry. - Xfce doesn't show the panel, discussed with maintainer Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Milestone3
by Stephan Kulow 22 Jul '11

22 Jul '11

Hi, It was close, but I published Milestone3 now. It's the first with kernel 3.0, so celebrate :) Greetings, Stephan -- Sent from openSUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 18

[opensuse-factory] Boot Log
by Steven Sroka 22 Jul '11

22 Jul '11

Is there a "boot log" available after each boot up of openSUSE? I know there are a lot of components/scripts that run during boot time so a unified log is probably a pipe dream, but is there anything similar? I got an error message during first boot up of 12.1 M3, but I couldn't read what was wrong, so I'm trying to find out and then report it. Steven Sroka -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 4

[opensuse-factory] Mesa 7.11 RC1 released : where to submit ?
by Vincent Lejeune 21 Jul '11

21 Jul '11

Hi, Today is Mesa 7.11 first release candidate released. I packaged it, however I don't know where to submit it. I highly doubt that X11:XOrg is the right repository, because it contains only stable versions. However OpenSUSE:Factory seems to branch its X11 related package from it... I would like Mesa 7.11 RC1 to appear for next Milestone, as Mesa 7.11 is a major milestone of Mesa project. Lots of performance improvements and bug fixes over 7.10 are expected ; on the other hand, it might break things (as usual when there are big changes) If it can ship early in OpenSUSE developpement, more bugs could be reported upstream before final relase and won't have to wait for a minor revision to be fixed. Vincent -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 9

[opensuse-factory] Tumbleweed user reports with Kernel:HEAD 3.0 rc7 "laptop-mode: Unhandled kernel version: 3.0" (possible Factory 12.1 HAL dependency to)
by Rob Davies 20 Jul '11

20 Jul '11

There's a forum post giving error - http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta… The Tumbleweed uers, tried kernel 3.0 because of bugs seen with the stable kernel series syncing notebook to Windows server. Bugzilla entry expected. I haven't found a reference to laptop-mode-tools since 3.0 announced, last change by Tue 07 Dec 2010 12:00:00 GMT coolo(a)novell.com - prereq init script haldaemon This may be another unnoticed HAL dependency to. I think this probably will be reportable in bugzilla, but I don't have laptop Factory install, & the Tumbleweed user is obviously using a pre-release kernel, so thought a quick heads up best first, before committing "bureaucracy". Regards Rob -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2