http://bugzilla.novell.com/show_bug.cgi?id=1008713 http://bugzilla.novell.com/show_bug.cgi?id=1008713#c1 --- Comment #1 from rens groenewegen --- Created attachment 700763 --> http://bugzilla.novell.com/attachment.cgi?id=700763&action=edit dmesg -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1008713 http://bugzilla.novell.com/show_bug.cgi?id=1008713#c3 --- Comment #3 from rens groenewegen --- Created attachment 700765 --> http://bugzilla.novell.com/attachment.cgi?id=700765&action=edit kernel -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1008713 http://bugzilla.novell.com/show_bug.cgi?id=1008713#c9 --- Comment #9 from rens groenewegen --- Created attachment 709010 --> http://bugzilla.novell.com/attachment.cgi?id=709010&action=edit dmesg output from /var/crash another crash -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1008713 http://bugzilla.novell.com/show_bug.cgi?id=1008713#c11 --- Comment #11 from rens groenewegen --- it is up to date. please fix ? :-) Information for package kernel-default: --------------------------------------- Repository: @System Name: kernel-default Version: 4.1.32-3.1.gb236690 Arch: x86_64 Vendor: obs://build.opensuse.org/Kernel Installed: Yes Status: up-to-date -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1008713 http://bugzilla.novell.com/show_bug.cgi?id=1008713#c13 --- Comment #13 from rens groenewegen --- i am not looking anywhere. zypper is looking somewhere, or updatekit or whatever it is called. I am using kernel default, not vanilla. so I am up to date. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1008713 http://bugzilla.novell.com/show_bug.cgi?id=1008713#c15 --- Comment #15 from Takashi Iwai --- Take a look at http://download.opensuse.org/repositories/Kernel:/openSUSE-42.1/standard/x86... There, you should be able to fine something like: http://download.opensuse.org/repositories/Kernel:/openSUSE-42.1/standard/x86... I don't know why your machine doesn't take it. But the newer kernel *is* present. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1008713 http://bugzilla.novell.com/show_bug.cgi?id=1008713#c17 --- Comment #17 from rens groenewegen --- Takashi, "No. Either you didn't update properly, or your repo configuration is wrong." again, *I* do not do anything. openSUSE does. I do NOT update. your/opensuse's software does. i didnt change repos, and it happens to be a clean install. so if the repo is wrong, we apparently are also looking at a bug in the installer or whatever. What you specify as "the repo" is some OBS directory. I am fully aware, and hopefully you are too, that this is NOT the place where *every* opensuse leap42.1 gets its updates from. this is my repo list as your openSUSE software configured it for me during install: ( looks pretty regular to me.) zypper lr repo-oss Alias : repo-oss Name : openSUSE-Leap-42.1-Oss URI : http://download.opensuse.org/distribution/leap/42.1/repo/oss/ Enabled : Yes GPG Check : (r ) Yes Priority : 99 Auto-refresh : On Keep Packages : Off Type : yast2 GPG Key URI : Path Prefix : / Parent Service : Keywords : Repo Info Path : /etc/zypp/repos.d/repo-oss.repo MD Cache Path : /var/cache/zypp/raw/repo-oss 4.1.32-3.gb236690-default:itsme:[/home/itsme] = zypper lr repo-update Alias : repo-update Name : openSUSE-Leap-42.1-Update URI : http://download.opensuse.org/update/leap/42.1/oss/ Enabled : Yes GPG Check : (r ) Yes Priority : 99 Auto-refresh : On Keep Packages : Off Type : rpm-md GPG Key URI : Path Prefix : / Parent Service : Keywords : Repo Info Path : /etc/zypp/repos.d/repo-update.repo MD Cache Path : /var/cache/zypp/raw/repo-update -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1008713 http://bugzilla.novell.com/show_bug.cgi?id=1008713#c19 --- Comment #19 from Takashi Iwai --- (In reply to rens groenewegen from comment #17)

Takashi,

"No. Either you didn't update properly, or your repo configuration is wrong."

again, *I* do not do anything. openSUSE does.

I do NOT update. your/opensuse's software does. i didnt change repos, and it happens to be a clean install. so if the repo is wrong, we apparently are also looking at a bug in the installer or whatever.

Rens, please face the fact: you've installed an unofficial package from somewhere, and keep it without updating. It's not what the system does it automatically. You did something in the past manually by yourself, and it's been sticking so. zypper or the system-update mechanism is nothing more than a tool. It works wrongly unless a user uses it correctly. The openSUSE-42.1 official kernel was already updated to 4.1.36 recently. 4.1.34 had been released even before that. Please check whether you really missed something, e.g. try to run like: # zypper ref # zypper se -s kernel-default If it still doesn't show up a newer kernel, it implies either your repo seup is messed up, or something is seriously broken on your system. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1008713 http://bugzilla.novell.com/show_bug.cgi?id=1008713#c21 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rens.groenewegen@ | |xs4all.nl) --- Comment #21 from Takashi Iwai --- (In reply to rens groenewegen from comment #20)

Takashi,

like I said, *I* didnt do anything.

*fortunately* btrfs / partition crashed this morning, could not be repaired, so i had to reinstall. I will be filing a bug for that, ;-)

Well, unless it happens with the official Leap kernel, it doesn't help. The 4.1.32 kernel you've tested is an unofficial package you took from somewhere. A bug happening with an unsupported kernel, especially a very old one, is practically undebuggable.

While / after reinstalling I noticed that while installing the owncloud package, it changes default repositories maybe the reason for that. anyway, I am on 4.1.36-44-default now.

OK, that's a good news at least, and we can start debugging better now. Please clear NEEDINFO once when you get the crash again. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.