October 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Super Computing conference 13 in Denver
by Robert Schweikert 24 Oct '13

24 Oct '13

Sorry for the cross post, need to reach as large an audience as possible. SUSE is a sponsor at SC13 and we have a 10x20 booth with a mini theater to give presentations. The team managing the SUSE presence and the event would like to have an openSUSE presence in the booth :) . In the past many questions about openSUSE were asked and it would be great to have a community member present to handle this. There is also an opportunity, for whomever goes, to give a 5 to 15 minute presentation about openSUSE. SC13 takes place November 18-21 in Denver Colorado, i.e. right after SUSECon and the openSUSE Summit. This is not retsricted to 1 person, if we have a different person for each day that's fine as well. Unfortunately, there is no money in the TSP fund as we used it all up for the Summit for this quarter ;) . Thus, if you are "local" to Denver or willing to pick up your own travel costs and willing to represent openSUSE at SC13 in Denver please speak up. We do have a number of passes to the Exhibit, thus entry into the event is "free". This has just come to my attention and thus the timing is a bit tight, sorry. Whomever is interested to jump in please speak up and let me know. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- 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] major features - closing today
by Jos Poortvliet 24 Oct '13

24 Oct '13

Hi, Tomorrow I'm going to start creating a list of top features of openSUSE 13.1 for the announcement. This is based on the wiki page: https://en.opensuse.org/openSUSE:Major_features If you have done anything worth mentioning to our users, please put it on that page! I would rather not miss major features/changes in the announcement... Beginning of next week I will move that page to https://en.opensuse.org/Features_13.1 and add some screenshots. We still need a lot of help creating screenshots, please put them here: https://en.opensuse.org/Screenshots_13.1 Thanks and hugs, J

1 0

[opensuse-factory] EFI system partition subdir registry
by Vincent Untz 24 Oct '13

24 Oct '13

Hi, The openSUSE board will most likely register an openSUSE-specific directory in the EFI system partition subdir registry (thanks to Jörg Wiegleb for pushing for this): http://www.uefi.org/registry AFAIK, right now, we use EFI/opensuse. Do we want to register this or instead the real case (EFI/openSUSE), assuming that we'd do the change in our packages? Note that many entries in the registry have mixed case (RedHat, VMware, etc.) Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] Question about the nv video driver on 13.1
by Larry Finger 23 Oct '13

23 Oct '13

Is anyone using the nv (xf86-video-nv) 2D accelerated video driver on 13.1-RC1? I use it for my laptop as nouveau fails for my graphics adapter, and I change kernels too often to mess around with the proprietary module. If you use this combination, I would appreciate you running a test. 1. Install package fltk-devel. 2. Enter the command 'fluid'. On the resulting screen, press the "File" menu item 3 times. That will toggle the menu item on/off/on. Can you now read the menu text, or is the resulting box empty? The latter is what I see. Everything was OK with 12.3, and it works OK with the frame buffer driver, but the max resolution is wrong. I would like to know if this is a bug on only my system. or if others are affected. Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] X11:Cinnamon is active again!
by Marguerite Su 23 Oct '13

23 Oct '13

Hi, everyone, I feel honored to broadcast this exciting news! Yesterday with the help of Jerzy, I got maintainership for X11:Cinnamon:*. So we can keep going now. For now, this project is left behind. Upstream is 2.0.2 and we're still 1.6.7. I see many home projects have higher versions of Cinnamon: http://software.opensuse.org/package/cinnamon There's even latest 2.0.2 out there. So I call people to submit your packaging work to X11:Cinnamon:Factory freely, I'll wait you there. And I need a few experts to act as repository maintainer with me. So we can cherry-pick packages from home projects (not just linking or copying, we have to merge changelogs so we will not override other people's credits) My plan is: 1. cleanup work. remove 12.1 tagets becasue it's EOLed. and considering remove GNOME34 tagets (don't know if it's possible, open to discussion here) 2. add new targets 12.3, 13.1 Tumbleweed. (maybe a new X11:Cinnamon:GNOME38 or something to absorb Cinnamon 1.8, also open to discussion) 3. copy new packages from home:cyberorg:cinnamon because it has latest versions and fix possible packaging warnings/bugs if there're. 4. cherry-pick packages from the same project and merge changelogs. 5. solid testing. After we finished the update job. welcome to test if your old annoying bugs are still there in newer versions, and we'll find a way to eliminate them. 6. find as many guy interested as possible to keep this project going and hope one day we can make it 13.2 or 13.3 So now: 1. Everyone interested in this project (a must) and have a home repository (so we can see if you're qualified) can apply maintainership against: X11:Cinnamon It's the project we keep permissions. If accepted, you can deal with all X11:Cinnamon:* sub-projects. For now there's a problem that if no one is added to X11:Cinnamon:Factory, we won't have any notifications if there're submit requests against it. As a workaround I added myself maintainer there. I want a bugowner for this project, because my daily-use DE is actually KDE. I myself personally prefer those who have already been repository maintainers to apply, because you have already known how this game plays and how important working with upstream is. And those who have strong packaging skills and know how to use mailing lists. Because at this stage we just need underlying works. After a few weeks, I welcome every daily Cinnamon users who have passion to apply some permissions, in that way this project will not be inactive any more just because we shift or turn our head to other projects (eg, I personally feel more responsible to keep M17N going...because without that, I can't even input anything in openSUSE) But also, my idea is open to discussion here. 2. Everyone who already have some Cinnamon bits inside your home, please merge the old changelog from X11:Cinnamon:Factory if there already been a package there (copy and keep items in correct timestamp, easy) and submit, or just submit if it's a new package. Greetings Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] [13.1 RC1] XFCE bad policy when battery is low.
by Carlos E. R. 23 Oct '13

23 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Testing the "Xfce Power manager", on a laptop. Select "On battery" on the left panel, to choose actions. When the battery power is critical, the drop list contains: "Nothing, Suspend, Shutdown, Ask". However, if you login as root into xfce, you also can "Hibernate". This is wrong. If the battery is _critical_, it can happen that the battery runs out during suspend, so it is normal and valid to choose "hibernation". However, a plain user can not choose that action, and I suspect that this is intentional. :-/ How can I tell XFCE to list "hibernate" as a valid action when I'm a plain user? Why are the security team scared that we hibernate our laptops, but not that we power them off? Because I suspect it is their decission. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJmgbQACgkQtTMYHG2NR9WPYACgi9pOHTLmZ/FeZRbWUJbj/oIc aCAAoIdgx72enzQgu0NmaQOqHTzNFtE1 =gtOX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] 13.1-RC1 repo's
by Upscope 22 Oct '13

