Hi,
Running openSUSE 12.3 RC1 64Bit.
Installed fine, but when I try to update system
I receive a notification every time:
“A Restart is Required”
“Packages : openSUSE-2013-142, openSUSE-2013-143”
[Restart]
I click on restart and it reboots OS,
but then when I try to update
it says the same “A Restart is Required” message?
How do I fix this, thanks!
JeZ+Lee
http://16bitsoft.com/V2/Images/Stuff/openSUSE12_3-RC1_ARestartIsRequired-01.png
Hmm, when I did that (in a vm like you), KDE (I assume that’s what you are showing us) and Apper notified three updates. IIRC they were all for package management. In my case Apper notified only a logout/relogin, either you had a fourth or more update requiring a restart, or something’s very different. Did you remove any packages during or after install?
Hi,
Sorry, I installed openSUSE 12.3 64Bit RC1 with KDE on current VirtualBox on a Windows 8 Pro 64Bit system.
I did a normal install which worked without issues.
I did not remove any packages during or after the installation.
Any ideas on how to get this working? I can’t update the RC1 now.
(know RC2 is due in 2 days, perhaps the issue is solved with that one)
Thanks!
JeZ+Lee
I ran “online update” last night.
It reported a conflict, and gave uninstalling the kernel as a solution. This was before it even told me what updates were available.
I bailed out. I decided that it’s best to wait for RC2. The repos may have been in a temporarily inconsistent state, as they were being readied for RC2.
I should have welcomed you to the forum. Welcome!
Mine was 64bit, in a VirtualBox VM, using a network cd, but before that had used a liveCD for first test of RC1.
This may sound a silly question, but instead of restarting, did you try cancelling the notification via the “x” button? Then just use the system rather than updating again? For the purposes of elimination… 
Hi,
This is what “Apper” shows right after a successful installation of the OS:
JeZ+Lee
http://16bitsoft.com/V2/Images/Stuff/openSUSE12_3-RC1_ApperAfterInstallationOfOS-01.png
Four updates. Yes, when I followed up with a re-install to real hardware, it was the same number, but can’t remember if re-install was required. If it was, all went well. I’m on 12.2 right now but will soon boot to 12.3 for current status re updates, and I can check the log at /var/log/zypp/history (well that’s on 12.2).
BTW, Apper is front end > PackageKit > libzypp(as used by YaST, or zypper via commandline). Apper is the only way to have notifier + updater on KDE desktop. You may already know that.
Well, looking at 12.3 now. I have three more updates notified: openSUSE-2013-142, -143, and -155. The -142 said it needed a restart, the other two didn’t respond quickly enough. So as @nrickert posted this is probably a bad time as between release upgrade, remembering this is pre-release (current release doesn’t normally do this). Also having reviewed, unusually the notify refuses to give the info again. I didn’t install any of them. Best now wait until it sorts itself out.
openSUSE-2013-142 is a kernel update to 3.7.9, and requires a restart. The others are for PolicyKit default permissions, and Grub2.
On 2013-02-26 21:56, jezlee wrote:
> How do I fix this, thanks!
It may be a non issue 
I have not installed 12.3, but normally all factory versions for years
past had fake update patches. They are not real, they are just there
so that you test updates (patches).
It should say so in the description, that it is a test patch. I’m not
saying that this is your case, but it might be.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Yes, for Milestones, but not with RC1. They are the same as the distribution repos (not available by browser until release), with real updates. I wouldn’t have wasted my time on fake updates, really! 
I have ten machines (not VMs) running 12.3RC1-KDE. Three are in daily use with real users. (I am preparing for a move from 11.4 to 12.3 at five remote sites in a few weeks.)
I have noticed three restart packages in the Online Update (text mode YaST).
The first restarts YaST after updating libzypp, before continuing with the other updates.
The second is a a reboot suggestion after updating the kernel to 3.7.9.
The third appears to be a mistake in the update package, as it suggests an unnecessary reboot (zypper ps. reports “No processes using deleted files”).
[opensuse-factory] systemd offline updates - working for anyone?](http://lists.opensuse.org/opensuse-factory/2013-02/msg00379.html)
> I have noticed three restart packages in the Online Update (text mode YaST).
> The first restarts YaST after updating libzypp, before continuing with the other updates.
openSUSE-2013-123
> The second is a a reboot suggestion after updating the kernel to 3.7.9.
openSUSE-2013-142
The third appears to be a mistake in the update package, as it suggests an unnecessary reboot (zypper ps. reports “No processes using deleted files”).
openSUSE-2013-143 (grub2)
There are now 43 12.3 Update packages; my standard KDE desktop installs 10 of them.
Yes, but -123 is quite old now. I installed that on 18 Feb.
I’m still only seeing the three new updates I mentioned yesterday. -142, -143, and -155.
│ │Name │Summary │Kind │Version ┬
│ │openSUSE-2013-103│chromium: security and bugfix update to 26.0.1383 │security │1 │
│ │openSUSE-2013-112│hamster-time-tracker: Update to version 1.03.3 │recommended│1 ┴
│ │openSUSE-2013-115│PackageKit: Fix for bnc#735864 │recommended│1 │
│ │openSUSE-2013-116│perl-Finance-Quote: Fixed typo in the .changes-file │recommended│1 │
│ i │openSUSE-2013-123│libzypp, zypper: bugfix updates │recommended│1 │
│ │openSUSE-2013-126│rubu19: replace bind_stack.patch with upstream patch │recommended│1 │
│ │openSUSE-2013-127│rubygem-devise: fixed database input validation │security │1 │
│ │openSUSE-2013-128│rubygem-rack-1_1: update to security version 1.1.6 │security │1 │
│ │openSUSE-2013-129│postgresql92: security update to 9.2.3 │security │1 │
│ │openSUSE-2013-136│jakarta-commons-httpclient: fix bnc reference in changes │recommended│1 │
│ i │openSUSE-2013-137│colord: Add AppArmor profiles to 12.3 │recommended│1 │
│ i │openSUSE-2013-140│translation-update: Update to version 12.3 │recommended│1 │
│ │openSUSE-2013-142│kernel: update to 3.7.9 │recommended│1 ┬
│ i │openSUSE-2013-143│grub2: various stability and bugfixes │recommended│1 │
│ i │openSUSE-2013-144│git: update to 1.8.1.4 │security │1 ┴
│ i │openSUSE-2013-155│polkit-default-privs: switch from localauthority to javascript based rules │security │1 │
│ │openSUSE-2013-156│pesign: fix the broken signature list when inserting signature into a signed EFI binary│recommended│1 │
│ │openSUSE-2013-157│nagios-plugins-zypper: Update to 1.45 and several fixes │recommended│1 │
│ │openSUSE-2013-30 │update-test-trivial: test the reboot needed flag │recommended│1 │
│ │openSUSE-2013-31 │flash-player: a test eula update │security │1 │
│ │openSUSE-2013-46 │update-test-trivial: test package manmager restart flag │recommended│1 │
│ │openSUSE-2013-55 │kdenlive: Update to 0.9.4 and several fixes │recommended│1 │
│ │openSUSE-2013-56 │tomoyo-tools: Update to 2.5.0-20120805 │recommended│1 │
│ │openSUSE-2013-57 │qt-creator: Update to version 2.6.1 │recommended│1 │
│ │openSUSE-2013-58 │gnote: Update to version 3.6.2 │recommended│1 │
│ │openSUSE-2013-59 │calibre: Several fixes │recommended│1 ┬
│ i │openSUSE-2013-60 │vim: Update to revision 785 │recommended│1 │
│ │openSUSE-2013-61 │rekonq: Update to version 2.1 │recommended│1 ┴
│ │openSUSE-2013-62 │seamonkey: Update to version 2.15.1 │recommended│1 │
│ │openSUSE-2013-63 │mercurial: update to version 2.4.2 │recommended│1 │
│ │openSUSE-2013-64 │NetworkManager-kde4: Several bugfixes │recommended│1 │
│ │openSUSE-2013-65 │nss_ldap: Fix segfault when using glibc-2.16 and linking with pthread │recommended│1 │
│ │openSUSE-2013-66 │PackageKit: Two bugfixes │recommended│1 │
│ │openSUSE-2013-71 │osc: Update to version 0.138.0 │recommended│1 │
│ │openSUSE-2013-78 │wireshark: update to 1.8.5 │security │1 │
│ │openSUSE-2013-84 │enlightment: update to 0.17.1 │recommended│1 │
│ │openSUSE-2013-85 │wine: update to 1.5.23 │recommended│1 │
│ │openSUSE-2013-86 │phpMyAdmin: updated to 3.5.6.0 │recommended│1 │
│ │openSUSE-2013-87 │nagios-plugins-mem: Initial update │recommended│1 │
│ │openSUSE-2013-88 │PackageKit: Two bugfixes │recommended│1 │
│ i │openSUSE-2013-95 │pulseaudio: update to 3.0 │recommended│1 ┬
│ i │openSUSE-2013-96 │cronie: fix repeated crashes │recommended│1 │
│ i │openSUSE-2013-97 │gnutls: updated to 3.0.28 │security │1 ┴
~ # zypper lr
# | Alias | Name | Enabled | Refresh
---+------------------------------+------------------------------+---------+--------
1 | 12.3-rc1.iso | 12.3-rc1 | Yes | No
2 | kde:release:410-12.3 | kde:release:410-12.3 | Yes | Yes
3 | kernel:stable-standard | kernel:stable-standard | Yes | Yes
4 | libreoffice:stable-12.2 | libreoffice:stable-12.2 | No | Yes
5 | libreoffice:unstable-factory | libreoffice:unstable-factory | Yes | Yes
6 | openSUSE-12.3-Update | openSUSE-12.3-Update | Yes | Yes
7 | packman.inode.at-suse-12.2 | Packman Repository-12.2 | No | Yes
8 | update-12.3 | update-12.3 | No | Yes
:~ # zypper lr openSUSE-12.3-Update
Alias : openSUSE-12.3-Update
Name : openSUSE-12.3-Update
URI : http://download.opensuse.org/update/12.3/
Enabled : Yes
Sorry about the formatting, hope it’s readable. The table was pasted from YaST2 (text) Online Update with Filter All.
I’m assuming you don’t have a problem, right? I’ve been regularly updating 12.3 RC1 with patches. Just installed (using Apper for testing here) the three I mentioned in my last post, followed by a reboot. BTW, to reach RC2 or the final release, without re-installing from new media, will require a dist-upgrade (zypper dup).
So my 12.3 RC1 is now fully updated as of today, wrt relevant patches. It would appear that last night’s issues have gone, and I had no further problems following the restart.
The 12.3 repos are now populating with a sizeable upgrade+downgrade+new packages (around 200 at time of posting). I assume that’s RC2. I will probably wait until it has obviously completed before upgrading.
After refreshing the repos, I decided to do a dist-upgrade (zypper dup) followed by a reboot. Once again I have a working system.
There were a number of downgrades, including a minor downgrade of the 3.7.9 kernel, so I now have three versions in the boot loader’s menu (2 x 3.7.9 and a 3.7.7). Keeping multiple versions seems to be the default operation, at least from RC1 on. Once I’m happy with the system, I can delete older versions.
KInfocentre tells me it’s 12.3, nothing more than that. The “-12.3-Update” repo is now empty (by YaST S.M.). openSUSE Download is still showing RC1 for the development release. It’s not uncommon for the project to keep RC2 as an internal release i.e. no release of ISO’s, and there is only 14 days to final release.