November 2015 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Warning: 20151030 went out untested
by Stephan Kulow 02 Nov '15

02 Nov '15

Hi, OBS broke a feature required for our Tumbleweed release process (https://github.com/openSUSE/open-build-service/issues/1326) so the normal release process does not work. Unfortunately our tool to handle the process wasn't prepared for that, so while it failed to release the ISOs to openQA, it did release the FTP tree - but it wasn't tested due to the lack of a NET.iso. Today it found the latest snapshot in testing (20151022) to be good, so it decided to publish what is there. This is now a bad mix betwen 1022 DVDs and 1030 FTP tree, but worse: the FTP tree is untested and your zypper dup might give you uncatched bugs ;( I can't revert that, so please zypper dup only on your own risk until told otherwise ;( 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

8 8

[opensuse-factory] Leap 42.1 is gold
by opensuse.lietuviu.kalba 02 Nov '15

02 Nov '15

Hi, Just tested it. It contains Qt 5.5.0, but as stated in https://news.opensuse.org/2015/10/28/rolling-awesome-of-the-day/ , Qt 5.5.0 brought some problems for Intel users. Almost 1000 fixes and improvements in Qt 5.5.1 not included in Leap?! I hope its not too late to do something! -- Regards, M -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 26

[opensuse-factory] [Leap_42.1] GPG keys don't get unlocked after login
by Manfred Hollstein 02 Nov '15

02 Nov '15

Hi there, in case someone else is having trouble to get the GPG keys unlocked after login, please take a look at <https://bugzilla.opensuse.org/show_bug.cgi?id=953100> I have created fixed packages in my home project. HTH, cheers. l8er manfred

1 0

[opensuse-factory] Recommended pathway from 13.2 to Leap 42
by Bob Williams 01 Nov '15

01 Nov '15

What is the recommended way to move from openSUSE 13.2 to Leap 42? Change repos and Upgrade/zypper dup or download iso and do a new installation? Bob -- Bob Williams System: Linux 3.16.7-7-desktop Distro: openSUSE 13.2 (x86_64) with KDE Development Platform: 4.14.3 Uptime: 06:00am up 7:55, 3 users, load average: 0.16, 0.05, 0.06

13 25

[opensuse-factory] Re: systemd-fstab-generator creating duplicate entries within /etc/fstab - Tumbleweed (2015-10-22)
by André Verwijs 01 Nov '15

01 Nov '15

ok :) thank you... still hoping TW is getting more stable (less crashes) witch is not the case now (unfortunately) ... André -- 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] [Leap 42.1] [LUKS password at boot]
by 0x90 01 Nov '15

01 Nov '15

Hi, I just installed leap on bare metal for the first time and ran into the problem that I can not enter the password for my encrypted partitions. To be more precise: No keyboard action possible. installation: from usb (iso x86_64 build 265) modifications: "nomodeset" and partitions, rest is default tested boot types: uefi (tried secure and normal) and bios keyboard: usb partitions: (only uefi setup): /boot/efi FAT /boot ext2 lvm (encrypted) for /, /home, swap,... history: This setup worked fine in 13.1 and 13.2. additional info: If boot parameter "silent" and "quiet" is removed, I can see on console correct anouncement of usb keyboard when replugged. So usb subsystem is recognising keyboard. Tested with different keyboards, but no interaction possible. Anybody an idea? 0x90 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 24

[opensuse-factory] openQA installation problems
by vlad 01 Nov '15

01 Nov '15

