Upgraded to OpenSuse 12.1

English Install/Boot/Login
#1

Last night I logged into OpenSuse 11.4 on my laptop.

The software update icon indicated that there were updates for this version of OpenSuse.

There were 1750 packages ready to be downloaded and installed. This seemed like a complete software refresh but I thought that there must be a good reason for it.
So I selected “update” , the packages were all downloaded and installed.

Once the update was complete, I noticed that parts of the Gnome desktop were no longer working. For example, I could not select the usual “Shutdown” button and the Gnome terminal could not be accessed. So I opened the 32-bit Linux terminal and issued the shutdown command.

When I restarted the machine, the GRUB startup menu listed two basic options:

OpenSuse 12.1 Milestone5-3.0.0.4
FAILSAFE OpenSuse Milestone5-3.0.0.4

So it looks as though I am running a pre-release version of OpenSuse 12.1 !!!

The standard boot option does not work. It displays the regular .jpg image background but does not get as far as a login screen.

The FAILSAFE option does work. I can boot into GNOME session and login successfully. Here is the output from uname:

uname -a

Linux ferrari.shoreham-beach.net 3.0.0-4-desktop #1 SMP PREEMPT Thu Aug 18 09:38:15 UTC 2011 (f25ce3e) x86_64 x86_64 x86_64 GNU/Linux

I have been able to look at the log files:

(1) Gnome errors in /var/log/messages when standard bootup option selected:

p 1 10:33:35 ferrari gnome-session[2057]: WARNING: Could not parse desktop file /etc/xdg/autostart/ksmolt-autostart.desktop: Invalid key name: X-KDE-autostart-condition$e]
Sep 1 10:33:35 ferrari gnome-session[2057]: WARNING: could not read /etc/xdg/autostart/ksmolt-autostart.desktop
Sep 1 10:33:39 ferrari gnome-session[2057]: WARNING: Application ‘gsettings-data-convert.desktop’ killed by signal
Sep 1 10:33:40 ferrari gnome-session[2057]: WARNING: Application ‘gsettings-data-convert.desktop’ killed by signal
Sep 1 10:33:40 ferrari gnome-session[2057]: WARNING: App ‘gsettings-data-convert.desktop’ respawning too quickly
Sep 1 10:33:40 ferrari gnome-session[2057]: WARNING: Error on restarting session managed app: Component ‘gsettings-data-convert.desktop’ crashing too quickly
Sep 1 10:33:44 ferrari gnome-session[2057]: WARNING: Failed to start app: Unable to start application: Failed to execute child process “beagled” (No such file or directory)

(2) (1) Gnome errors in /var/log/messages when FAILSAFE bootup option selected:

grep gnome-session /var/log/messages

Sep 1 11:10:34 ferrari gnome-session[2274]: WARNING: Session ‘gnome’ runnable check failed: Exited with code 1
Sep 1 11:10:34 ferrari gnome-session[2274]: WARNING: Could not parse desktop file /etc/xdg/autostart/ksmolt-autostart.desktop: Invalid key name: X-KDE-autostart-condition$e]
Sep 1 11:10:34 ferrari gnome-session[2274]: WARNING: could not read /etc/xdg/autostart/ksmolt-autostart.desktop
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: Application ‘gsettings-data-convert.desktop’ killed by signal
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: Application ‘gsettings-data-convert.desktop’ killed by signal
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: App ‘gsettings-data-convert.desktop’ respawning too quickly
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: Error on restarting session managed app: Component ‘gsettings-data-convert.desktop’ crashing too quickly
Sep 1 11:10:42 ferrari gnome-session[2274]: WARNING: Failed to start app: Unable to start application: Failed to execute child process “beagled” (No such file or directory)
ferr