22 Oct '13

are these two repo's correct fro 13.1-RC1? The oss one keeps taking me to Factory-Snapshot. I thought that had moved on to 13.2. Code ---------- http://download.opensuse.org/distribution/13.1/repo/oss/ http://download.opensuse.org/distribution/13.1/repo/non-oss/ ---------- I installed 13.1-RC1 from DVD's but it did not install the repo's. Russ -- openSUSE 12.3(Linux 3.11.1-3.gfeffbf9-desktop)|KDE 4.11.2 |Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS (NVIDIA-Linux-x86_64-325.15 Patched) -- 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] [13.1 RC1] dd problem
by Carlos E. R. 22 Oct '13

22 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Look: cer@Eleanor4:~/bin> dd if=/dev/zero of=sample bs=100 count=1 ; l sample 1+0 records in 1+0 records out 100 bytes (100 B) copied, 0.000910599 s, 110 kB/s - -rw-r--r-- 1 cer users 100 Oct 20 16:08 sample cer@Eleanor4:~/bin> dd if=/dev/random of=sample bs=100 count=1 ; l sample 0+1 records in 0+1 records out 22 bytes (22 B) copied, 0.00131574 s, 16.7 kB/s - -rw-r--r-- 1 cer users 22 Oct 20 16:08 sample cer@Eleanor4:~/bin> dd if=/dev/random of=sample bs=100 count=1 ; l sample 0+1 records in 0+1 records out 9 bytes (9 B) copied, 17.0424 s, 0.0 kB/s - -rw-r--r-- 1 cer users 9 Oct 20 16:08 sample cer@Eleanor4:~/bin> Why if the input is /dev/random, the size of the output file is not 100 bytes? Some times 16 bytes, some 20, some 9... However, if I run that in 12.3, I get the expected result, consistently: Telcontar:~ # dd if=/dev/random of=sample bs=100 count=1 ; l sample 1+0 records in 1+0 records out 100 bytes (100 B) copied, 0.00013542 s, 738 kB/s - -rw-r--r-- 1 root root 100 Oct 20 16:13 sample Telcontar:~ # Two tested machines running 13.1 fail (one virtual, one real) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJj6JcACgkQtTMYHG2NR9VZzQCeM2Kbfe4fOrSPOMPKTCyDFshX LUAAnRc/rRGyeidl1dTEM3kc36a6Qbvq =yqPb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 45

[opensuse-factory] RC1 net install broken
by Guido Berhoerster 22 Oct '13

22 Oct '13

It seems that RC1 tree on download.opensuse.org is currently broken making net-installs impossible: $ curl -IL http://download.opensuse.org/distribution/13.1/repo/oss/boot/x86_64/root HTTP/1.1 302 Found Date: Tue, 22 Oct 2013 16:00:48 GMT Server: Apache/2.2.12 (Linux/SUSE) Location: http://download.opensuse.org/factory-snapshot/repo/oss/boot/x86_64/root Content-Type: text/html; charset=iso-8859-1 HTTP/1.1 302 Found Date: Tue, 22 Oct 2013 16:00:48 GMT Server: Apache/2.2.12 (Linux/SUSE) X-Prefix: 79.192.0.0/10 X-AS: 3320 Location: http://downloadcontent.opensuse.org/srv/ftp/pub/opensuse/factory-snapshot/r… Content-Type: text/html; charset=iso-8859-1 HTTP/1.1 404 Not Found Content-Type: text/html; charset=utf-8 Content-Length: 808 Date: Tue, 22 Oct 2013 16:00:48 GMT Server: lighttpd/2 - openSUSE is good for you -- Guido Berhoerster -- 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] proposal of new package
by Oliver Neukum 22 Oct '13

22 Oct '13

Hi, I'd like to submit libmbim to Factory. This is a user space library that allows communication with devices that use the MBIM protocol, for which there's a kernel driver named cdc-mbim in recent kernels. ModemManager uses it to communicate with those devices making them availabe as WWAN devices. Regards Oliver -- 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] Tumbleweed inconsistency between DRBD kernel module and tools
by Wirlach Manfred 22 Oct '13

22 Oct '13

On 09.10.2013 06:21 Greg KH wrote: > On Tue, Oct 08, 2013 at 12:07:18PM -0400, Ken Schneider - openSUSE wrote: >> On 10/08/2013 04:01 AM, Wirlach Manfred pecked at the keyboard and wrote: >>> Hi all, >>> >>> yesterday I startet to migrate my openSUSE machines from normal >>> distribution to the rolling-update Tumbleweed (currently openSUSE 12.3) - machines are productive and so Factory was no option. >>> >>> After switching to Tumbleweed everything works fine except DRBD. >>> I found out that there is an inconsistency between drbd kernel >>> module (V8.4.3 in kernel-default) and the drbd admin tools (V8.3.11 from repository) which ends up with the inability to start the cluster volumes. >>> >>> As workaround I found a matching rpm on suse build service, but >>> please include a proper drbd-tools version in the Tumbleweed repos. >>> >>> Thx in advance. >>> >>> Manfred >>> >> Stability, stability, stability is what is needed for production >> machines which is something that TW _cannot_ provide/guarantee. >> Therefore it is not recommended for your use case. > It all depends on what your "production" is? I know lots of valid use > cases for constantly rolling updates for real-life-production-systems, > so please don't think that "stability" is somehow the only way stuff > like that can work. > > I'll be glad to add the drbd tools to Tumbleweed, Wirlach, what repo > should I pull them from to ensure they are kept up to date with the > kernel releases? > > thanks, > > greg k-h I'm a little bit confused about the replies which say that Tumbleweed is not stable enough for production use. Of course I will test all needed services before deploying them to production servers... This information is published at http://en.opensuse.org/Portal:Tumbleweed ----- The Tumbleweed project provides a rolling updates version of openSUSE containing the latest stable versions of all software instead of relying on rigid periodic release cycles. The project does this for users that want the newest, but stable software. The difference to Factory is that Factory is bleeding edge, often experimental, not yet stabilized software that needs more work to become useful. Tumbleweed contains the latest stable applications and is ready for daily use. ----- I'm currently using the following repos (as recommended on Tumbleweed homepage) http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ http://download.opensuse.org/distribution/openSUSE-current/repo/oss/ http://download.opensuse.org/update/openSUSE-current/ The Tumbleweed repo does not contain any drbd tools package - but drbd 8.4 kernel module within the kernel-default package. The older drbd tools package v8.3 came from the openSUSE-current repo. I've got the 8.4 tools package from http://download.opensuse.org/repositories/home:/smarty12/openSUSE_12.3/ Did I understand it correct that Tumbleweed references to the newest openSUSE stable distribution (today this should be 12.3), but offers newer software-packages (bleeding edge) and rolling updates to newer distributions? So why contains the Tumbleweed kernel a newer drbd module - just a little mistake in the big version jungle? Best regards Manfred -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] [13.1 RC1] Problem resizing vmplayer window
by Carlos E. R. 22 Oct '13

