November 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Thunderbird 24.1 is broken.
by Graham P Davis 08 Nov '13

08 Nov '13

Yesterday, Thunderbird 24.0.1 was upgraded(?) to 24.1 on my system. Sadly, Mozilla still haven't fixed it to pick up the correct version of Lightning plugin (2.6.2) and it stays with version 2.6.1, with which it is incompatible. Suggest 13.1 final release be with 24.0.1 until Mozilla sort out their mess. -- Graham Davis, Bracknell, Berks. openSUSE 13.1-RC2 (64-bit); KDE 4.11.2; AMD Phenom II X2 550 Processor; Kernel: 3.11.6; Video: nVidia GeForce 210 (using nouveau driver); Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306 -- 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] Window decorations change?
by Thomas Taylor 08 Nov '13

08 Nov '13

Has the "Modern" window decoration been deleted? It had the close button on the upper left corner, similar to the "laptop" decoration. It was available in RC1 but not there in RC2. Couldn't find it in get new decorations so can only assume it has been dropped for some reason. 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 -- 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] mdadm being very persistent
by Per Jessen 08 Nov '13

08 Nov '13

I've just upgraded a box running 13.1M4 to RC2 - before I did so, I noticed that mdadm was running, for some strange reason. So I stopped and disabled it. After upgrading (zypper up), mdadm was back up and running, despite: # systemctl status mdadm.service mdadm.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) I'll just deinstall it, but should it really be so persistent? -- Per Jessen, Zürich (12.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 13

[opensuse-factory] RFC: new package: wemux
by Adam Spiers 08 Nov '13

08 Nov '13

Hi all, I've just packaged wemux: https://build.opensuse.org/package/show/home:aspiers/wemux and would like to find a suitable develproject to be its home. Suggestions gratefully received! Thanks, Adam -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] Plain text restriction [Was: Testing many small file write on several filesystems]
by Archie Cobbs 07 Nov '13

07 Nov '13

Jan Engelhardt <jengelh(a)inai.de> wrote: > 14:42 ares07:~ > xfs_info . > meta-data=/dev/md7 isize=256 agcount=32, agsize=22891675 blks > = sectsz=512 attr=2 > data = bsize=4096 blocks=732533583, imaxpct=5 > = sunit=0 swidth=0 blks > naming =version 2 bsize=4096 ascii-ci=0 > log =internal bsize=4096 blocks=357682, version=2 > = sectsz=512 sunit=0 blks, lazy-count=1 > realtime =none extsz=4096 blocks=0, rtextents=0 Sorry for the following rant, I just can't stand to be silent anymore... This filesystem performance discussion is very interesting! Unfortunately, I can't read any of the reported statistics. Why are they unreadable? Because all of the emails are plain text, but rendered in Gmail in a non-fixed width font, so the columns don't line up. Why are all of the emails plain text? Because all openSUSE mailing lists require this. Why do all openSUSE mailing lists require plain text? HECK IF I KNOW!?! This is 2013. Is anyone out there still reading email using /usr/bin/mail? It sure would be nice if people could send HTML email, like the rest of the world (and every other open source project I'm involved in) has been doing for the past 15 years, so that, say, a fixed-width font could be specified for stuff that needs a fixed-width font. We could even require HTML emails to be "multipart/alternative" for those remaining 17 /usr/bin/mail users. What am I missing? -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

23 60

[opensuse-factory] x11-video-nvidiaG03 built from X11:Drivers:Video does not install
by Robert Munteanu 07 Nov '13

07 Nov '13

