Well, here I am again with upgrade problems after installing 13.1 almost one year ago. I’m seeing several problems with the system and will try to address them individually with new posts for each. But I want to at least start the discourse with this initial post.
First, I have attempted several updates to my 13.1 partition and seen several error conditions, but not having any recent experience with the installation routine, I had not noticed what was going on with the installation until the system first booted afterwards. From what I recall, even though not specifically, the first sign of failure was that my desktop fonts were enlarged. I had this problem before and tried to review my posts from a year ago but to no real avail.
Second, I notice too that my videos on Facebook were not displaying; another problem that I had had before but am sad to say is a problem currently plaguing the system.
So, seeing these anomalies, I decided to try and reapply the update wherein I began to become more aware of the installation errors that I noticed during this new attempt. The first of these were an indication that there were failed packages that did not install contained in a dialog box advising me of same. Becoming quite apprehensive at this point, I continued to reapply the updates in a most aggressive manner and have not proceeded to the point where I do not recall which steps I have taken over these last two days and am now at a point where the update procedure will not allow me to even configure my network card for downloading of packages from the online site.
And, having failed at this update for a good 5 or 6 times, I am up to a point where I notice that the Saving bootloader configuration stalls for quite a long time before completing and the system continues to where a reboot is initiated. The reboot completes to the desktop displaying the enlarged fonts which puts me on notice that the update did not go well.
I’m presently at the point in this install where I’m updating and the system wants to reboot but I have stopped it to view the details of the Actions performed and it shows to have Finished. I’m going to let this reboot complete now and will await any direction that someone may offer because I’m totally confused as to what I should do.
Thanks for any offered assistance.
You did not bother to mention what desktop??? Also useful is what video hardware and driver?
If you were using a proprietary driver in previous version did you reinstall it for the new??
On 2014-11-21 15:26, chuckenheimer wrote:
>
> Well, here I am again with upgrade problems after installing 13.1 almost
> one year ago. I’m seeing several problems with the system and will try
> to address them individually with new posts for each. But I want to at
> least start the discourse with this initial post.
Sorry, I don’t get a clear picture of what you did.
You attempted to upgrade from 13.1 to 13.2. How exactly?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Thanks for your interest.
KDE desktop with NVidia hardware - GeForce 6200 originally in 13.1 I had the proprietary drivers installed. At one point during the initial update process I saw many repositories were marked as “Remove” but change those to “Enabled” so I presume these were updated. However, at this point I am really unsure as to what state my systems is in and Yast refused to load any modules so I am unable to do anything at all.
Hope this answers your questions.
I had downloaded the .ISO image of the new 13.2 release and burned to DVD. From there I utilized the Update function.
There have been many attempts to update so far and I’m afraid that my system is so discombobulated that I am unable to perform the update correctly.
Thanks for your interest.
You probably should install them again.
But the ones for 13.1 will not work for 13.2.
However, at this point I am really unsure as to what state my systems is in and Yast refused to load any modules so I am unable to do anything at all.
You probably have some old 13.1 packages installed (likely if you enabled your 13.1 repos during the upgrade).
Please post your repo list:
zypper lr -d
I would suggest to disable all repos except the standard 4 (oss, non-oss, update, update-non-oss), and run “sudo zypper dup”.
This should at least get YaST working.
We can continue to fix your remaining problems better then.
Installing now. Enabling only those repos suggested, I was able to configure my Network adapters. That’s progress.
As you stated, I did initially enable the 13.1 repos I recognized which must have been the wrong move. I am currently waiting on the Saving bootloader configuration step and should soon be rebooted to the desktop. I’ll perform the repo list command once completed and let you know.
I should add that at the splash screen I see only the dialog that the system is trying to load 13.1 instead of what I am expecting of 13.2 and wonder why that may be.
charles@linux-o5eg:~> zypper lr -d
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
--+---------------------------+------------------------------------+---------+---------+----------+--------+-----------------------------------------------------------------+--------
1 | openSUSE-13.2-0 | openSUSE-13.2-0 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-LITE-ON_DVDRW_LH-20A1H |
2 | repo-debug | openSUSE-13.2-Debug | No | Yes | 99 | yast2 | http://download.opensuse.org/debug/distribution/13.2/repo/oss/ |
3 | repo-debug-update | openSUSE-13.2-Update-Debug | No | Yes | 99 | rpm-md | http://download.opensuse.org/debug/update/13.2/ |
4 | repo-debug-update-non-oss | openSUSE-13.2-Update-Debug-Non-Oss | No | Yes | 99 | rpm-md | http://download.opensuse.org/debug/update/13.2-non-oss/ |
5 | repo-non-oss | openSUSE-13.2-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.2/repo/non-oss/ |
6 | repo-oss | openSUSE-13.2-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.2/repo/oss/ |
7 | repo-source | openSUSE-13.2-Source | No | Yes | 99 | yast2 | http://download.opensuse.org/source/distribution/13.2/repo/oss/ |
8 | repo-update | openSUSE-13.2-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.2/ |
9 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.2-non-oss/ |
charles@linux-o5eg:~>
YaST still refuses to load any modules.
That’s normal and only cosmetical.
“openSUSE 13.1” in the boot menu is a user defined string and won’t be changed on Upgrades.
Therefore 13.2 uses just “openSUSE” by default on a fresh installation.
You can change that string in YaST->System->Boot Loader, or in /etc/default/grub.
That’s ok now.
I would suggest to add the nvidia repo in YaST->Software Repositories->Add->Community Repositories, and install the G02 driver then.
But let’s first fix YaST.
YaST still refuses to load any modules.
Does “sudo yast2” in a terminal window work?
Check that you have the packages libyui-qt6 and libyui-qt-pkg6 installed:
rpm -qa | grep libyui
If not, install them manually, with:
sudo zypper in libyui-qt6 libyui-qt-pkg6
If that doesn’t help, please post the last lines of your YaST log, preferably immediately after trying to start a module:
sudo tail /var/log/YaST2/y2log
sudo yast2 in terminal window does NOT work. I can initialize YaST from the Kickoff Application Launcher Computer tab YaST icon only.
charles@linux-o5eg:~> rpm -qa | grep libyui
libyui6-3.1.4-1.8.i586
libyui-qt6-2.46.13-2.1.9.i586
libyui-ncurses6-2.46.6-2.1.9.i586
libyui-qt-graph6-2.44.2-2.1.10.i586
libyui-ncurses-pkg6-2.46.1-2.1.9.i586
libyui-qt-pkg6-2.44.7-1.8.i586
charles@linux-o5eg:~>
charles@linux-o5eg:~> sudo tail /var/log/YaST2/y2log
root's password:
2014-11-21 15:16:45 <3> linux-o5eg(12713) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):25 cannot require yast:cannot load such file -- set at /usr/lib/ruby/vendor_ruby/2.1.0/yast/builtins.rb:1:in `require'
2014-11-21 15:16:45 <1> linux-o5eg(12713) [liby2] genericfrontend.cc(main):778 Finished YaST2 component 'y2base'
2014-11-21 15:16:45 <1> linux-o5eg(12713) [liby2] genericfrontend.cc(main):783 Exiting with client return value 'false'
2014-11-21 15:51:19 <3> linux-o5eg(17256) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):25 cannot require yast:cannot load such file -- rubygems at Unknown
2014-11-21 15:51:19 <1> linux-o5eg(17256) [liby2] genericfrontend.cc(main):575 Launched YaST2 component 'y2base' 'menu' 'ncurses'
2014-11-21 15:51:19 <1> linux-o5eg(17256) [ui-component] YUIComponentCreator.cc(createInternal):124 Creating UI component for ""
2014-11-21 15:51:19 <1> linux-o5eg(17256) [liby2] genericfrontend.cc(main):764 YAST_IS_RUNNING is yes
2014-11-21 15:51:19 <3> linux-o5eg(17256) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):25 cannot require yast:cannot load such file -- set at /usr/lib/ruby/vendor_ruby/2.1.0/yast/builtins.rb:1:in `require'
2014-11-21 15:51:19 <1> linux-o5eg(17256) [liby2] genericfrontend.cc(main):778 Finished YaST2 component 'y2base'
2014-11-21 15:51:19 <1> linux-o5eg(17256) [liby2] genericfrontend.cc(main):783 Exiting with client return value 'false'
charles@linux-o5eg:~>
charles@linux-o5eg:~> charles@linux-o5eg:~> sudo tail /var/log/YaST2/y2log
charles@linux-o5eg:~: command not found
charles@linux-o5eg:~> root's password:
> 2014-11-21 15:16:45 <3> linux-o5eg(12713) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):25 cannot require yast:cannot load such file -- set at /usr/lib/ruby/vendor_ruby/2.1.0/yast/builtins.rb:1:in `require'
bash: roots password:
2014-11-21 15:16:45 <3> linux-o5eg(12713) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):25 cannot require yast:cannot load such file -- set at /usr/lib/ruby/vendor_ruby/2.1.0/yast/builtins.rb:1:in `require: No such file or directory
charles@linux-o5eg:~> 2014-11-21 15:16:45 <1> linux-o5eg(12713) [liby2] genericfrontend.cc(main):778 Finished YaST2 component 'y2base'
bash: syntax error near unexpected token `1'
charles@linux-o5eg:~> 2014-11-21 15:16:45 <1> linux-o5eg(12713) [liby2] genericfrontend.cc(main):783 Exiting with client return value 'false'
bash: syntax error near unexpected token `1'
charles@linux-o5eg:~> 2014-11-21 15:51:19 <3> linux-o5eg(17256) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):25 cannot require yast:cannot load such file -- rubygems at Unknown
bash: syntax error near unexpected token `3'
charles@linux-o5eg:~> 2014-11-21 15:51:19 <1> linux-o5eg(17256) [liby2] genericfrontend.cc(main):575 Launched YaST2 component 'y2base' 'menu' 'ncurses'
bash: syntax error near unexpected token `1'
charles@linux-o5eg:~> 2014-11-21 15:51:19 <1> linux-o5eg(17256) [ui-component] YUIComponentCreator.cc(createInternal):124 Creating UI component for ""
bash: syntax error near unexpected token `1'
charles@linux-o5eg:~> 2014-11-21 15:51:19 <1> linux-o5eg(17256) [liby2] genericfrontend.cc(main):764 YAST_IS_RUNNING is yes
bash: syntax error near unexpected token `1'
charles@linux-o5eg:~> 2014-11-21 15:51:19 <3> linux-o5eg(17256) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):25 cannot require yast:cannot load such file -- set at /usr/lib/ruby/vendor_ruby/2.1.0/yast/builtins.rb:1:in `require'
bash: syntax error near unexpected token `3'
charles@linux-o5eg:~> 2014-11-21 15:51:19 <1> linux-o5eg(17256) [liby2] genericfrontend.cc(main):778 Finished YaST2 component 'y2base'
bash: syntax error near unexpected token `1'
charles@linux-o5eg:~> 2014-11-21 15:51:19 <1> linux-o5eg(17256) [liby2] genericfrontend.cc(main):783 Exiting with client return value 'false'
bash: syntax error near unexpected token `1'
charles@linux-o5eg:~> charles@linux-o5eg:~>
The last one was performed after a failed module loading command whereas the first one was not.
Ok, seems to be an issue with your ruby installation.
Which ruby packages do you have installed?
rpm -qa | grep ruby
charles@linux-o5eg:~> rpm -qa | grep ruby
rubygem-fast_gettext-0.8.1-2.1.3.i586
ruby2.1-rubygem-gem2rpm-0.10.1-2.2.3.i586
libstorage-ruby-2.25.18-3.1.i586
libruby2_1-2_1-2.1.3-1.1.i586
yast2-ruby-bindings-3.1.24-1.1.i586
ruby-common-2.1-2.1.noarch
ruby-2.1-1.2.i586
ruby2.1-2.1.3-1.1.i586
rubygem-ruby-dbus-0.11.0-2.1.8.i586
charles@linux-o5eg:~>
Ok, you miss ruby2.1-stdlib for some reason, which explains why you get those errors as it contains set.rb and other basic ruby libraries.
It’s strange that it is missing though, as it is required by rub2.1.
Have you chosen “break xxx by ignoring some of its dependencies” at some point?
Anyway, install it and YaST should work:
sudo zypper in ruby2.1-stdlib
No, there has been no “break xxx by ignoring some of its dependencies” and I don’t know what you are speaking about.
I performing the install and that resolved the problem with YaST, I’m happy to say. I’ll now go back to perform the other suggestions you offered. Wish me luck. 
I mean sometime during the upgrade you might have gotten a dependency conflict by YaST or zypper and chose that solution.
The point is that ruby2.1 requires ruby2.1-stdlib, so you cannot install the former without installing the latter too.
I performing the install and that resolved the problem with YaST, I’m happy to say. I’ll now go back to perform the other suggestions you offered. Wish me luck.
Ok, install the nvidia driver (G02) and your system should work better.
Regarding Flash, IIRC you have an old 32bit CPU without SSE2 support, so current Flashplayer versions won’t work.
To verify, please post the output of:
cat /proc/cpuinfo
charles@linux-o5eg:~> cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : AMD Athlon(tm) XP 3000+
stepping : 0
cpu MHz : 2156.160
cache size : 512 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips : 4312.32
clflush size : 32
cache_alignment : 32
address sizes : 34 bits physical, 32 bits virtual
power management: ts
charles@linux-o5eg:~>
I remember the SSE2 issue and I believe that an earlier version of FlashPlayer worked for me with this video adapter. Do you perchance recall that discussion?
Also, it appears to me that the G02 Nvidia drivers are already installed. The font issue is still apparent, too.
Yes.
Run this to install flash-player 10.2 from openSUSE 11.4 (should work on 13.2 as well I hope):
sudo rpm -i --force http://ftp5.gwdg.de/pub/opensuse/discontinued/distribution/11.4/repo/non-oss/suse/i586/flash-player-10.2.152.26-2.1.i586.rpm
Then lock the package so that you won’t get the newer one installed again automatically via updates:
sudo zypper al flash-player
Also, it appears to me that the G02 Nvidia drivers are already installed. The font issue is still apparent, too.
But which ones?
As mentioned, the 13.1 packages won’t work on 13.2.
rpm -qa | grep nvidia
And with the font issue you mean that the desktop fonts are enlarged?
This could be because the nvidia driver is not working and the generic fbdev is installed, using a too low resolution (640x480).
Note that if the NVIDA was already installed you may not have the correct version reinstall it. As a rule non open source stuff does not get updated.
On 2014-11-21 21:26, chuckenheimer wrote:
>
> robin_listas;2677905 Wrote:
>> You attempted to upgrade from 13.1 to 13.2. How exactly?
> I had downloaded the .ISO image of the new 13.2 release and burned to
> DVD. From there I utilized the Update function.
I assume you mean that you booted the DVD, then when prompted, you chose
“update installed system” instead of “install new system”?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-11-21 21:26, chuckenheimer wrote:
> KDE desktop with NVidia hardware - GeForce 6200 originally in 13.1 I had
> the proprietary drivers installed. At one point during the initial
> update process I saw many repositories were marked as “Remove” but
> change those to “Enabled” so I presume these were updated.
Oh my. You messed it. Don’t do that. 
I have to read the rest of the thread, but so far my suggestion is to
redo the update again, and don’t re-enable any of the disabled repos.
If you must, you have to edit the urls of each re-enabled repo so that
it points to 13.2. This step can be done more confortably before
attempting the upgrade on the running system - but yours is not running.
And this method is very problematic, so my recomendation is “don’t do it”.
And enabling the repos while they point to 13.1 breaks your system
completely.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)