March 2014 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Include lxc in Tumbleweed
by Johannes Kastl 22 Mar '14

22 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone (part 2), any thoughts against including lxc in Tumbleweed? The virtualization-repo contains a package for the latest release 1.0, and it should be in factory, afaik. Regards, Johannes - -- `Oh, you may not think I'm pretty, But don't judge on what you see, I'll eat myself if you can find a smarter hat than me.´ (The Sorting Hat in Harry Potter I) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlMh+u4ACgkQzi3gQ/xETbJLFwCglmlJAgUfnQm4fQtSeaaNEGWW SdIAoIONdr2TOzLaByRnXUMoS7RQdBWf =bicg -----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 4

[opensuse-factory] Base:System util-linux, regarding sr 226509
by Ruediger Meier 21 Mar '14

21 Mar '14

Hi, The ChangeLog is almost useless since none of the referenced bug reports is readable for non-suse people. At least one of the added patches ("umount-avoid-readlink.patch") has no effect because it patches a deprecated and unused subdir which will be removed in next release anyway. Please somebody have a look at the last changelog and either make the bug reports world-readable or fix the changlog to explain the purpose of these patches: ------------ Mon Mar 17 22:36:58 CET 2014 - sbrabec(a)suse.cz - Merge fixes and features from SLE11 (bnc#831868): * Detect squashfs version <= 3 as squashfs3 and version >= 4 as squashfs. (mszeredi(a)suse.cz, util-linux-ng-2.16-squashfs3-detect.patch, bnc#666893) * add sfdisk-warn-about-2TB-limit.patch (puzel(a)novell.com, bnc#495657) * Document barrier option in mount.8 (jack(a)suse.cz, hvogel(a)suse.de, util-linux-ng-2.19.1-barrier_documentation.patch, bnc#489740) * lscpu: improve hypervisor detection (puzel(a)novell.com, fate#310255) - util-linux-lscpu-improve-hypervisor-detection.patch * umount: avoid calling readlink on mountpoints if not necessary - add: umount-avoid-readlink.patch (puzel(a)suse.com, bnc#794529) * fix file conflict between util-linux and s390-32 (puzel(a)suse.com, bnc#805684) * util-linux-update-default-commit-interval.patch: mount(8): update default commit interval (puzel(a)suse.com, bnc#809480) * Obsolete no more packaged uuid-runtime. - Add uname26 (util-linux-setarch-uname26.patch, FATE#313476). ---------------- cu, Rudi -- 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] Proposal or Request to remove openSUSE13_1_LOCAL.exe from the install media.
by Carlos E. R. 21 Mar '14

21 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The installation DVD contains these files: openSUSE13_1_LOCAL.exe openSUSE13_1_NET.exe autorun.inf People popping the DVD on a Windows machine will run that file, automatically, and try to install openSUSE that way. It does not work: ever, AFAIK. It is not documented anywhere. No mention of it in the startup guide or reference book, or I have not seen it. People now and then come to the forums, disappointed that openSUSE does not work, until we find out that they are trying to install "The Windows Way". Immediately and abruptly we tell them not to use an unsupported, obsolete, method that does not work and nobody knows anything about it. To boot the DVD and use the supported and documented method instead. Proposal: a) · That the procedure is explicitly and clearly documented in our books. · That somebody steps up and support, hand holding as necessary, the newcomers that try this method. · That a method to contact that/those person(s) is clearly published. · That there a readme file about this method is included in the install media. b) · Lacking any of the above (a), the installation .exe files and autorun.inf be completely removed from our install media. (Excuse my harshness if you feel that way. No impoliteness was intended). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMsGYAACgkQtTMYHG2NR9V1xgCfSPsXt/SCA3R7EqkgJCPBdmw8 GzYAn0QNeR05gzssPZYoifRpVtzXDYaS =43Wf -----END PGP SIGNATURE-----

2 2

[opensuse-factory] When was it decided to stop supporting remote desktops?
by Linda Walsh 20 Mar '14

20 Mar '14

It seems that's what has happened. When the dri drivers went into the X server, the removed the Xgl (or was it Xglx) extension that allowed OpenGL to be encapsulated in X. This meant you could have a server with lots of resources to do computations that would use a remote computer with a high end graphics card on any platform that supported X (BSD, MacOS, Windows (xp to win7) as well as desktop linux clients that don't have the same resources as a server. FWIW, the server wasn't built with available power supplies to even begin to support high end graphics cards these days. It seems also that this is the reason why XDMCP no longer works -- it was another remote desktop facility that would have needed the Xgl to transport most of today's desktop managers that use graphics acceleration to enable faster desktop respond with fancier effects. OpenGL *used* to work remotely on openSuse. Not anymore -- it seems that no form of remote testing or forwarding a remote desktop has been done for the past few cycles. I am biased in that I wanted to be able to use such occasionally -- maybe more so with an upgraded network. Was it actually planned, or did RedHat just kill it and other vendors followed suit because they went with the dri solution? The wayland support also doesn't seem to have an X-compat solution for 3D either. I'm not sure how possible or easy it would be, but it might be possible to get a degraded performance with a virtualGL solution that was designed to send the rendering commands to a 3rd computer that just did rendering and display the result to the client using the equivalent of jpeg/mpeg compression over slower networks, but possibly uncompressed over faster networks coming down the line. If the user has a 1Gb ethernet -- not unreasonable, they would have a max of about a max theoretical around 0.12GB which is about 7 frames/second if you try to send full screens, it would be hard to compress and uncompress that in SW to make it faster. But if you are just sending the rendering commands, it's like the difference between SVG and bitmapped graphics. The latter is 100's to 1000's times larger. Some of the largest SVG's I've seen have still been under 1MB, vs. bitmapped tiff's ... I've seen a few too many 4+GB that take a long time to read or write even over 1Gb. I'm guessing this wasn't intentional (??I hope), but that not many people realized what was happening until some time after the fact?? Is breaking remote compatibility with the past 15+ years a good thing? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 33

[opensuse-factory] M0 installation proposed xfs for /home
by Robert Munteanu 20 Mar '14

20 Mar '14

Hi, Just installed M0 from DVD. I pretty much kept to the defaults, and I noticed that /home is xfs, not btrfs, although I have other partitions formatter as btrfs. I was under the impression that the default is btrfs for 13.2 [1] Is this intentional? Robert [1]: https://news.opensuse.org/2014/03/19/development-for-13-2-kicks-off/ -- 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

3 3

Re: [opensuse-factory] Re: When was it decided to stop supporting remote desktops?
by Carlos E. R. 19 Mar '14

19 Mar '14

On 2014-03-19 18:20, Claudio Freire wrote: > On Tue, Mar 18, 2014 at 8:54 PM, Carlos E. R. wrote: Your post did not reach the list. The reason is that it contains an html part, thus the mail server rejects it. Silently, it seems. You have to configure your mail software to send pure plain text email only, at least to the lists. I'll copy your email back. > > It seems to be doing the rasterization in software on the X server, in > > spite of having more than enough acceleration capabilities, > resulting in > > 8fps or less (couldn't accurately measure). > > Well, that's expected for Nouveau, accel is not complete. > > > How come nouveau has enough acceleration support to run compositing > desktops and even games I believe (haven't tested the more demanding > ones), but not glxgears? > > Does xgl impose some seldom-supported mode of operation? (I can't > imagine that) You could compare how fast it runs locally and how fast remotely. If they are very different, I can only guess that it does not use the same methods in each case. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

2 1

Re: [opensuse-factory] Re: When was it decided to stop supporting remote desktops?
by Carlos E. R. 19 Mar '14

19 Mar '14

On 2014-03-18 20:17, Claudio Freire wrote: > On Tue, Mar 18, 2014 at 9:44 AM, Carlos E. R. <> wrote: Your post did not arrive on the list. Are you sure you are subscribed? > Tried between nVidia-nouveau desktop and headless server (glxgears at > headless server) and it works, if you can call it working. Ah! That's interesting. > It seems to be doing the rasterization in software on the X server, in > spite of having more than enough acceleration capabilities, resulting in > 8fps or less (couldn't accurately measure). Well, that's expected for Nouveau, accel is not complete. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

2 2

[opensuse-factory] osc checks being run by factory-auto ...
by Stefan Dirsch 18 Mar '14

18 Mar '14

Hi Which checks are being run by this "factory-auto" user for openSUSE:Factory? One of the commands appears to be osc service localrun download_files but I'm afraid there are more to come (and fail) when trying to forward a submitrequested package. Is it possible to run these tests during 'osc ci'? BTW, when maintaining a devel project I'm feeling like a fool between accepting and forwarding to factory a valid looking submitrequest and then getting an automatic decline by this factory-auto reviewer of openSUSE:Factory. Can't this be improved, so the submit requester already get the decline? By adding factory-auto as reviewer also for the devel project maybe? Didn't try this yet. Thanks, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- 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

2 2

[opensuse-factory] Status: Distribution
by Stephan Kulow 18 Mar '14

18 Mar '14

Hi, As Factory's Quality is at the moment pretty high and factory-snapshot pretty old, I will release 13.2-Milestone0 this week. Without agenda, but with tons of changes. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] oS 13.1 Tumbleweed : LibreOffice crashes on command "File Open"
by ellanios82 16 Mar '14

16 Mar '14

Hello List, - am using XFCE4 with oS 13.1 & Tumbleweed .......... after a recent 'zypper dup' , LibreOffice crashes on command "File Open" ................ - after removing modules from LibreOffice , the culprit appears to be : libreoffice-gnome ................ when libreoffice-gnome is removed, then LibreOffice opens files all right . ................ BUT, the Menu Text is too microscopic for me to be able to read : when using XFCE4 it seems one does need libreoffice-gnome to be able to see a large enough text on Menu Bar, to be readable. ................... [ as a work-around have tried Apache Open Office : this operates OK with nice large Menu Text.] ................. regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2