October 2013 - openSUSE Factory - openSUSE Mailing Lists

[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