On 2014-07-23 05:12 (GMT-0400) Felix Miata composed:

With core2duo and EXT4 / 64 bit host big41 I just tried upgrading with zypper, thus:

# zypper ref # zypper -v in zypper libzypp libsolv-tools rpm glibc udev systemd dracut lvm2 mdadm dmraid multipath-tools

Very quickly a segfault occurred, with triggered reboot in 90 seconds. Trying to reboot the default (only) kernel-desktop-3.15rc7 quickly triggers another segfault and 90 second later reboot about 7 seconds into boot process after reaching default target and seeing systemd-journald get a SIGTERM from PID1.

Tail of /var/log/zypp/history: # 2014-06-27 23:46:56 /var/adm/update-scripts/xterm-306-1.1-reconfigure-fonts executed 2014-07-23 04:14:46|install|htop|1.0.3-1.1|x86_64|root@big41|OSS|ccd3a9db411d98f3fb0c5378daf049285a906c5584f2bdf08bcc72098c94c4e6| # 2014-07-23 04:38:04 kernel-desktop-3.14.0-2.2.x86_64 removed ok # Additional rpm output: # warning: file /boot/initrd-3.14.0-2-desktop: remove failed: Operation not permitted # 2014-07-23 04:38:04|remove |kernel-desktop|3.14.0-2.2|x86_64|root@big41| 2014-07-23 04:39:32|install|mozilla-nss|3.16.3-166.2|x86_64||Mozilla|fe642cb44d05de25abb195c4a94b36a8ca8bf1e72610b79d7fcc5acad5404a88| 2014-07-23 04:39:33|install|firefox-esr-branding-upstream|17.0.11-1.8|x86_64|root@big41|MozillaLegacy|94d56345928b5f7f83d4150ee227e5efcd8c3fa659f657cbac7510ed521b738c| # 2014-07-23 04:40:01 firefox-esr-17.0.11-1.8.x86_64.rpm installed ok # Additional rpm output: # Unknown media type in type 'all/all' # Unknown media type in type 'all/allfiles' # Unknown media type in type 'uri/mms' # Unknown media type in type 'uri/mmst' # Unknown media type in type 'uri/mmsu' # Unknown media type in type 'uri/pnm' # Unknown media type in type 'uri/rtspt' # Unknown media type in type 'uri/rtspu' # 2014-07-23 04:40:01|install|firefox-esr|17.0.11-1.8|x86_64|root@big41|MozillaLegacy|36e5a2b761c4f38116d73917518b74f2bbfaeada1364cc57451e10539f77b2a9| 2014-07-23 04:43:41|radd |_tmpRPMcache_|dir:///var/cache/zypper/RPMS| # 2014-07-23 04:43:46 fbset-2.1-938.1.1.x86_64.rpm installed ok # Additional rpm output: # Updating /etc/sysconfig/console... # 2014-07-23 04:43:46|install|fbset|2.1-938.1.1|x86_64|root@big41|_tmpRPMcache_|| 2014-07-23 04:43:46|rremove|_tmpRPMcache_|

Fixed via chroot approximately thus: # zypper clean -a # rpm --rebuilddb # zypper ref # zypper in zypper libzypp libsolv-tools rpm # DB error thrown re llibyui* # rpm -e --nodeps libyui5-3.0.10-3.52 # zypper in zypper libzypp libsolv-tools rpm # zypper in -f glibc udev systemd dracut # zypper in mdadm dmraid lvm2 multipath-tools openSUSE-release reboot to 13.2 aka 20140721 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 23.07.2014 12:24, Freek de Kruijf wrote:

Op woensdag 23 juli 2014 04:59:56 schreef Stephan Kulow:

...

Hi,

There are still bugs shown in the test (e.g. mkfs.btrfs crashing the kernel on LVM setups), but I dared to push the button. As usual, for details - click around on https://openqa.opensuse.org/tests/overview?distri=opensuse&version=FTT

Had to change from Networkmanager to wicked to have a working network connection.

subversion-perl and some git-perl still require perl-5.18 and prevent installation of perl-5.20.

Proper bug report needed?

subversion is known - it fails to build. For that we don't need a bug report - I hope. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Quoting Ralf Haferkamp <rhafer@suse.de>:

On Wed, Jul 23, 2014 at 12:24:37PM +0200, Freek de Kruijf wrote:

...

Op woensdag 23 juli 2014 04:59:56 schreef Stephan Kulow:

...

Hi,

There are still bugs shown in the test (e.g. mkfs.btrfs crashing the kernel on LVM setups), but I dared to push the button. As usual, for details - click around on https://openqa.opensuse.org/tests/overview?distri=opensuse&version=FTT

