September 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Tumbleweed: Issues with kernel-desktop 3.11.1-29 and systemd-remount-fs service
by Matthew McKeen 29 Sep '13

29 Sep '13

After upgrading kernel-desktop from -28 to -29 my boot is halting with journalctl reporting that the systemd-remount-fs service couldn't find the UUID of my root partition on the disk. This service works fine with -28 and all other kernels previously. Has anyone else seen this bug? Thanks, Matthew McKeen -- Matthew McKeen matthew(a)mmckeen.net -- 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] 13.1 Beta YAST NFS Client failure creation failure.
by Steven Hess 29 Sep '13

29 Sep '13

Trying to create some NFS mounts in YAST hangs at 50% and does not continue or recover. Create entries to fstab but renders system unbootable even in recovery mode. I have no useful other data and am a complete newbie to testing so I can't really create a bug report against the new ruby YAST Running KDE on x64 13,1 beta System is a Dell 775 Optiflex core two duo with 3 gb ram Steven -- 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] Can't login to Typo3 4.5.30 on 13.1
by Christian Boltz 29 Sep '13

29 Sep '13

Hello, I installed Typo3 4.5.30 (also tested 6.1.3) on a new server (running 13.1 beta). The result is that I can't login to the install tool or to the backend :-( There's an interesting detail: Typo3 seems to recognize that my password is correct[1], but asks me to enter it again and again. Does someone have an idea what could be wrong? (It must be something around session handling, but phpMyAdmin and PostfixAdmin work on the same server, so it can't be a general issue.) Does someone successfully use Typo3 on 13.1 beta or Factory? Some more technical details: I'm using my "usual" apache config that works since years on multiple servers with various openSUSE releases up to 12.3. (If needed, I can provide it for download.) The access_log says (IP changed, Referrer removed) a) with correct password: 1.2.3.4 - - [28/Sep/2013:19:37:00 +0200] "POST /typo3/install/index.php HTTP/1.1" 303 - "" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) konqueror/4.11.1 Safari/537.21" 1.2.3.4 - - [28/Sep/2013:19:37:00 +0200] "GET /typo3/install/index.php?TYPO3_INSTALL%5Btype%5D=about HTTP/1.1" 200 1090 "" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) konqueror/4.11.1 Safari/537.21" b) with wrong password 1.2.3.4 - - [28/Sep/2013:19:37:04 +0200] "POST /typo3/install/index.php HTTP/1.1" 200 1162 "" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) konqueror/4.11.1 Safari/537.21" The headers of an install tool login (attemp) are also quite interesting, especially when comparing them with a working setup on 12.3. Especially note that I get 3 different Typo3InstallTool cookies on 13.1 beta, and only one on 12.3. (Domains and session keys shortened with "...") Headers from failing installtool (openSUSE 13.1 beta) *** Reply header: Cache-Control no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Connection Keep-Alive Content-Length 0 Content-Type text/html Date Sat, 28 Sep 2013 18:32:48 GMT Expires Thu, 19 Nov 1981 08:52:00 GMT Keep-Alive timeout=15, max=98 Last-Modified Sat, 28 Sep 2013 18:32:48 GMT Location http://.../typo3/install/index.php?TYPO3_INSTALL[type]=about Pragma no-cache Server Apache/2.4.6 (Linux/SUSE) Set-Cookie Typo3InstallTool=duenfn...p8ii3ufat81; path=/ Typo3InstallTool=3qqfrg19...sq4o40; path=/ Typo3InstallTool=sjobc2tcsp...upah5f1l3d4u81; path=/ X-Powered-By PHP/5.4.19 *** Request header: Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Encoding gzip, deflate Accept-Language de-de,de;q=0.8,en;q=0.5,en-gb;q=0.3 Authorization Basic ... Connection keep-alive Cookie Typo3InstallTool=8pgbgo...vsumtaj81 DNT 1 Host ... Referer http://.../typo3/install/index.php User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 Headers from working installtool (on openSUSE 12.3, same Typo3 version) *** Reply header: Cache-Control no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Connection Keep-Alive Content-Encoding gzip Content-Length 20 Content-Type text/html Date Sat, 28 Sep 2013 18:33:55 GMT Expires Thu, 19 Nov 1981 08:52:00 GMT Keep-Alive timeout=15, max=95 Last-Modified Sat, 28 Sep 2013 18:33:55 GMT Location http://.../typo3/install/index.php?TYPO3_INSTALL[type]=about Pragma no-cache Server Apache/2.2.22 (Linux/SUSE) Set-Cookie Typo3InstallTool=k97ipsdh...n0; path=/ Vary Accept-Encoding X-Powered-By PHP/5.3.17 *** Request header: Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Encoding gzip, deflate Accept-Language de-de,de;q=0.8,en;q=0.5,en-gb;q=0.3 Authorization Basic ... Connection keep-alive Cookie Typo3InstallTool=qmc4e3...pamtl0 DNT 1 Host ... Referer http://.../typo3/install/index.php User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 Regards, Christian Boltz [1] in the install tool, I don't get the "the password you entered has $hash" message, and for the backend login, the sys_log table shows a successful(!) login -- >> Man möge mich korrigieren. > Du hast es nicht anders gewollt ;-) Jaaaa, gibs mir! ;-) [> Christian Boltz und Johannes Kastl in suse-linux] -- 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] 13.1 repo is now 13.1
by Stephan Kulow 29 Sep '13

