September 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Tumbleweed issue with latest updates (Power Management)
by Carl Fletcher 08 Sep '13

08 Sep '13

Please see this thread https://forums.opensuse.org/english/get-technical-help-here/applications/49… ---------------------- Or the content is: I upgraded to day to KDE 4.11.1 from KDE 4.11.0. Also, Kernel 3.11 was installed. After the upgrade, I receive the following error at the top of my screen after login: Code: KDE Power Management System could not be initialized. The backend reported the following error: No valid Power Management backend plugins are available. A new installation might solve this problem. Please check your system configuration. So I went to System Settings>>Power Management and the pane on the right is greyed out and there is a message: Code: Power Management configuration module could not be loaded. The Power Management Service appears not to be running. This can be solved by starting or scheduling it inside "Startup and Shutdown" Added: So I go to System Settings>>Startup and Shutdown>>Service Manager and it states that the service is running. SO I stop and start the service and I receive the original message. I also booted in the 3.10.25 kernel and the problem persists. I created a new user and logged into KDE and the problem persists. I ran ps -ef | grep upower and here is the output: Code: root 1247 1 0 10:14 ? 00:00:00 /usr/lib/upower/upowerd I ran /user/lib/upower/upowerd since it is runable by a normal user. I received the followingoutput: Code: (upowerd:3843): UPower-WARNING **: Failed to acquire org.freedesktop.UPower: Connection ":1.122" is not allowed to own the service "org.freedesktop.UPower" due to security policies in the configuration file (upowerd:3843): UPower-WARNING **: Could not acquire name; bailing out Any ideas? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 6

[opensuse-factory] Kernel 3-11-0
by Basil Chupin 08 Sep '13

08 Sep '13

The (latest, released last week) nVidia driver 319.49 will not compile with the just-released kernel 3-11-0. I was under the impression that this problem was already known about for quite some time and already fixed. Is there a patch, please, to overcome this hassle? BC -- Using openSUSE 12.3, KDE 4.11.1 & kernel 3.10.10-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 34

[opensuse-factory] A major regression in the new version of Mesa.
by Marek Paśnikowski 07 Sep '13

07 Sep '13

I have resigned from using the 13.1 milestones because of this bug. Initially I had thought that it is one of those random breakages which could happen in the untested software and linger around even after fix has been done. But no. Right now I have a Tumbleweed with some additional repositories neatly organized by priority. When I wanted to try out the OpenSUSE 12.3 X11:XOrg repo version of mesa drivers (mesa 9.2) some of my games and a wine program stopped executing properly. The games behaviour is varied (stuck in a window mode with the first frame frozen, no window at all, transparent-frozen window). The wine program just crashes halfway through the loading procedure. I want to help hunt this regression down, but have no idea what tools to choose and how to use them... Any ideas, where to start? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] wicked
by Hans Witvliet 07 Sep '13

07 Sep '13

Hi, Couple of days ago i was at a presentation of Matthias Eckermann. He was giving us a glimp of the near future of suse. One of the things was using wicked as an alternative method of managing network-related-hardware. afaicr, it is something Olaf Kirch came up with, several years ago, and besides Olaf, it looks like (on github) Marius Tomaschewski is the main code-contributor. As little or near nothing docu can be found about "wicked", anybody around here who has been experimenting with the code? It's potential could be very cool indeed hans -- 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] howto push a pattern in factory for openvas ??
by johann Luce 07 Sep '13

07 Sep '13

hi all is in the title thanks for your answers regards jluce -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 5

[opensuse-factory] Project build does not start
by Andrey Borzenkov 06 Sep '13

06 Sep '13

I branched new project but somehow build does not start. As far as I can tell build is enabled in repository properties. Anything I missed? home:arvidjaar:branches:server:mail/mailman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Heads up on mdadm 3.3 - risk of unbootable system
by Luca Beltrame 05 Sep '13

05 Sep '13