Had to change from Networkmanager to wicked to have a working network connection. This seems to be related to the recent upgrade of libnl3 to 3.2.25. Downgrading this to 3.2.24 helped for my system. (https://bugzilla.novell.com/show_bug.cgi?id=888558)

For reference on that one: the update to 0.9.10.0 is currently pending Staging:C It seems to be in the unfortunate situation that something in Staging:C breaks a lot (bootloader; I doubt NM causing this :) ) The latest NM packages are available already in GNOME:Factory. If there is demand, I can temporary create a NM-only repo, so users willing to update can verify if this fixes the issue completely. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 23.07.2014 17:42, schrieb Marcus Meissner:

On Wed, Jul 23, 2014 at 04:59:56AM +0200, Stephan Kulow wrote:

...

Hi,

There are still bugs shown in the test (e.g. mkfs.btrfs crashing the kernel on LVM setups), but I dared to push the button. As usual, for details - click around on https://openqa.opensuse.org/tests/overview?distri=opensuse&version=FTT I am seeing yast theme issues with zypper dup (and the already written subversion and NetworkManager issues).

"yast2-branding-openSUSE-3.1.0-1.2.noarch benoetigt yast2-theme-openSUSE-any, was aber nicht angeboten werden kann."

The yast one is a real problem - nothing obsoletes it. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 23.07.2014 22:48, schrieb Guido Berhoerster:

The LightDM problem could actually have been caught via OpenQA, the xfce_lightdm_logout_login failures started between build 20140718 and 20140721. Apparently the greeter doesn't come up as autologin seems to work, I'll have a closer look at it later.

Which brings me back to my favorite topic: we need more eyes on openQA - the results are only as good as the tests and the ways they break is endless :) For staging prjs we require 100% success, which is easy to track, but for factory we generate a lot of failed tests that need review, create needles for and restart the job. 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@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 24.07.2014 14:09, Guido Berhoerster wrote:

* Stephan Kulow <coolo@suse.de> [2014-07-24 07:49]:

...

Am 23.07.2014 22:48, schrieb Guido Berhoerster:

...

The LightDM problem could actually have been caught via OpenQA, the xfce_lightdm_logout_login failures started between build 20140718 and 20140721. Apparently the greeter doesn't come up as autologin seems to work, I'll have a closer look at it later.

Which brings me back to my favorite topic: we need more eyes on openQA - the results are only as good as the tests and the ways they break is endless :)

For staging prjs we require 100% success, which is easy to track, but for factory we generate a lot of failed tests that need review, create needles for and restart the job.

So why was this not caught in Staging, the test correctly failed in this case and I suppose the change in update-desktop-files on July 1st went through staging?

Yes, but we don't have xfce tested in staging. We don't even compile it. Staging prjs have only ~2000 packages and we test gnome and kde additionally to uefi and encrypted lvm. And we only test x86_64. Once we have a factory snapshot we test more and problems then only mean the snapshot is not published. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 23.07.2014 21:00, schrieb Stefan Seyfried:

lightdm does not start; switched back to gdm in /etc/sysconfig/displaymanager and login is fine.

ypbind does not start, times out. comment out "#Type=notify" in /usr/lib/systemd/system/ypbind.service and it starts. This is probably not the correct fix :-P yeah, it's unfortunate that the fix was delayed for 2 months: https://build.opensuse.org/request/show/235555

I just called ypbind manually.

Other than that, no problems.

But -- this is a "qa tested", "Lord of the Rings" Factory. It certainly works worse for me than the old, untested Factory usually worked. Very seldom did I have *two* problems to fix after one update.

Remember that we had no updates for over 3 weeks and it was a full rebuild. But yes, I'm disappointed too - especially that we have no NetworkManager coverage at all. ypbind coverage is something that might be complicated, but NM should be possible to test at least for wired network.

OTOH, my machine had an uptime of 26 days. It has been a long time that I did not update for almost four weeks, so this might account for the accumulation of problems.

Fortunately all problems are already fixed, so next update will hopefully happen sooner :) 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@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, Jul 23, 2014 at 09:00:56PM +0200, Stefan Seyfried wrote:

Am 23.07.2014 04:59, schrieb Stephan Kulow:

...

Hi,

There are still bugs shown in the test (e.g. mkfs.btrfs crashing the kernel on LVM setups), but I dared to push the button. As usual, for details - click around on https://openqa.opensuse.org/tests/overview?distri=opensuse&version=FTT