Hi, I'm trying to build and install the NVidia proprietary driver for some final 13.1 testing. I've zypper dup-ed my installation about one hour ago. My build process was the following: # checkout the project osc co X11:Drivers:Video nvidia-gfxG03 # build and save the RPMs sh fetch.sh osc build nvidia-gfxG03.spec cp /var/tmp/build-root/openSUSE_13.1-x86_64/home/abuild/rpmbuild/RPMS/x86_64/* . osc build x11-video-nvidiaG03.spec cp /var/tmp/build-root/openSUSE_13.1-x86_64/home/abuild/rpmbuild/RPMS/x86_64/* . # clean up unneeded kmps rm nvidia-gfxG03-kmp-default* # install using zypper sudo zypper in *.rpm At this point zypper complains that Problem: nothing provides libGL.so needed by x11-video-nvidiaG03-319.60-0.x86_64 Solution 1: do not install x11-video-nvidiaG03-319.60-0.x86_64 Solution 2: break x11-video-nvidiaG03-319.60-0.x86_64 by ignoring some of its dependencies I have no idea where to pick this from, and a rpm -q --requires x11-video-nvidiaG03 | grep -i libGL.so on 12.3 yields nothing. What do I have to do to build and install the proprietary driver? I prefer to use the packaged driver since it should provide a testing experience much closer to the 13.1 GA. Thanks, 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

1 0

[opensuse-factory] Last call for testing (before 13.1 GM)
by Alberto Planas Dominguez 07 Nov '13

07 Nov '13

Hi all, this email is the last call for help testing openSUSE before the gold master. So if you want to help with this process, this is email is for you. We are organizing the manual test using a public spreadsheet [1]. In this spreadsheet we have an small test plan (what to test) in the first column, and who is testing this in the first row. The goal of this is to have a good (in a easy and dirty way) overview of the actual test coverage, and a place to put notes and BNC bug references. If you want to help, please: 1.- Put you alias / name in the first row 2.- Download the last build [2] 3.- Pick some tests cases and test! 4.- Publish the result in the proper cell: 4.1.- Put the full name of the media (media, arch and build number) that you used to make the test 4.2.- Use green if the test is ok, or red if is not ok (yellow if you are not sure) 4.3.- If is not ok the test, please, create a bug report in BNC and put the number in the cell Thanks!!! [1] https://docs.google.com/spreadsheet/ccc?key=0AgNkaGiuxpjxdFJMa2lKVXQ5eGszYU… [2] You can use the service provided by Bernhard M. Wiedemann to the project. Please use this URLs with responsibility because this is a single server without a mirror: * DVD ** http://openqa.opensuse.org/openqa/factory/iso/openSUSE-13.1-DVD-i586-Build0… ** http://openqa.opensuse.org/openqa/factory/iso/openSUSE-13.1-DVD-x86_64-Buil… * GNOME-Live ** http://openqa.opensuse.org/openqa/factory/iso/openSUSE-13.1-GNOME-Live-i686… ** http://openqa.opensuse.org/openqa/factory/iso/openSUSE-13.1-GNOME-Live-x86_… * KDE-Live ** http://openqa.opensuse.org/openqa/factory/iso/openSUSE-13.1-KDE-Live-i686-B… ** http://openqa.opensuse.org/openqa/factory/iso/openSUSE-13.1-KDE-Live-x86_64… * NET ** http://openqa.opensuse.org/openqa/factory/iso/openSUSE-13.1-NET-i586-Build0… ** http://openqa.opensuse.org/openqa/factory/iso/openSUSE-13.1-NET-x86_64-Buil… -- 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] Going forward with Plymouth (based on dracut changes)
by Raymond Wooninck 07 Nov '13

07 Nov '13