22 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, In 13.1 Beta I can simply grab the border of the vmware vmplayer window and resize it. However, in 13.1 RC1 I can not. I can resize the window size by using the guest XFCE settings manager "display" module, which allows me to set a fixed size. This should be a problem with the guest tools (provided by openSUSE), but they are installed and aparently do not work (completely). The same packages are installed on both: cer@Eleanor4:~> rpm -qa | grep -i vm | sort libLLVM-3.3-6.3.1.x86_64 libXxf86vm1-1.1.3-2.1.2.x86_64 libvmtools0-9.2.3-3.1.2.x86_64 lvm2-2.02.98-0.28.1.5.x86_64 open-vm-tools-9.2.3-3.1.2.x86_64 udevmountd-0.81.5-2.1.x86_64 xf86-input-vmmouse-13.0.0-5.1.2.x86_64 xf86-video-vmware-13.0.1-2.1.2.x86_64 yast2-vm-3.0.2-2.1.4.x86_64 cer@Eleanor4:~> - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJmW00ACgkQtTMYHG2NR9UHhACfVy8Xu0YAfiH0F7NAmYnmarvG j+oAn1ov9gLU6vjLZX9Lcz/+p+U6STmT =pz+D -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] Ancient hardware support statement
by İsmail Dönmez 22 Oct '13

22 Oct '13

Hi, On 10/21/2013 03:44 PM, Sascha Peilicke wrote: > Hi guys, > > without checking any mail archives, our forums or wikis for prior art, I would > like to know if we have any general hardware support statements. I'm currently > staring at a maintenance update that disables SSE2 support on certain software > because the CPU doesn't support it. The manufacturing of that CPU stopped in > 2004, so I'm not really sure what to think of it. Any thoughts? openSUSE builds for i586 hence SSE2 does not exist there. If we build for i686 instead we wouldn't need such changes. FWIW I am all for changing to i686 as default 32bit target. Regards, ismail -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 10

[opensuse-factory] sources were changed after submissions and the old sources never built...
by Cristian Rodríguez 22 Oct '13

22 Oct '13

Hi: I am getting this message as a "declined" request.. https://build.opensuse.org/request/show/204243 "apache2's sources were changed after submissions and the old sources never built. Please resubmit" Yes, It was my explicit intention to submit revision 393 to factory/13.1 not any later, I did not made a mistake.. but apparently the "factory-repo-checker" does not like it. am I supposed to be able to do this or the OBS cannot handle submissions of previous revisions ? -- "Judging by their response, the meanest thing you can do to people on the Internet is to give them really good software for free". - Anil Dash -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] [13.1 RC1] How to disable system asking for root password when hibernating?
by Carlos E. R. 21 Oct '13

21 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On [Bug 846914], I reported that the system requests for the root password to hibernate. I think this is absurd, it is a laptop and I can push the red button or remove the battery. It is withing my power. But Linux thinks otherwise. Why hibernation has to ask for root's password, but not a system restarts? Same machine, same user. I'm told to change something in policykit - I don't know how. There is no Yast module to change these things. I asked: +++······················· > Or where is the exact hack published? You can place overrides in /etc/polkit-default-privs.local and then run /sbin/set_polkit_default_privs. The privileges you're looking for are org.freedesktop.login1.hibernate-multiple-sessions and org.freedesktop.login1.suspend-multiple-sessions, see the man pages for polkit-default-privs, set_polkit_default_privs, and polkit for details. ·······················++- Well, I don't understand any of that. How exactly do I impede the system from asking the root password for hibernation, power off, reboot, etc? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJlncEACgkQtTMYHG2NR9XGngCcCIXJBseTEliPLp5WlQ3Fskvx yk8AoJi/7cD2o8dmKixwiJ7nHRBR1Bzu =u1Jp -----END PGP SIGNATURE-----

1 0

[opensuse-factory] [13.1 RC1] XFCE - hibernation test fails completely under vmplayer
by Carlos E. R. 21 Oct '13

21 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It hibernates, but on restore, it gets stuck at: s2disk: returned to userspace 1: Beginning Domain Validation - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJiwv4ACgkQtTMYHG2NR9WorQCgiKbWxpP6+kDZ0nBimMTJiPiF SkgAnjpLa8Es3oVeEyGrSbbAv3q9VXcR =k+7M -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 8

[opensuse-factory] [13.1 RC1] XFCE refuses to hibernate, and more.
by Carlos E. R. 21 Oct '13

21 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It asks for the root password, because it says another user is logged in - which is false. And when the password is given, it fails with popup message. A second attempt does not ask for the password, and succeeds... On restore, it "finds" an usb stick that was plugged before, umounted, and mounts it. I had clicked on umount an hour before, this is not respected after hibernation. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJh1EgACgkQtTMYHG2NR9WuSQCeIcR3TJ8fs24PTwlMXGsGAYUc 5E8An3GOLiNhANNlIjLzscSgOo1kQdQy =qkKy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 15

[opensuse-factory] Add your features!
by Jos Poortvliet 21 Oct '13

21 Oct '13

Heya, A reminder: please add features to http://en.opensuse.org/openSUSE:Major_features so we know what to talk about in our announcement! Hugs, J

1 0

[opensuse-factory] [13.1 RC1] I managed to destroy a btrfs - anyone wants to investigate it?
by Carlos E. R. 21 Oct '13