Hello, just to prevent people from having an unbootable system like I did: it seems that the recent update of mdadm to 3.3 no longer scans metadata at boot if you use FakeRAID from Intel (IMSM or Intel Matrix Storage Manager), therefore the RAID is not assembled and the root device is not found (drops to emergency shell). I found this the hard way when my RAID 1 set was not assembled and the system could not boot. In this case checking /proc/mdstat only shows the metadata device (like /dev/md/imsm0) and not the RAID: md127 : inactive sda[1](S) sdb[0](S) 5928 blocks super external:imsm A workaround is to manually scan the metadata and assemble in the emergency shell: $ mdadm -I /dev/<metadata_device> [on my system it's /dev/md127; creates the RAID device node] $ mdadm --assemble --scan [partitions are also scanned and device nodes generated] Afterwards boot resumes once the emergency shell is quit, as / can be mounted. This behavior does not occur at all with mdadm 3.2 so I would suggest to lock it in place if you use it (I did). I filed https://bugzilla.novell.com/838777 just in case. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- 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] Dependency missing in lastest 12.3 kernel update
by Upscope 05 Sep '13

05 Sep '13

Current kernel: 3.10.10-1.g8038aea-desktop YaST shows up date to: 3.11.0-1.1.g16dd1ca update for kernel-syms says" nothing provides: kernel-zen-dev 3.11.0-1.1.g16dd1ca". Is this because the repo (http://download.opensuse.org/repositories/Kernel:/stable/standard/) has not finished building or is it a bug I should report? Thanks Russ -- openSUSE 12.3(Linux 3.10.10-1.g8038aea-desktop)|KDE 4.11.00 |Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS (NVIDIA-Linux-x86_64-325.15) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] can someone update mariadb in factory to one that works.
by doiggl＠velocitynet.com.au 05 Sep '13

05 Sep '13

Hello, can someone update mariadb in factory to one that works. -Thanks Glenn Tests I did so far: fail[1] using factory pass[2] using rpms from http://ftp5.gwdg.de/pub/opensuse/repositories/server:/database/openSUSE_Fac… [1] -using factory version [failed] # rpm -qa | grep -i mariadb |sort mariadb-5.5.32-3.1.x86_64 mariadb-client-5.5.32-3.1.x86_64 mariadb-errormessages-5.5.32-3.1.x86_64 # /bin/systemctl start mysql.service returned 1 (unspecified error): # /bin/systemctl start mysql.service Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details. # # systemctl status mysql.service mysql.service - LSB: Start the MySQL database server Loaded: loaded (/etc/init.d/mysql) Active: failed (Result: exit-code) since Fri 2013-09-06 11:09:21 EST; 2min 13s ago Process: 3730 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE) Sep 06 11:08:51 test.site mysql[3730]: [72B blob data] Sep 06 11:08:51 test.site mysql[3730]: Fatal error in defaults handling. Program aborted Sep 06 11:08:51 test.site mysql[3730]: [52B blob data] Sep 06 11:08:51 test.site mysql[3730]: Fatal error in defaults handling. Program aborted Sep 06 11:09:21 test.site mysql[3730]: Starting service MySQL warning: /var/run/mysql/mysql.sock didn't appear within 30 seconds Sep 06 11:09:21 test.site mysql[3730]: chmod: cannot access '/var/run/mysql/mysqld.pid': No such file or directory Sep 06 11:09:21 test.site mysql[3730]: ..failed Sep 06 11:09:21 test.site systemd[1]: mysql.service: control process exited, code=exited status=1 Sep 06 11:09:21 test.site systemd[1]: Failed to start LSB: Start the MySQL database server. Sep 06 11:09:21 test.site systemd[1]: Unit mysql.service entered failed state. #### [2] # mariadb worked[passed] #sources used: http://ftp5.gwdg.de/pub/opensuse/repositories/server:/database/openSUSE_Fac… # rpm -qa | grep -i mariadb |sort mariadb-5.5.32-137.2.x86_64 mariadb-client-5.5.32-137.2.x86_64 mariadb-errormessages-5.5.32-137.2.x86_64 # /bin/systemctl start mysql.service returned 0 (success): # /bin/systemctl start mysql.service test:~ # systemctl status mysql.service mysql.service - LSB: Start the MySQL database server Loaded: loaded (/etc/init.d/mysql) Active: active (running) since Fri 2013-09-06 20:16:20 EST; 32s ago Process: 12988 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS) CGroup: /system.slice/mysql.service ├─13450 /bin/sh /usr/bin/mysqld_safe --mysqld=mysqld --user=mysql --pid-file=/var/run/mysql/mysqld.pid --socket=/var/run/mysql/mysql.sock --datadir=/var/lib/mysql └─13664 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/lib/mysql/test.site.err --pid-file=/var/run/mysql/mysqld.pid --socket... Sep 06 20:16:18 test.site mysql[12988]: Phase 1/3: Fixing table and database names Sep 06 20:16:18 test.site mysql[12988]: Phase 2/3: Checking and upgrading tables Sep 06 20:16:18 test.site mysql[12988]: Processing databases Sep 06 20:16:18 test.site mysql[12988]: information_schema Sep 06 20:16:18 test.site mysql[12988]: mysql Sep 06 20:16:18 test.site mysql[12988]: test Sep 06 20:16:18 test.site mysql[12988]: Phase 3/3: Running 'mysql_fix_privilege_tables'... Sep 06 20:16:18 test.site mysql[12988]: OK Sep 06 20:16:20 test.site mysql[12988]: Starting service MySQL ..done Sep 06 20:16:20 test.site systemd[1]: Started LSB: Start the MySQL database server # systemctl status mysql.service mysql.service - LSB: Start the MySQL database server Loaded: loaded (/etc/init.d/mysql) Active: active (running) since Fri 2013-09-06 20:16:20 EST; 14min ago Process: 12988 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS) CGroup: /system.slice/mysql.service ├─13450 /bin/sh /usr/bin/mysqld_safe --mysqld=mysqld --user=mysql --pid-file=/var/run/mysql/mysqld.pid --socket=/var/run/mysql/mysql.sock --datadir=/var/lib/mysql └─13664 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/lib/mysql/test.site.err --pid-file=/var/run/mysql/mysqld.pid --socket... Sep 06 20:16:18 test.site mysql[12988]: Phase 1/3: Fixing table and database names Sep 06 20:16:18 test.site mysql[12988]: Phase 2/3: Checking and upgrading tables Sep 06 20:16:18 test.site mysql[12988]: Processing databases Sep 06 20:16:18 test.site mysql[12988]: information_schema Sep 06 20:16:18 test.site mysql[12988]: mysql Sep 06 20:16:18 test.site mysql[12988]: test Sep 06 20:16:18 test.site mysql[12988]: Phase 3/3: Running 'mysql_fix_privilege_tables'... Sep 06 20:16:18 test.site mysql[12988]: OK Sep 06 20:16:20 test.site mysql[12988]: Starting service MySQL ..done Sep 06 20:16:20 test.site systemd[1]: Started LSB: Start the MySQL database server. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Freeze is coming...
by Jos Poortvliet 05 Sep '13

05 Sep '13

A gentle reminder: it's time to get your code inside! http://news.opensuse.org/?p=16740 Hugs, Jos

1 0