29 Sep '13

Hi, To get some testing for the 13.1 tree before RC1 is released, I set the 13.1 project to autopublish below the factory-snapshot repo - which all 13.1 installations point to. But be aware that Wolfgang reports that dbus calls timeout and I'm afraid openqa sees the same. Greetings, Stephan -- 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] testing show_bug.cgi?id=827520 fix
by Dale Ritchey 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=827520 https://bugzilla.novell.com/show_bug.cgi?id=827520#c19 Marcus Schaefer<ms(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #19 from Marcus Schaefer<ms(a)suse.com> 2013-09-27 13:10:50 UTC --- ok I can reproduce the "no space left" case and have fixed it. But I found that even with the error I have useful data in /boot. I never was able to create an empty /boot except if the image itself doesn't have a kernel installed. Because of this please check the following in your live iso: mount -o loop live.iso /mnt # below /mnt you will see a file with name "XXXX-read-only.XXX" # this is a squashfs file, mount this as well: mount -t squashfs /mnt/XXXX-read-only.XXX /mnt now check the contents of /boot inside this squashfs image ls -l /mnt/boot umount /mnt umount /mnt you have to have some useful data there. if not your image build is missing a kernel or you have custom scripts removing /boot or something I have submitted kiwi v5.05.35 to Factory (sr: 201109) to fix the reported defect but I still feel there is something different wrong in your image because of the empty /boot if so please open another bug report with: a) the information from the test mentioned in this comment b) the /var/log/boot.kiwi file to verify if the "no space" problem is fixed Thanks closing -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You reported the bug. When will we be able to test this? -- 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 - why network eth0 is named instead ens33?
by Carlos E. R. 29 Sep '13

29 Sep '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I installed 13.1 under vmplayer. On second boot, there was no network, but rcnetwork started it. However, the name is abusrd: ens33. Where is eth0? Why the change? How do I revert that change? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJG5PsACgkQtTMYHG2NR9WG7gCfS3H16eYR4dyzeMWGV6K3RID1 SgIAnR/zBAXAHnIS8gbSJlXgk9OikpLx =PudE -----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

14 29

[opensuse-factory] Something created /etc/udev/rules.d/70-persistent-net.rules ?
by Per Jessen 29 Sep '13

29 Sep '13

I have a test-system with 13.1b1 where the network interface renaming scheme seems a little inconsistent. For instance, on the first boot-up, I had eth1 and enp13s0. Now, after a few more reboots, I seem to have acquired "70-persistent-net.rules" with two renaming rules for maintaining eth0 and eth1. I simply do not remember creating this myself, but it looks likes yast is doing something to it. I would like to maintain the old naming scheme, so I'm actually happy with this, but something isn't quite right with the new scheme. -- Per Jessen, Zürich (16.2°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

1 2

[opensuse-factory] Tumbleweed and openSUSE 13.1 Look & Feel
by Ronan Arraes Jardim Chagas 28 Sep '13

28 Sep '13

Hi, By the time openSUSE 13.1 is out, will it be possible to install in Tumbleweed the openSUSE's *-branding* packages to get the official look & feel? Best regards, Ronan

4 4

Re: [opensuse-factory] Missing /usr/lib/udev/rules.d/80-btrfs.rules causes mkinitrd errors when upgrading to kernel 3.11.1-29
by Edward Reiss 28 Sep '13

28 Sep '13

I apologize for the SNAFU regarding the subject. The file /lib/mkinitrd/scripts/setup-btrfs.sh in btrfsprog currently has the following content: #!/bin/bash # #%stage: filesystem mkdir -p $tmp_mnt/etc/udev/rules.d cp /usr/lib/udev/rules.d/80-btrfs.rules $tmp_mnt/etc/udev/rules.d It should be changed to read: #!/bin/bash # #%stage: filesystem mkdir -p $tmp_mnt/etc/udev/rules.d cp /usr/lib/udev/rules.d/64-btrfs.rules $tmp_mnt/etc/udev/rules.d 64-btrfs.rules comes with udev. I verified I can run mkinitrd without errors with setup-btrfs.sh pointing to 64-btrfs.rules. -- Edward Reiss ebreiss(a)gmail.com Quis custidiet ipsos custodes? -- 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] http://forums.opensuse.org/english/get-technical-help-here/alternative-distributions-based-opensuse/tumbleweed/490727-errors-when-upgrading-kernel-4.html#post2588125
by Edward Reiss 28 Sep '13

28 Sep '13

The file /lib/mkinitrd/scripts/setup-btrfs.sh in btrfsprog currently has the following content: #!/bin/bash # #%stage: filesystem mkdir -p $tmp_mnt/etc/udev/rules.d cp /usr/lib/udev/rules.d/80-btrfs.rules $tmp_mnt/etc/udev/rules.d It should be changed to read: #!/bin/bash # #%stage: filesystem mkdir -p $tmp_mnt/etc/udev/rules.d cp /usr/lib/udev/rules.d/64-btrfs.rules $tmp_mnt/etc/udev/rules.d 64-btrfs.rules comes with udev. -- Edward Reiss ebreiss(a)gmail.com Quis custidiet ipsos custodes? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1