21 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a 2 GB test filesystem formatted as btrfs. I wrote to it 1 million files, 100 bytes each, as part of a test. Then I deleted all the files - however, space was not freed: Filesystem Size Used Avail Use% Mounted on /dev/sdb7 2,0G 4,6M 7,9M 37% /data/btrfs Eleanor4:~ # ls -a /data/btrfs/ . .. test Eleanor4:~ # ls -a /data/btrfs/test/ . .. Eleanor4:~ # There are no snapper configs, yast-snapper finds nothing and quits. Eleanor4:~ # snapper list-configs Config | Subvolume - -------+---------- Eleanor4:~ # Eleanor4:~ # snapper list Unknown config. Eleanor4:~ # snapper list all Command 'list' does not take arguments. Eleanor4:~ # snapper list -t all Unknown config. Eleanor4:~ # snapper -t all list Unknown config. Eleanor4:~ # Eleanor4:~ # snapper cleanup Command 'cleanup' needs one arguments. Eleanor4:~ # So I tried to fsck it. fsck did nothing. btrfsck says something, but repairs nothing: Eleanor4:~ # btrfsck /dev/sdb7 Checking filesystem on /dev/sdb7 UUID: facfd969-cebc-4558-960f-4798f43129cd checking extents checking free space cache free space inode generation (0) did not match free space cache generation (257) free space inode generation (0) did not match free space cache generation (255) free space inode generation (0) did not match free space cache generation (255) free space inode generation (0) did not match free space cache generation (257) free space inode generation (0) did not match free space cache generation (257) free space inode generation (0) did not match free space cache generation (257) checking fs roots checking csums checking root refs found 233472 bytes used err is 0 total csum bytes: 0 total tree bytes: 36864 total fs tree bytes: 8192 total extent tree bytes: 4096 btree space waste bytes: 24523 file data blocks allocated: 196608 referenced 196608 Btrfs v0.20-rc1+20130701 Eleanor4:~ # mount /data/btrfs Eleanor4:~ # df -h /data/btrfs Filesystem Size Used Avail Use% Mounted on /dev/sdb7 2.0G 264K 7.9M 4% /data/btrfs Eleanor4:~ # The man page for btrfsck is outdated! "btrfsck --help" gives some options. I tried "btrfsck --init-extent-tree /dev/sdb7" and "btrfsck --init-csum-tree /dev/sdb7" to no avail. But: Eleanor4:~ # btrfsck --repair /dev/sdb7 enabling repair mode parent transid verify failed on 776749056 wanted 283 found 274 parent transid verify failed on 776749056 wanted 283 found 274 parent transid verify failed on 776749056 wanted 283 found 274 parent transid verify failed on 776749056 wanted 283 found 274 Ignoring transid failure Checking filesystem on /dev/sdb7 UUID: facfd969-cebc-4558-960f-4798f43129cd checking extents ref mismatch on [29425664 4096] extent item 1, found 0 repair deleting extent record: key 29425664 168 4096 Backref 29425664 root 7 not referenced back 0x1cc46c0 Incorrect global backref count on 29425664 found 1 wanted 0 backpointer mismatch on [29425664 4096] owner ref check failed [29425664 4096] repaired damaged extent references checking free space cache cache and super generation don't match, space cache will be invalidated checking fs roots parent transid verify failed on 776749056 wanted 283 found 274 Ignoring transid failure checking csums checking root refs found 565248 bytes used err is 0 total csum bytes: 0 total tree bytes: 36864 total fs tree bytes: 8192 total extent tree bytes: 4096 btree space waste bytes: 23667 file data blocks allocated: 524288 referenced 524288 Btrfs v0.20-rc1+20130701 Eleanor4:~ # mount /data/btrfs mount: mount /dev/sdb7 on /data/btrfs failed: Cannot allocate memory Eleanor4:~ # Ok, a destroyed btrfs system. What can be done? Admit failure and reformat? Anyone wants to investigate this? Bugzilla? - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJkXp8ACgkQtTMYHG2NR9VQXACfRND/QQA0XdK73/7bYrYnrOnt v9kAni0FsLUoiCM1yobjzQ2czoFuxksO =Nbtl -----END PGP SIGNATURE----- -- 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] UPower update to 1.0 for openSUSE 13.2
by Dominique Leuenberger a.k.a. Dimstar 21 Oct '13

21 Oct '13

Hi all, openSUSE 13.1 is almost there, things look not too bad (in most areas) and it's (almost) time to start breaking things. The first known breakage to report is an update of UPower to version 1.0, that will be required for GNOME 3.12 (which we should not have any troubles by timeline to get into 13.2). Now, of course, UPower is used by more than only GNOME, so please consider this notice a heads-up, to be aware something is coming. The most notable being that UPower is no longer responsible for suspend/hibernate. The original announcement from upstream: === Heya, As some of you might have seen at: http://www.hadess.net/2013/10/more-power-management-changes.html I've done some work on UPower, and hope to label it 1.0 (though that's not really my remit) before the end of the GNOME 3.12 cycle. With this work, I've been able to shave off a couple of thousands of lines of code from gnome-settings-daemon, make it work better for consumers of the D-Bus interface, in particular GDBus. gnome-shell, gnome-settings-daemon and gnome-control-center have been ported to the new API, though gnome-control-center could do with additional cleanups. I believe telepathy and tracker used API that was removed but both got ported. Cheers === Hope to have everybody informed sufficiently to start the thread about how bad changes are. Dominique -- 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] openQA
by Guido Berhoerster 21 Oct '13

21 Oct '13

Hi, why haven't there been any openQA runs on Factory and 13.1? At Beta/RC time it is more important than ever and there are e.g. problems net-installing the Xfce desktop post-Beta1 where openQA would really be helpful. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 33

[opensuse-factory] RC 13.1 nfs, autofs problem
by Paweł Wieczorkiewicz 21 Oct '13

21 Oct '13

Hi, Is this a known issue? I am trying to restart (systemctl) autofs. If so, could someone point me to the bug regarding this: /var/log/messages:2013-10-20T15:07:29.338919+02:00 pc kernel: [24755.614327] traps: automount[7643] general protection ip:7f075cf823d8 sp:7fffec21f668 error:0 in libpthread-2.18.so[7f075cf71000+18000] Thanks! BR, Pawel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

Re: [opensuse-factory] Re: 2 questions about 13.1 RC1
by "Stefan Brüns" 20 Oct '13

20 Oct '13

Am 19.10.13, schrieb Jan Engelhardt <jengelh(a)inai.de>: > > In XFCE, the same occurs and was only "fixed" by installing gvfs. > (wtf does udisks need gvfs?) > Of course I could just manually mount(8) them, which I fathom Dolphin > might just do (which would also explain why it needs root, if it does). XFCE might depend on gvfs, udisks does not. You can mount devices using udisk (iirc the CLI tool is called udiskctl), who is allowed to do what depends on your policykit settings (/etc/polkit-default-privs.*) Dolphin uses udisks via its solid library. On KDE, you can (un)mount partitions from Dolphin, from the Device Notifier, from Konqueror ... Policykit settings apply here as well. Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- 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] Two XFCE problems on 13.1 RC1
by Carlos E. R. 20 Oct '13