Sep 1 11:10:37 ferrari kernel: 43.257192] gsettings-data-[2508]: segfault at 18 ip 00007ff0430f9aa2 sp 00007fffa55346a0 error 4 in libgio-2.0.so.0.2914.0[7ff04305a000+13f000]
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: Application ‘gsettings-data-convert.desktop’ killed by signal
Sep 1 11:10:37 ferrari kernel: 43.623063] gsettings-data-[2666]: segfault at 18 ip 00007f6dadb9caa2 sp 00007fffa29df7e0 error 4 in libgio-2.0.so.0.2914.0[7f6dadafd000+13f000]
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: Application ‘gsettings-data-convert.desktop’ killed by signal
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: App ‘gsettings-data-convert.desktop’ respawning too quickly
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: Error on restarting session managed app: Component ‘gsettings-data-convert.desktop’ crashing too quickly
Sep 1 11:10:40 ferrari dbus[1052]: [system] Activating service name=‘org.freedesktop.RealtimeKit1’ (using servicehelper)
Sep 1 11:10:40 ferrari dbus[1052]: [system] Successfully activated service ‘org.freedesktop.RealtimeKit1’

If I tail the log file for my current FAILSAFE session, I get a bit more detail:

Sep 1 11:10:37 ferrari kernel: 43.257192] gsettings-data-[2508]: segfault at 18 ip 00007ff0430f9aa2 sp 00007fffa55346a0 error 4 in libgio-2.0.so.0.2914.0[7ff04305a000+13f000]
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: Application ‘gsettings-data-convert.desktop’ killed by signal
Sep 1 11:10:37 ferrari kernel: 43.623063] gsettings-data-[2666]: segfault at 18 ip 00007f6dadb9caa2 sp 00007fffa29df7e0 error 4 in libgio-2.0.so.0.2914.0[7f6dadafd000+13f000]
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: Application ‘gsettings-data-convert.desktop’ killed by signal
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: App ‘gsettings-data-convert.desktop’ respawning too quickly
Sep 1 11:10:37 ferrari gnome-session[2274]: WARNING: Error on restarting session managed app: Component ‘gsettings-data-convert.desktop’ crashing too quickly
Sep 1 11:10:40 ferrari dbus[1052]: [system] Activating service name=‘org.freedesktop.RealtimeKit1’ (using servicehelper)
Sep 1 11:10:40 ferrari dbus[1052]: [system] Successfully activated service ‘org.freedesktop.RealtimeKit1’

So I think that I can say that there is definitely a problem relating to initialising the GNOME desktop.

QUESTIONS:
(1) I have gone into Yast and checked my software repositories. As far as I can see, they all relate to version 11.4.
So why did I get this upgrade to version 12.1 ??

(2) Is there anything that can be done to fix the problems with Gnome? Should I reinstall version 11.4 ??

Regards,

Bill Harpley

#2

On 09/01/2011 01:16 PM, billharpley wrote:

> QUESTIONS:
> (1) I have gone into Yast and checked my software repositories. As far
> as I can see, they all relate to version 11.4.
> So why did I get this upgrade to version 12.1 ??

please show us the output of entering the following into a terminal


zypper lr -d

and copy/paste the output back to this thread using the instructions
here: http://goo.gl/i3wnr

> (2) Is there anything that can be done to fix the problems with Gnome?

probably…

> Should I reinstall version 11.4 ??

maybe but NOT yet, but i would advise you to do three things while we
look at your repos:

-STOP using package kit, it is broken

-when you get back to reasonable: always use YaST Online Updater (aka:
YOU) instead of packagekit

-never expect more than a few (say six or so) packages available in YOU
at one time…usually time is NOT critical, instead of approving
whatever it suggests think…and, ASK first because it is easier to
avoid a problem than to fix it…

–
DD Caveat
openSUSE®, the “German Engineered Automobile” of operating systems!

#3 