Hello, I have been trying to install openQA on a recent version of Tumbleweed on my local machine to familiarise myself with this product. While I have followed the installation instructions from the relevant web page and the accompanying video, I have run into problems and would greatly appreciate some help in resolving them. I have full console outputs saved, but have not attached same as I am not sure what the conventions for attaching attachments on this mailing list are. In essence, this is what I have done: linux-zpun:/home/vlad # zypper ar -f obs://devel:openQA/openSUSE_13.2 openQA linux-zpun:/home/vlad # zypper ar -f obs://devel:openQA:13.2/openSUSE_13.2 openQA-perl-module linux-zpun:/home/vlad # zypper in apache2. # chose(a) when prompted linux-zpun:/home/vlad # zypper in openqa linux-zpun:/home/vlad # zypper in *sass* # I found this was needed from previous attempts linux-zpun:/home/vlad # systemctl restart apache2 linux-zpun:/home/vlad # systemctl start openqa-webui linux-zpun:/home/vlad # systemctl status apache2Oct 31 19:34:56 linux-zpun openqa[30676]: Server available at http://localhost:9526/ linux-zpun:/etc/apache2/vhosts.d # ls openqa-common.inc openqa.conf.template openqa-ssl.conf.template vhost-ssl.template vhost.template linux-zpun:/etc/apache2/vhosts.d # cp openqa.conf.template openqa.conf linux-zpun:/etc/apache2/vhosts.d # systemctl restart apache2 Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details. linux-zpun:/etc/apache2/vhosts.d # systemctl status apache2 ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2015-10-31 20:03:54 EDT; 21s ago Process: 30899 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=1/FAILURE) Process: 30894 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=1/FAILURE) Main PID: 30894 (code=exited, status=1/FAILURE) Oct 31 20:03:54 linux-zpun systemd[1]: Starting The Apache Webserver... Oct 31 20:03:54 linux-zpun start_apache2[30894]: AH00526: Syntax error on line 22 of /etc/apache2/vhosts.d/openqa-common.inc: Oct 31 20:03:54 linux-zpun start_apache2[30894]: Invalid command 'Header', perhaps misspelled or defined by a module not included in the server configuration Oct 31 20:03:54 linux-zpun systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE Oct 31 20:03:54 linux-zpun start_apache2[30899]: AH00526: Syntax error on line 22 of /etc/apache2/vhosts.d/openqa-common.inc: Oct 31 20:03:54 linux-zpun start_apache2[30899]: Invalid command 'Header', perhaps misspelled or defined by a module not included in the server configuration Oct 31 20:03:54 linux-zpun systemd[1]: apache2.service: Control process exited, code=exited status=1 Oct 31 20:03:54 linux-zpun systemd[1]: Failed to start The Apache Webserver. Oct 31 20:03:54 linux-zpun systemd[1]: apache2.service: Unit entered failed state. Oct 31 20:03:54 linux-zpun systemd[1]: apache2.service: Failed with result 'exit-code'. # Note I only copied openqa.conf.template to openqa.conf, and did not touch openqa-common.inc where the apache2 error was reported. # Next I modified openqa.conf to enable 'headers' etc as per install instructions by uncommenting the a2enmod lines. linux-zpun:/etc/apache2/vhosts.d # systemctl status apache2 ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2015-10-31 20:06:55 EDT; 11s ago Process: 30950 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=1/FAILURE) Process: 30945 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=1/FAILURE) Main PID: 30945 (code=exited, status=1/FAILURE) Oct 31 20:06:55 linux-zpun systemd[1]: Starting The Apache Webserver... Oct 31 20:06:55 linux-zpun start_apache2[30945]: AH00526: Syntax error on line 15 of /etc/apache2/vhosts.d/openqa.conf: Oct 31 20:06:55 linux-zpun start_apache2[30945]: Invalid command 'a2enmod', perhaps misspelled or defined by a module not included in the server configuration Oct 31 20:06:55 linux-zpun systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE Oct 31 20:06:55 linux-zpun start_apache2[30950]: AH00526: Syntax error on line 15 of /etc/apache2/vhosts.d/openqa.conf: Oct 31 20:06:55 linux-zpun start_apache2[30950]: Invalid command 'a2enmod', perhaps misspelled or defined by a module not included in the server configuration Oct 31 20:06:55 linux-zpun systemd[1]: apache2.service: Control process exited, code=exited status=1 Oct 31 20:06:55 linux-zpun systemd[1]: Failed to start The Apache Webserver. Oct 31 20:06:55 linux-zpun systemd[1]: apache2.service: Unit entered failed state. Oct 31 20:06:55 linux-zpun systemd[1]: apache2.service: Failed with result 'exit-code'. # This step simply moved the trigger for the apache2 error to a different place. # To move on, I removed openqa.conf and applied a2enmod at the command line for each of the arguments and that worked. linux-zpun:/etc/apache2/vhosts.d # rm openqa.conf linux-zpun:/etc/apache2/vhosts.d # systemctl restart apache2 linux-zpun:/etc/apache2/vhosts.d # systemctl status apache2 ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; disabled; vendor preset: disabled) Active: active (running) since Sat 2015-10-31 20:07:48 EDT; 5s ago Process: 30950 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=1/FAILURE) Main PID: 30980 (httpd-prefork) Status: "Processing requests..." CGroup: /system.slice/apache2.service ├─30980 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d/ -DSYSTEMD -DFOREGROUND -k ... ├─30984 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d/ -DSYSTEMD -DFOREGROUND -k ... ├─30985 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d/ -DSYSTEMD -DFOREGROUND -k ... ├─30986 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d/ -DSYSTEMD -DFOREGROUND -k ... ├─30987 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d/ -DSYSTEMD -DFOREGROUND -k ... └─30988 /usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -DSYSCONFIG -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d/ -DSYSTEMD -DFOREGROUND -k ... Oct 31 20:07:48 linux-zpun systemd[1]: Starting The Apache Webserver... Oct 31 20:07:48 linux-zpun systemd[1]: Started The Apache Webserver. # Applied a2enmod at the command line for each of the arguments and that worked. linux-zpun:/etc/apache2/vhosts.d # a2enmod header linux-zpun:/etc/apache2/vhosts.d # a2enmod proxy linux-zpun:/etc/apache2/vhosts.d # a2enmod proxy_http linux-zpun:/etc/apache2/vhosts.d # a2enmod headers "headers" already present linux-zpun:/etc/apache2/vhosts.d # a2enmod a2enmod proxy_wstunnel linux-zpun:/etc/apache2/vhosts.d # systemctl restart openqa-webui linux-zpun:/etc/apache2/vhosts.d # ---------------------------------------------------------------------------------------------------- What is the convention for attaching longer outputs on this ml? What I have provided are the minimal edited commands. Anyway, until these apache2 errors are cleared up (or the workaround used is deemed successful) there probably not much point in moving on. I might add that at this point the openqa-webui basic screen was displayed on a browser at localhost:6526. Could someone from this area please advise me of possible reasons why the installation process thus far has not followed the documented approach. I am happy to provide further details or more voluminous output as required. Thank you for your assistance. Vladimir Zawalinski -- 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] systemd-fstab-generator creating duplicate entries within /etc/fstab - Tumbleweed (2015-10-22)
by André Verwijs 01 Nov '15