20 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have two problems with XFCE. 1) Log out is impossible. Solution seems to be install "iceauth" (bug 845264) 2) Once "iceauth" is installed, I can log out, but it doesn't ask to save settings on log out (setting to "ask on log out" is set). Is there a report on (2) ? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJhy+QACgkQtTMYHG2NR9VL9ACgiTASVdnHsWmAUDUgydJTslbU cckAnA7FaFgstMyGoYAuCQR9vdQElOub =ccZq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 10

[opensuse-factory] [13.1 RC1] XFCE - of two installs, one gets ibus, one not.
by Carlos E. R. 20 Oct '13

20 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On two installs, one of the two gets ibus installed and activated. What for? AFAIK, the Spanish keyboard does not need that. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJivXsACgkQtTMYHG2NR9WzpACfVnmGGDs7mWDQ76hOq2lIBRTT m14AniJpPIH7e1zZsAWa+U9OGqdUST1c =kHPh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] 13.1: no NIC configured at boot after zypper dup upgrade
by Greg Freemyer 18 Oct '13

18 Oct '13

On Wed, Oct 16, 2013 at 4:52 PM, lynn <lynn(a)steve-ss.com> wrote: > On Wed, 2013-10-16 at 16:18 -0400, Greg Freemyer wrote: >> On Wed, Oct 16, 2013 at 2:40 PM, Cristian Rodríguez >> <crrodriguez(a)opensuse.org> wrote: >> > El 16/10/13 15:29, Rich Coe escribió: >> >> I'm running 13.1. >> >> I have a fixed ip-address configured for eth0 and it supposed to config with ifup. >> >> >> >> On boot, eth0 does not get configured. >> >> Running 'ifup eth0' does not configure eth0 either. >> >> >> >> Any tips to configure eth0 at boot or diagnose the issue? >> >> >> >> Thanks. >> >> >> > >> > There is no eth0 or eth1 or whatever eth.. by default now. interfaces >> > are named according to >> > http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac… >> > .. that document contains instructions to "go back" to the old names.. >> >> >> Christian, >> >> I opened a bugzilla yesterday because after a 12.3 => 13.1 >> upgrade I didn't have a configured interface of any name. >> >> <https://bugzilla.novell.com/show_bug.cgi?id=845886> >> >> I had to go into yast and configure it before it showed up with any name. >> >> After configuring via yast, it showed up when I ran ifconfig. I >> assumed it was VMware related, but I don't know. >> >> Greg > > Hi > 12.3 to 13.1 upgrade same here but on vbox. The upgrade knocked out what > was usually eth0. ifup failed. I too ran yast where I found that the > default route had been deleted. I re-entered it and yast completed > whereupon ifup eth0 began working again. > > Will this be the norm for the upgrade to 13.1? > Thanks, > L x Lynn, Did you open a bugzilla? If this is not a pure VMware related bug, this is seeming like a major / potential showstopper bug to me. My bugzilla again is: <https://bugzilla.novell.com/show_bug.cgi?id=845886> I have it set as priority "none" currently because I thought it only impacted VMware installs. I repeated my upgrade test of VWware appliance from 12.3 => 13.1 on another VM. I used: - Set Repos to 12.3 OSS and 12.3 OSS upgrade repos only. - zypper dup to ensure a pure 12.3 environment was in place - change the 2 repos to the 13.1 equivalents - zypper dup - choose uninstall vmware client packages (2 different interactions with zypper) - let it run to completion - reboot - login as root - ifconfig The only interface displayed is lo (loopback). I don't need this VM to be functional, so I'll leave it like that if anyone wants me to do any troubleshooting. If you want it properly tracked, please ask via bugzilla. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 7

[opensuse-factory] 2 questions about 13.1 RC1
by Roman Bysh 18 Oct '13

18 Oct '13

Two (2) questions about 13.1 RC1 which I installed (clean install) on my wife's computer: 1. Where in blue-blazes does one find a USB stick when it is mounted in an USB port?! 1b Answer Click on up arrow in the system tray to see your Device Notifier. 2. How does one login as another user - as root for instance - when either (a) booting the system or (b) when one goes to Logout and then login as, say, root?! 2b Answer I always set in in Yast-->Security and Services-->User and Group Management-->Select the Expert Options-->click on dropdown arrow and select Login Settings A Display Manager Login Settings window appears. Under _User_ Login to Log In--> and select a different user for auto login. Click on the OK buttons. Cheers! Roman -- 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] 13.1: no eth0 configured at boot
by Rich Coe 18 Oct '13

18 Oct '13

I'm running 13.1. I have a fixed ip-address configured for eth0 and it supposed to config with ifup. On boot, eth0 does not get configured. Running 'ifup eth0' does not configure eth0 either. Any tips to configure eth0 at boot or diagnose the issue? Thanks. -- Rich Coe rcoe(a)wi.rr.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 14

[opensuse-factory] Packman repository for 13.1 RC1
by Bob Williams 18 Oct '13

18 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there a Packman repository for openSUSE 13.1? I need the broadcom wifi drivers, which are usually available from Packman. The version of broadcom.wl in the Packman 12.3 repo fails to provide one dependency. Bob - -- Bob Williams System: Linux 3.7.10-1.16-desktop Distro: openSUSE 12.3 (x86_64) with KDE Development Platform: 4.10.5 "release 4" Uptime: 18:00pm up 3 days 7:23, 3 users, load average: 0.25, 0.20, 0.23 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJgY2UACgkQ0Sr7eZJrmU6IaQCfSnCUCck+p1a3ERxAe0WvmZD3 IOIAnR6/ft9bYZtvAOiI4uAhdSPFvr8I =1a/A -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] 13.1 rc1 YaST2 NFS client configuration error. bug 845620
by Steven Hess 17 Oct '13

17 Oct '13