Updated my work laptop after "zypper al libnl3*" to avoid the NetworkManager problem mentioned earlier;

lightdm does not start; switched back to gdm in /etc/sysconfig/displaymanager and login is fine.

Hi, I don't use/maintain/know much about lightdm, but trying to run it this morning with debugs on I hit this: "Failed to find session configuration lightdm-default-greeter" And as you pointed out, lightdm does not start. It seems /etc/lightdm/lightdm.conf is missing in our installation. I've no idea if this was present before, or some other configuration method was used, but adding something like the following allowed lightdm to come up correctly on my system. /etc/lightdm/lightdm.conf: -------------------------- [SeatDefaults] allow-guest=true autologin-guest=false autologin-user= greeter-session=lightdm-gtk-greeter user-session=openSUSE Not sure if the user-session is at all needed. Hope this helps a bit, Karol

Quoting Guido Berhoerster <gber@opensuse.org>:

* Stefan Seyfried <stefan.seyfried@googlemail.com> [2014-07-23 21:01]:

...

lightdm does not start; switched back to gdm in

Fix: ln -sf /etc/alternatives/lightdm-default-greeter.desktop /usr/share/xgreeters/lightdm-default-greeter.desktop

I'm currently trying to figure out why update-alternatives turns the packaged symlink into an empty file.

Guido, RPMLint might have the hints for you: [ 209s] RPMLINT report: [ 209s] =============== [ 212s] lightdm-gtk-greeter.x86_64: W: suse-alternative-generic-name-not-symlink /usr/share/xgreeters/lightdm-defaul t-greeter.desktop [ 212s] The update-alternative generic-name is not a symlink pointing to [ 212s] %{_sysconfdir}/alternatives/$(basename generic-name). [ 212s] [ 212s] lightdm-gtk-greeter.x86_64: W: no-manual-page-for-binary lightdm-gtk-greeter Please see http://en.opensuse.org/openSUSE:Packaging_Multiple_Version_guidelines on the proper usage of update-alternatives. Best regards, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Guido Berhoerster <gber@opensuse.org> writes:

thanks for the pointer, but actually it is a symlink: $ rpm2cpio lightdm-gtk-greeter-1.3.1-30.2.x86_64.rpm | cpio -ivt | grep lightdm-default-greeter

There are no symlinks in the rpm in openSUSE:Factory: $ rpm -qlvp binaries/lightdm-gtk-greeter-1.3.1-10.4.x86_64.rpm | grep ^l Maybe it was clobbered by trim-desktopfiles: [ 200s] calling /usr/lib/rpm/brp-suse.d/brp-70-trim-desktopfiles [ 200s] grep: //home/abuild/rpmbuild/BUILDROOT/lightdm-gtk-greeter-1.3.1-10.4.x86_64/usr/share/xgreeters/lightdm-default-greeter.desktop: No such file or directory [ 200s] cat: //home/abuild/rpmbuild/BUILDROOT/lightdm-gtk-greeter-1.3.1-10.4.x86_64/usr/share/xgreeters/lightdm-default-greeter.desktop: No such file or directory [ 200s] trimmed output to /home/abuild/rpmbuild/OTHER/lightdm-gtk-greeter.desktopfiles [ 200s] grep: //home/abuild/rpmbuild/BUILDROOT/lightdm-gtk-greeter-1.3.1-10.4.x86_64/usr/share/xgreeters/lightdm-default-greeter.desktop: No such file or directory [ 200s] trimmed output to /home/abuild/rpmbuild/OTHER/lightdm-gtk-greeter.desktopfiles Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, Jul 24, 2014 at 10:57:12AM +0200, Guido Berhoerster wrote:

* Stefan Seyfried <stefan.seyfried@googlemail.com> [2014-07-23 21:01]:

...

lightdm does not start; switched back to gdm in

Fix: ln -sf /etc/alternatives/lightdm-default-greeter.desktop /usr/share/xgreeters/lightdm-default-greeter.desktop

I'm currently trying to figure out why update-alternatives turns the packaged symlink into an empty file.

So /etc/lightdm/lightdm.conf is not needed then... cool, even simpler. Regards, Karol

Am 24.07.2014 04:14, schrieb Neil Rickert:

On Wed, 23 Jul 2014 04:59:56 +0200 Stephan Kulow <coolo@suse.de> wrote:

...

There are still bugs shown in the test (e.g. mkfs.btrfs crashing the kernel on LVM setups), but I dared to push the button. As usual, for details - click around on

I attempted an install, using a USB. I wrote the 64-bit DVD iso to the USB and booted it.