billh@ferrari:~> zypper lr -d
# | Alias                  | Name                       | Enabled | Refresh | Priority | Type   | URI                                                                                  | Service
--+------------------------+----------------------------+---------+---------+----------+--------+--------------------------------------------------------------------------------------+--------
1 | openSUSE-11.4-11.4-0   | openSUSE-11.4-11.4-0       | Yes     | No      |   99     | yast2  | cd:///?devices=/dev/disk/by-id/ata-MATSHITADVD-RAM_UJ-845S                           |        
2 | openSUSE:Factory       | openSUSE:Factory           | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/factory/repo/oss/                                       |        
3 | repo-debug             | openSUSE-11.4-Debug        | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/distribution/11.4/repo/oss/                       |        
4 | repo-debug-update      | openSUSE-11.4-Update-Debug | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/11.4/                                      |        
5 | repo-non-oss           | openSUSE-11.4-Non-Oss      | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.4/repo/non-oss/                         |        
6 | repo-oss               | openSUSE-11.4-Oss          | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.4/repo/oss/                             |        
7 | repo-source            | openSUSE-11.4-Source       | No      | Yes     |   99     | NONE   | http://download.opensuse.org/source/distribution/11.4/repo/oss/                      |        
8 | repo-update            | openSUSE-11.4-Update       | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/11.4/                                            |        
9 | server:database:STABLE | server:database:STABLE     | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/server:/database:/STABLE/openSUSE_Factory/ |
#4

You have factory which can cause problems and certainly can have a huge number of updates at a given time. Do you really need factory to be an active repo?

#5

On 09/01/2011 04:46 PM, billharpley wrote:
>
> Code:
> --------------------
>
> billh@ferrari:~> zypper lr -d
> # | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
> --±-----------------------±---------------------------±--------±--------±---------±-------±-------------------------------------------------------------------------------------±-------
> 1 | openSUSE-11.4-11.4-0 | openSUSE-11.4-11.4-0 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-MATSHITADVD-RAM_UJ-845S |
> 2 | openSUSE:Factory | openSUSE:Factory | Yes | Yes | 99 | yast2 | http://download.opensuse.org/factory/repo/oss/ |
> 3 | repo-debug | openSUSE-11.4-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/11.4/repo/oss/ |
> 4 | repo-debug-update | openSUSE-11.4-Update-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/11.4/ |
> 5 | repo-non-oss | openSUSE-11.4-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.4/repo/non-oss/ |
> 6 | repo-oss | openSUSE-11.4-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.4/repo/oss/ |
> 7 | repo-source | openSUSE-11.4-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/11.4/repo/oss/ |
> 8 | repo-update | openSUSE-11.4-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/11.4/ |
> 9 | server:database:STABLE | server:database:STABLE | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/server:/database:/STABLE/openSUSE_Factory/ |
>
> --------------------
>
>

ok, the main problem here is your inclusion of the Factory
repo…factory is always where the next version of openSUSE is ‘built’…

so, now you machine is filled with a mixture of 11.4 and 12.1, a 12.1 at
some unknown state…that is, that 12.1 M5 (milestone five) is now
available for brave leading edge software testers at
http://software.opensuse.org/developer/en

but, that is a ‘snapshot’ of the factory repo as it stood at a moment in
time…a moment when it was predicted that all the pieces meshed
together, more or less…