Hi, Based on the recent changes for Dracut and making it replace mkinitrd, also has some consequences for Plymouth. Using Dracut at the moment would generate a smaller initrd file, then utilizing mkinitrd. Main reason for this is not that Dracut is so much smarter, but more that only partial Plymouth support is provided. The initrd that Dracut generated does not include the Pango libraries/modules and Font that is required to present the user with a question or comments during the boot process. In most cases this is never used, but for those users that utilize encrypted disks, this would be a major issue. This particular combination has been always a hot topic in the past and I would like to resolve it in the best way possible. As far as I can see, we have the following possibilities: 1) Drop the ask-for-password stuff from Plymouth, which would allow us to drop the additional library requirements. This would mean that the password for encrypted disks is validated before plymouth starts (all within the initrd) 2) Drop plymouth from initrd and start plymouth from disk after password, etc have been required. This would then be the task for systemd, which already has this support. 3) Try to establish a checking mechanism that implements option 2 for particular kernels/encrypted root/swap disks. For the other users there is no change. Option 2 would be easy to implement. For the others I don't know and I might have to rely on others to support me. However I would like to have your opinion on the right way forward. Thanks Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

14 21

[opensuse-factory] [13.1 RC1] - upgrade test: no network device
by Carlos E. R. 07 Nov '13

07 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm testing the offline upgrade method (DVD) from 12.3 to 13.1, in a vmplayer machine. I've hit a strange problem: no network. Aparently there is a conflict between the old network name, eth0, and the new, ens33. I had a look at yast network module (yast says the name is eth0), then rebooted. This is what the service status says now: +++······························· network.service - LSB: Configure network interfaces and set up routing Loaded: loaded (/usr/lib/systemd/system/network.service; enabled) Active: failed (Result: exit-code) since Tue 2013-10-29 00:37:31 CET; 1h 11min ago Process: 902 ExecStart=/etc/init.d/network start (code=exited, status=7) Oct 29 00:37:01 eleanor3 network[902]: Setting up network interfaces: Oct 29 00:37:01 eleanor3 network[902]: lo Oct 29 00:37:01 eleanor3 ifup[1186]: lo Oct 29 00:37:01 eleanor3 ifup[1230]: lo Oct 29 00:37:01 eleanor3 ifup[1233]: IP address: 127.0.0.1/8 Oct 29 00:37:01 eleanor3 network[902]: lo IP address: 127.0.0.1/8 Oct 29 00:37:01 eleanor3 ifup[1235]: Oct 29 00:37:01 eleanor3 network[902]: ..done ens33 Startmode is 'manual' -> skipping Oct 29 00:37:01 eleanor3 ifup[1301]: ens33 Startmode is 'manual' -> skipping Oct 29 00:37:01 eleanor3 network[902]: ..skippedWaiting for mandatory devices: eth0 Oct 29 00:37:31 eleanor3 network[902]: 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 6 5 4 3 2 1 0 Oct 29 00:37:31 eleanor3 network[902]: eth0 No interface found Oct 29 00:37:31 eleanor3 network[902]: ..failedSetting up service network . . . . . . . . . . . . ...failed Oct 29 00:37:31 eleanor3 systemd[1]: network.service: control process exited, code=exited status=7 Oct 29 00:37:31 eleanor3 systemd[1]: Failed to start LSB: Configure network interfaces and set up routing. Oct 29 00:37:31 eleanor3 systemd[1]: Unit network.service entered failed state. ·······························++- How should this be handled? If I try to delete the interface in YaST, and then add a new interface, it still says the name is eth0. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJvCJsACgkQtTMYHG2NR9UDdQCeIehd/YSBlnAFRXZok2+1UREr PM4An12cMm7q93fAsas1PrgqC3et14qJ =CY5N -----END PGP SIGNATURE-----

5 9

Re: [opensuse-factory] Automount with LDAP maps
by Malcolm Moore 06 Nov '13

06 Nov '13

The bit that puzzles me is the error If you look at the attachment, where has the first 'c' gone from the ldap servers name it should be core1.whsg.info M lynn <lynn(a)steve-ss.com> , 5/11/2013 7:30 PM: On Tue, 2013-11-05 at 17:50 +0000, Malcolm Moore wrote: > It's described in the bug Which is here: http://lists.opensuse.org/archive/opensuse-bugs/2013-10/msg03608.html Someone may now ask how you are obtaining autofs stuff from ldap. Then they'll ask you to post the config for it etc etc. HTH L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5