That got me into the installer. But it could not find the repos: ---- Unable to create repository from URL 'hd:/?device=/dev/disk/by-id/scsi-SanDisk_Cruzer_Glide_20043515110A4E41237-part2'

Details: Empty destination URI: hd:///?same-string-of-characters ----

So I opened a shell, and did:

ls -l /dev/disk/by-id

The USB did not show up there at all, though it did show up in the output of "blkid" (with UUID and LABEL).

This is what openqa found too: https://openqa.opensuse.org/tests/12989 So if you can find out more about it, that would be great. 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@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, 24 Jul 2014 07:19:33 +0200 Stephan Kulow <coolo@suse.de> wrote:

Am 24.07.2014 04:14, schrieb Neil Rickert: ...

...

That got me into the installer. But it could not find the repos: ... So if you can find out more about it, that would be great.

I've open bug 888802 on this, with an "ls" before and after "/dev/disk/by-id" got messed up. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 24 July 2014 12:00, Jiri Slaby <jslaby@suse.cz> wrote:

On 07/23/2014 04:59 AM, Stephan Kulow wrote:

...

Hi,

There are still bugs shown in the test (e.g. mkfs.btrfs crashing the kernel on LVM setups), but I dared to push the button. As usual, for details - click around on https://openqa.opensuse.org/tests/overview?distri=opensuse&version=FTT

Hi,

KNOWN

- NM did not work (0.9.10 from the current factory helps)

- subversion problems (fixed by using new ones from factory)

UNKNOWN

- DM (KDE) crashed during 'dup'. I have no evidence or logs, so I can barely create a bug. I had to finish dup on console.

This is known, or at least I was advised a while ago not to dup from within a graphical session as X gets restarted and as such kills your current session. Not sure if this is an Xorg config issue or what.

- seeing lots of these in many apps:

libGL error: dlopen /usr/lib/dri/updates/i965_dri.so failed (/usr/lib/dri/updates/i965_dri.so: sdílený objektový soubor nelze otevřít: Adresář nebo soubor neexistuje)

i.e. "no such file or directory". But according to strace, proper one is found afterwards.

This is a false positive. It is actually a warning and not an error, if you check /usr/kib/dri you'll find the required shared library. It's supposed to check to see if there is a newer version in the updates directory, and if there is use that instead of the one from the parent directory. If not use the parent one.

- yast crashes:

# LANG=en yast2 sw_single qt YaST got signal 11 at file /usr/share/YaST2/modules/PackageCallbacks.rb:2169 /sbin/yast2: line 434: 6929 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

I can confirm YaST appears to caught a very nasty flu. Regards, Andy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 07/24/2014 03:18 PM, Max Lin wrote:

...

...

- yast crashes:

# LANG=en yast2 sw_single qt YaST got signal 11 at file /usr/share/YaST2/modules/PackageCallbacks.rb:2169 /sbin/yast2: line 434: 6929 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

I can confirm YaST appears to caught a very nasty flu.

If this hapeens when you closing YaST dialog, that may a known issue and fixed in libyui-qt6-2.46.12

No, for me it happens at the beginning, after repos are updated. The windows disappears and yast crashes -- is it the use case you describe too? -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 24.07.2014 13:00, Jiri Slaby wrote:

On 07/23/2014 04:59 AM, Stephan Kulow wrote:

...

Hi,

There are still bugs shown in the test (e.g. mkfs.btrfs crashing the kernel on LVM setups), but I dared to push the button. As usual, for details - click around on https://openqa.opensuse.org/tests/overview?distri=opensuse&version=FTT

Hi,

KNOWN

- NM did not work (0.9.10 from the current factory helps)

- subversion problems (fixed by using new ones from factory)

UNKNOWN

- DM (KDE) crashed during 'dup'. I have no evidence or logs, so I can barely create a bug. I had to finish dup on console. This is the same old bug in xdm's %preun scripts ;(

- seeing lots of these in many apps:

libGL error: dlopen /usr/lib/dri/updates/i965_dri.so failed (/usr/lib/dri/updates/i965_dri.so: sdílený objektový soubor nelze otevřít: Adresář nebo soubor neexistuje) I have them like forever - I thought it's considered good style nowadays. But I connected it to chromium only so far.

i.e. "no such file or directory". But according to strace, proper one is found afterwards.

- yast crashes:

# LANG=en yast2 sw_single qt YaST got signal 11 at file /usr/share/YaST2/modules/PackageCallbacks.rb:2169 /sbin/yast2: line 434: 6929 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

I was told this is known to the yast devs, Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org