bug 845620 I raised this bug and it says it's unresolved. On a clean install of 13.1 rc1 Hangs at 50% then fails. I did a clean install as my previous install never would properly shut down after I fiex it by adding the server to my hosts file. It would hit the Plymouth shut doen screen and just stop. How do I proceed since this is not fixed I can really use this machine for much or really do any testing? If you want testing it's got to be something I can more or less use as my general computing desktop I'd really like to keep testing. 2013-10-17T18:22:30.833114+00:00 linux-8vd9 rpcbind[7851]: Cannot open '/var/lib/rpcbind/rpcbind.xdr' file for reading, errno 2 (No such file or directory) 2013-10-17T18:22:30.833591+00:00 linux-8vd9 rpcbind[7851]: Cannot open '/var/lib/rpcbind/portmap.xdr' file for reading, errno 2 (No such file or directory) 2013-10-17T18:22:31.444803+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.445256+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.465269+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.465781+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.480243+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.480669+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.494420+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.494821+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.508608+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.508970+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.522730+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.523147+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.536442+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.536783+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.550556+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.550928+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.564544+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.565059+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.585006+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.585447+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.600394+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.600731+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.614629+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.615094+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.628290+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.628712+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.645018+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.645418+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.658285+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.658652+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.672487+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.672898+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:27:30.902288+00:00 linux-8vd9 systemd[1]: nfs.service operation timed out. Terminating. 2013-10-17T18:27:30.903219+00:00 linux-8vd9 systemd[1]: Failed to start LSB: NFS client services. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 openSUSE Linux 12.3 KDE Known as FlameBait and The Sock Puppet of Doom. -- 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] Tumbleweed: Black screen after suspend
by Stefan Zimmer 17 Oct '13

17 Oct '13

Hi, my DELL Latitude E6510 runs with Tumbleweed and the proprietary Nvidia driver. Until about begin of last week, everything worked fine, but after some updates, the screen stays black, or shows some triangle artefaicts after resuming the laptop from suspend mode. When I switch to console, kill kwin, the desktop is shown again. Greetings, Stefan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Do 13.1 maintenance updates end up in the OSS repo?
by Greg Freemyer 17 Oct '13

17 Oct '13

I just did a SR to 13.1 updates which really needs to be in the OSS repo, not updates. https://build.opensuse.org/request/show/203614 Does that require any special hand holding or are all updates at this point still headed to the main OSS repo. Greg -- Greg Freemyer -- 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] /etc/mailcap still needed?
by Ludwig Nussel 17 Oct '13

17 Oct '13

Hi, I got a bug report about xine in /etc/mailcap (842938). IMO it's wrong to have things like xine or realplay(!) hardcoded in there. Maybe we should ship that file empty or not at all anymore. Any opinions? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- 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] 13.1RC1: Problems with automounter and LDAP
by Johannes Weberhofer 17 Oct '13

17 Oct '13

Dear all, I've installed the latest beta and now I have upgraded to the RC1 of opensuse. In both I can not use the automounter. I see the following failures in the log: 2013-10-17T08:42:06.948533+00:00 c-web3 automount[3076]: DIGEST-MD5 common mech free 2013-10-17T08:42:06.991094+00:00 c-web3 automount[3076]: parse_server_string: lookup(ldap): invalid LDAP map syntax erkules.test.com:nisMapName=auto.herkules,ou=autofs,dc=weberhofer,dc=at 2013-10-17T08:42:06.994942+00:00 c-web3 automount[3076]: lookup_init: lookup(ldap): cannot parse server string 2013-10-17T08:42:06.998318+00:00 c-web3 automount[3076]: mount_autofs_indirect: failed to read map for /herkules 2013-10-17T08:42:07.003886+00:00 c-web3 automount[3076]: handle_mounts: mount of /herkules failed! 2013-10-17T08:42:07.006092+00:00 c-web3 automount[3076]: master_do_mount: failed to startup mount 2013-10-17T08:42:07.041502+00:00 c-web3 automount[3076]: parse_server_string: lookup(ldap): invalid LDAP map syntax erkules.test.com:nisMapName=auto.home,ou=autofs,dc=weberhofer,dc=at 2013-10-17T08:42:07.042380+00:00 c-web3 automount[3076]: lookup_init: lookup(ldap): cannot parse server string 2013-10-17T08:42:07.043116+00:00 c-web3 automount[3076]: mount_autofs_indirect: failed to read map for /home 2013-10-17T08:42:07.043794+00:00 c-web3 automount[3076]: handle_mounts: mount of /home failed! 2013-10-17T08:42:07.044905+00:00 c-web3 automount[3076]: master_do_mount: failed to startup mount Is there any change required on the LDAP-Server? It's strange, that it writes "invalid LDAP map syntax erkules.test.com" where normally "herkules" should appear instead of "erkules". The system is running in my production environments, so older openSUSE versions accept the current configuration in LDAP. Except that, 13.1 looks great and runs very smoothly even on the slightly older test-machine. Well done! Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] New Project: ERP
by Axel Braun 16 Oct '13

16 Oct '13

Hello, I have build the OpenSource ERP System Tryton (www.tryton.org) in my private sandpit https://build.opensuse.org/project/show/home%3ADocB%3Apython_packages and would like to find a place in the 'official' repositories for it. What would be a suitable place, e.g repositories/ERP repositories/Application: Thanks Axel

1 0

[opensuse-factory] btrfs still borked
by Lew Wolfgang 16 Oct '13

16 Oct '13

Hi Folks, I finally have a chance to work on my previously reported issue with btrfs where I can't write more than about 15-TB to a single partition. Here's the machine: Supermicro X9DRH mobo 2-ea Xeon E5-2643 64-GB RAM 1-ea LSI MegaRAID SAS 2208 RAID controller 2-ea SSD 120-GB drives configured as RAID-1 mirror 24-ea 2-TB SATA drives configured as two 11-disk RAID-6 arrays with 2-hotswaps So I loaded 13.1 beta1 and pulled a "zipper dup". Here are my initial observations. 1. No more reiserfs! 2. The installer complains about using XFS on the boot partition 3. The installer complains if the boot partition is less than 12-MB (good!) But the installer won't let the install proceed past the final summary screen if I have multiple system partitions. It complains that there isn't enough room for the selected packages (default). There is room, but it complains nevertheless. Here's the error: "Not enough disk space. Remove some packages in the Single Selection" The screen said that 3.2-GB was required, but there was more than 50-GB available. I got around the error by just having one swap and one root partition. Configure the root partition and one of the data arrays with btrfs. The second data array was formatted as XFS. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] boot menu still gives 12.3 after upgrade to 13.1
by lynn 16 Oct '13

16 Oct '13