but, exactly what existed at the moment you tapped into Factory is not
at the M5 moment, so yours could be a real mismash of packages not
expected to be anywhere near stable (two different developers might have
just patched two different bits which just happend to be totally
incompatible…

so, disable Factory…and, my best advice is never enable it again for
your day-to-day system (aka: production system)…if you want to do
software testing do it in a ‘sandbox’ where it can eat your photos,
music, etc etc etc…

so, if you want to get back to 11.4, you need to do this, at least
(repos are numbered as above) set/reset them as:

enable refresh
1 Yes No
2 No No
3 No No
4 No No
5 Yes No
6 Yes No
7 No No
8 Yes Yes
9 No No

then, hmmm…i think we need a zypper guru BEFORE you do this, to say
if it is ok, or maybe something else should be done (CARL?)–read the
caveat below my sig BEFORE beginning!!

oh, do you have a backup of all your movies, music, photos, emails, etc
etc etc??

in a terminal do the following one at a time and do NOT touch the
machine until the process is over and the prompt returns…


su -       <do not forget the " -" and give root password when asked
zypper clean --all
rpmdb --rebuilddb
zypper ref
zypper up

again, i suggest you wait for someone else to check that i’m telling you
right…

if all goes well you should end with a fully functioning and updated 11.4

oh, ask yourself how factory got enabled! and read the paragraph
beginnning with “IMPORTANT” in this posting: http://tinyurl.com/33qc9vu

–
DD Caveat
openSUSE®, the “German Engineered Automobile” of operating systems!

#6

I think you do a zypper dup not a zypper up in this case but I’m not certain.

#7

On 09/01/2011 06:06 PM, gogalthorp wrote:
>
> I think you do a zypper dup not a zypper up in this case but I’m not
> certain.

you are right! (thanks) it should go:


su -       <do not forget the " -" and give root password when asked
zypper clean --all
rpmdb --rebuilddb
zypper ref
zypper dup

anyone else???

–
DD
Caveat-Hardware-Software
openSUSE®, the “German Engineered Automobile” of operating systems!

#8

It looks like you guys are doing just fine

Good advice

But I suspect a new install is on the table, due to limited understanding from the OP

#9

Thanks for all the help so far.

As for how the Factory repository came to be in my configuration, the only thing that I can think of is that I could not find ‘mysqladmin’ on my system.
So I looked on the forums and there was a posting about this very issue.

The responder recommended MySQL WorkBench and kindly provided a link to it in one of the OpenSuse repositories.
So I downloaded and installed the package, though I was not aware that it added a new repository to my configuration.

With regard to the current problem, I have changed the attributes of the software repositories as recommended:

enable refresh
1 Yes No
2 No No
3 No No
4 No No
5 Yes No
6 Yes No
7 No No
8 Yes Yes
9 No No

I then run the recommended commands as root:
zypper clean --all
rpmdb --rebuilddb
zypper ref
zypper dup

This started a process of going through all of the installed packages, asking me which ones to keep and which ones to deinstall.

As I can only guess at the correct answers, I decided to cancel about half-way through the process.

So unless anybody has any more good ideas, a fresh installation of 11.4 is the way forward.

#10

I decided to cancel about half-way through the process.
Bad Idea

Suggest a re-install and be more careful next time

#11

On 09/02/2011 09:46 PM, caf4926 wrote:
>
> Suggest a re-install

+1

> and be more careful next time

+1 +1

–
DD

#12

I have just done a clean reinstall and everything is up and running again.
This is the page where I found a link to MySQL WorkBench:

[opensuse-factory] Re: No more mysql-administrator in 11.4?](http://lists.opensuse.org/opensuse-factory/2011-02/msg00699.html)

This takes me to a page on OpenSuse Factory.

Last time, I selected the “One Click install” option. This time I just downloaded the package and did a manual install.

Thanks to all you guys for your help.

#13

Little problem to use factory for a single package if needed but it should not be left active unless you test alpha software for fun.

#14

On 09/03/2011 12:06 AM, billharpley wrote:
>
> This time I just downloaded the package and did a manual install.

that works! (as you have seen) and, there are alternatives:

  1. you can one click and the script gives you the chance to say you do
    NOT want to keep the repo enabled after install

  2. you can one click and afterwards go into YaST Software Repositories
    and either delete the repo or disable it (and stop it from refreshing)

  3. if you click in a browser on a FILE (not the one click link) to
    download it, you should be offered the choice to either save the file or
    install it, if you elect to install it YaST will do the installing for
    you (and not the one-click script)

  4. you can download it and then use YaST to install it

lots of ways to skin this cat and not poison the system

–
DD
Caveat