01 Nov '15

(generated with "journalctl -a > journal-log.txt" as root) Oct 31 20:45:56 nohostname systemd-fstab-generator[90]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab? Oct 31 20:45:56 nohostname systemd[87]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with error code 1. André I have linked 1 file to this message: * journal-log.txt (8,3 MB) hosted on Dropbox: https://db.tt/oxgdMKTx

2 1

Re: [opensuse-factory] [Leap 42.1] [no keyboard interaction in dracut] [WORKAROUND] was: [LUKS password at boot]
by stakanov＠freenet.de 01 Nov '15

01 Nov '15

p, li { white-space: pre-wrap; }In data domenica 1 novembre 2015 08:56:19, Andrei Borzenkov ha scritto: > 01.11.2015 03:35, 0x90 пишет: > > workaround: > > dracut --force --add-drivers hid_logitech_hidpp > > Please open bug report for it and mention it here. > > I'm not sure what is the "correct" solution. Including everything rather > defeats the purpose of kernel/initrd modularization. OTOH we cannot even > be sure next boot will have the same keyboard as was used during initrd > creation, so device detection is not sufficient as well. I am afraid > we'll have to bite the bullet and include all keyboard drivers, at least > in case of encrypted root. Sorry but for me I doubt it. I had done a clean reinstall with all disks erased and cmos removed to be dead sure it is "virgin". So after install of tubleweed (a part of getting the error on dublicates in fstab...that do not exist) everything worked. Once you stick in a usb device from the PC to the Hub or you change anything within the usb devices, the keyboard (branched to the hub) did loose functionality instantly. But it worked again normally if you changed directly to the usb outlet of the machine mainboard. I did lsusb recently and the only strange thing I saw was that the keyboard cherry was listet twice, but I do not know enough about usb and their controller issues to know if this is normal or not. Currently I can use the keyboard but only on the PC directly, not on the hub. The keyboards I have and that are concerned is a Cherry XT (so not brand new) and a well known MS Confort Curve 2000 (also very well known hardware). When the problem presented (identically on a 13.2 with stable kernel) it was after the update to 4.2 kernel, with the ultrabase and these two keyboards. But I had the very same problem also with Leap, so it is not bound to 4.2 afaiu. Will try to give you the outputs today. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1