Hi 12.3 to 13.1 rc1 upgrade via the NET install iso. It has upgraded fine to 13.1 but the menu for which to boot still shows only 12.3. I think this is a label in grub somewhere. Can anyone help me sort this out? Thanks, Lynn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 5

[opensuse-factory] Are there any articles on setting up a lampserver on opensuse
by doiggl＠velocitynet.com.au 16 Oct '13

16 Oct '13

Hello, I have some questions: 1. Are there any articles on setting up a lampserver on opensuse. I am interested in what goes into the index.html What software can I use to test the lampserver software stack and all the components are working[1] Thanks Glenn [1]LAMP stack (Linux Apache MySQL PHP) -- 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] testing - what help do we want?
by Jos Poortvliet 16 Oct '13

16 Oct '13

Heya, Please - help your marketing team write a decent "help test openSUSE" article... We need some input on what would be helpful, what do we want people to do. See https://news.opensuse.org/?p=16783&preview=true - and notice how empty it is! This is scheduled for next week so ideally we'd get some kind of input this week... please? /J

3 2

[opensuse-factory] openSUSE:Factory snapshot versus standard
by Lars Marowsky-Bree 16 Oct '13

16 Oct '13

Hi, we're building packages in network:ha-clustering:Factory against, well, Factory. Nodes have just these two repos: baseurl=http://download.opensuse.org/repositories/network:/ha-clustering:/F… baseurl=http://download.opensuse.org/factory/repo/oss/ Problem: nothing provides kernel-uname-r = 3.11.4-1-default needed by ocfs2-kmp-default-1.8_k3.11.4_1-0.19.4.x86_64 ocfs2-kmp-default was build yesterday (Wed 9, around 9:00). The latest available kernel-default package is: i | kernel-default | package | 3.11.3-2.1 | x86_64 | openSUSE-Factory (Sun Oct 6 01:07:53 2013) I also tried /factory-snapshot/ and a number of other install sources, but no luck. It'd appear more logical to me if n:h:F was *behind* Factory, not the other way around. What am I doing wrong? Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 23

[opensuse-factory] dracut problem
by Sid Boyce 15 Oct '13

15 Oct '13

System drops into a dracut shell, no devices found. "ls -l /dev/disk" is not there. With the previous 3.12.0-rc4 vanilla kernel installed one week ago, lsinitrd shows a large number of modules. sabre:~ # dracut --force --kver 3.12.0-rc5-smp+ Executing: /usr/bin/dracut --force --kver 3.12.0-rc5-smp+ dracut module 'cifs' depends on 'network', which can't be installed dracut module 'network' cannot be found or installed. dracut module 'network' cannot be found or installed. dracut module 'network' cannot be found or installed. dracut module 'network' cannot be found or installed. *** Including module: bash *** *** Including module: i18n *** *** Including module: drm *** *** Including module: plymouth *** *** Including module: btrfs *** *** Including module: crypt *** *** Including module: dm *** Skipping udev rule: 64-device-mapper.rules Skipping udev rule: 60-persistent-storage-dm.rules Skipping udev rule: 55-dm.rules *** Including module: dmraid *** Skipping udev rule: 64-md-raid.rules *** Including module: kernel-modules *** *** Including module: lvm *** Skipping udev rule: 64-device-mapper.rules Skipping udev rule: 56-lvm.rules Skipping udev rule: 60-persistent-storage-lvm.rules *** Including module: mdraid *** Skipping udev rule: 64-md-raid.rules *** Including module: multipath *** Skipping udev rule: 40-multipath.rules Skipping udev rule: 62-multipath.rules Skipping udev rule: 65-multipath.rules Skipping udev rule: 66-kpartx.rules *** Including module: resume *** *** Including module: rootfs-block *** *** Including module: terminfo *** *** Including module: udev-rules *** Skipping udev rule: 91-permissions.rules *** Including module: systemd *** *** Including module: base *** *** Including module: fs-lib *** *** Including module: shutdown *** *** Including module: suse *** *** Including modules done *** *** Installing kernel module dependencies and firmware *** *** Installing kernel module dependencies and firmware done *** *** Resolving executable dependencies *** *** Resolving executable dependencies done*** *** Hardlinking files *** *** Hardlinking files done *** *** Stripping files *** *** Stripping files done *** *** Generating early-microcode cpio image *** *** Constructing AuthenticAMD.bin **** *** Constructing GenuineIntel.bin **** *** Creating image file *** *** Creating image file done *** sabre:~ # lsinitrd /boot/initrd-3.12.0-rc5-smp+ Image: /boot/initrd-3.12.0-rc5-smp+: 19M ======================================================================== with dracut modules: ======================================================================== drwxr-xr-x 3 root root 0 Oct 15 04:09 . drwxr-xr-x 3 root root 0 Oct 15 04:09 kernel drwxr-xr-x 3 root root 0 Oct 15 04:09 kernel/x86 drwxr-xr-x 2 root root 0 Oct 15 04:09 kernel/x86/microcode -rw-r--r-- 1 root root 18644 Oct 15 04:09 kernel/x86/microcode/AuthenticAMD.bin -rw-r--r-- 1 root root 494592 Oct 15 04:09 kernel/x86/microcode/GenuineIntel.bin ======================================================================== sabre:~ # rpm -qi dracut Name : dracut Version : 034 Release : 1.1 Architecture: x86_64 Install Date: Tue 15 Oct 2013 04:14:09 BST sabre:/boot # cat /etc/SuSE-release openSUSE 13.1 (x86_64) VERSION = 13.1 CODENAME = Bottle # /etc/SuSE-release is deprecated and will be removed in the future, use /etc/os-release instead Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 5

[opensuse-factory] Problem with time display
by Thomas Taylor 15 Oct '13

15 Oct '13

openSUSE 13.1-RC1 (from DVD) KDE 4.11.12 On the lower right corner of the DE the time being displayed is UTC and I have been unsuccessful at trying to change either the actual time displayed or the time zone (mine is Los Angeles). When I right click on the time display and select "Adjust Date & Time", I am able to select the Los Angeles time zone. When I then supply the administrator password and click OK I get a message saying it's unable to reach the internet. NTP has been set up successfully using Yast2 and is apparently working. I am attaching a *.tar.bz2 file containing the ntp and message logs and a screenshot of the error message in hopes of getting a suggestion to solve this dilemma. Thanks, Tom -- Every man is encompassed by a cloud of comforting convictions, which move with him like flies on a summer day. - Bertrand Russell ^^ --... ...-- / -.- --. --... -.-. ..-. -.-. ^^^^ Tom Taylor - retired penguin - KG7CFC AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata2 openSUSE 13.1_RC1-x86_64 KDE 4.11.12, FF 24.0, claws-mail 3.9.2 registered linux user 263467

3 5

[opensuse-factory] plasma-nm instead of NetworkManager-kde4?
by Robert Munteanu 15 Oct '13

15 Oct '13

Hi, I did a fresh install of 13.1 RC1 from http://software.opensuse.org/developer/en, using the DVD ISO. I've performed a zypper dup, which seemed to promptly replace NetworkManager-kde4 with plasma-nm. Is this intended? If it is, I assume there were some pretty good reasons, as I've already found two bugs: - https://bugzilla.novell.com/show_bug.cgi?id=845909 (VPN connection can not be started from plasma-nm-openconnect) - https://bugzilla.novell.com/show_bug.cgi?id=845783 (NetworkManager fails to save connection details for WAN connection with TLS) Robert -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7

[opensuse-factory] Installation of ImageMagick-6.8.6.9-4.3 failed
by Olaf Hering 15 Oct '13

15 Oct '13

I'm doing zypper dup in a VM with btrfs, the dup fails like shown below. exception_8h.html is currently a file. Is this just an intermediate state between 12.3 and 13.1, or will a dist upgrade now likely fail? Olaf (1654/2159) Installing: ImageMagick-6.8.6.9-4.3 ...........................................................................[error] Installation of ImageMagick-6.8.6.9-4.3 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/doc/packages/ImageMagick/www/api/MagickCore/exception_8h.html;524c4c73: cpio: link error: ImageMagick-6.8.6.9-4.3.x86_64: install failed error: ImageMagick-6.8.5.7-3.5.x86_64: erase skipped Abort, retry, ignore? [a/r/i] (a): r (1654/2159) Installing: ImageMagick-6.8.6.9-4.3 ...........................................................................[error] Installation of ImageMagick-6.8.6.9-4.3 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/doc/packages/ImageMagick/www/api/MagickCore/exception_8h.html;524c4d21: cpio: link error: ImageMagick-6.8.6.9-4.3.x86_64: install failed error: ImageMagick-6.8.5.7-3.5.x86_64: erase skipped Abort, retry, ignore? [a/r/i] (a): -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 22

[opensuse-factory] beta 1 to rc1 question
by lynn 15 Oct '13

15 Oct '13

I just did a zypper dup on a 13.1 beta 1 and expected to see this: zypper dup locks up Bug #802525 But nothing. Only 6 packages were updates: zypper dup Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Retrieving repository 'openSUSE-13.1-1.2' metadata .......................[done] Building repository 'openSUSE-13.1-1.2' cache ............................[done] Retrieving repository 'openSUSE-13.1-Non-Oss' metadata ...................[done] Building repository 'openSUSE-13.1-Non-Oss' cache ........................[done] Retrieving repository 'openSUSE-13.1-Update' metadata ....................[done] Building repository 'openSUSE-13.1-Update' cache .........................[done] Loading repository data... Warning: Repository 'openSUSE-13.1-Update-Non-Oss' appears to outdated. Consider using a different mirror or server. Reading installed packages... Computing distribution upgrade... The following packages are going to be upgraded: accountsservice libaccountsservice0 libblkid1 libmount1 libuuid1 util-linux 6 packages to upgrade. Overall download size: 1.2 MiB. No additional space will be used or freed after the operation. Continue? [y/n/?] (y): And all was fine. Is that it? How do I know if I now have rc1? Thanks, L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 17

[opensuse-factory] should zypper dup inside a VMware appliance work yet?
by Greg Freemyer 15 Oct '13

15 Oct '13

I just tried to upgrade a VMware instance from 12.3 to 13.1 and I'm getting a complaint about a vmware client incompatibility. I only have 13.1 and 13.1 updates enabled as a repo. Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] 13.1 conflict
by Wolfgang Rosenauer 14 Oct '13

14 Oct '13

Hi, I'm getting this when I try to install gcc: ox:~ # zypper in gcc Loading repository data... Warning: Repository 'openSUSE-13.1-Update-Non-Oss' appears to outdated. Consider using a different mirror or server. Reading installed packages... Resolving package dependencies... Problem: gcc-4.8-2.1.2.x86_64 requires gcc48, but this requirement cannot be provided uninstallable providers: gcc48-4.8.1_20130909-3.2.1.i586[openSUSE-13.1-1.19] gcc48-4.8.1_20130909-3.2.1.x86_64[openSUSE-13.1-1.19] Solution 1: deinstallation of libgcc43-4.3.4_20091019-19.1.3.x86_64 Solution 2: do not install gcc-4.8-2.1.2.x86_64 Solution 3: do not install gcc-4.8-2.1.2.x86_64 Solution 4: break gcc-4.8-2.1.2.x86_64 by ignoring some of its dependencies zypper is configured for http://download.opensuse.org/distribution/13.1/repo/oss/ Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 13

[opensuse-factory] betapizzahackaton
by Jos Poortvliet 14 Oct '13

14 Oct '13

Heya, I'm working on an article on the bph ;-) If you participated, I'd love to get a quote, (screen)shot or in general hear your experiences, both good and bad*. Hugs, J *Can't promise to put the bad ones in the article but I'll make sure they are heard internally if needed.

1 0

[opensuse-factory] findutils,rpm: from Factory to Factory:Build?
by Bernhard Voelker 14 Oct '13

14 Oct '13

Hi *, after the upgrade of findutils to 4.5.12 in Factory [1] and the ugly hassle with it because the 'rpm' package needed a fix for an obsolete syntax [2] two weeks ago - sorry again, Coolo! - how will both packages now find their way into Factory:Build again? [1] https://build.opensuse.org/request/show/200576 [2] https://build.opensuse.org/request/show/200646 Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] RC1: Loading Installation System (#/6) 100% always
by Felix Miata 13 Oct '13

13 Oct '13

Loading Installation System (#/6) 100% Each such line only ever says 100%, no actual progress percentage ever displays as it used to. HTTP init using Grub Legacy cmdline: showopts install=http://download.opensuse.org/factory-snapshot/repo/oss/ hostname=myhost hostip=192.168.1.2/24 gateway=192.168.1.1 nameserver=192.168.1.1 kexec_reboot=0 ipv6.disable=1 net.ifnames=0 noresume video=1152x864@85 vga=791 3 lang=en keytable=us namescheme=by-label -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3