Running Suse 13.1.
After returning to my PC after a few days holiday neither Firefox or Chrome will now start.
My system did do a bunch of updates before I shut it down prior to going away.
If I try to run >firefox from within Konsol I get the following output :-
Can you run other gtk2 applications?
(GIMP, avidemux-gtk, kino, MPlayer, audacity, inkscape, LibreOffice, gnucash, xchat, … )
Please post your repo list:
zypper lr -d
AFAICS there haven’t been a gtk2 update for 13.1 recently.
Still, you said you installed updates before you shut down. Did you wait for the updates to finish?
Try to run “sudo zypper up” to maybe finish an aborted update.
Thanks for the quick response which I think has helpoed me to identify what could be a couple of my problems
First off I dont seem to have most of the gtk packaes you suggest to run but although Libre Office does open OK GIMP fails with
gimp: symbol lookup error: /usr/lib64/libgtk-x11-2.0.so.0: undefined symbol: g_type_check_instance_is_fundamentally_a
Now Libre Office I have tweaked thus :-
The menu-bar of Libreoffice looks ugly under KDE (Qt/Gtk conflict). But there is an easy way to fix it.Remove libreoffice-kde4 packagesInstall gtk3-engine-oxygen & gtk3-theme-engineNow, go to desktop settings > application appearance > Gtk configuration
Select oxygen-gtk in both GTK2 and 3 themes. Now, you Gtk apps will look beautiful and KDEfied.
That maybe explains why Libre Office is OK…??
However after calling up my repo list I see that I have the 13.2 repo enabled…
I was planning to do an 'upgrade' about a week ago and had begun the process by adding the 13.2 repo, but then thought better of going any further. I could have swore I had disabled the repo but apparently not...
Also a buinch of the updates (about 19) that I was offered before I went away failed to install with dependancy errors - now I think I know why :-(
So it seems that I have probably installed someeething for 13.2 which has broken FF, Chrome and GIMP etc...
Any ideas how I can find out what I might need to remove ??
Chris
All sorted!!! I did a search in yast package manager for gtk and there were about a dozen entries showing in red relating to various gtk things… my installed versions were 2.24,25-4.4.1 but showing as available were versions 2.24.23-7.1
Figuring that the latter were likely to be the older original versions that I really needed i selected them ot upgrade to the earlier version and FF, Chrome and GIMP all now open up just fine.
Thanks for prodding me in the right direction.
I haev now made double sure the 13.2 repo is disabled and never to be enabled again by using the safer method of deleting it
Not really. Actually it should be more ok if you used libreoffice-kde4 than libreoffice-gnome.
But LibreOffice probably doesn’t even use libgtk2 itself, only the themes. I’m not sure.
However after calling up my repo list I see that I have the 13.2 repo enabled…
That’s definitely a source for problems, yes.
So apparently you installed the latest gtk2 update for 13.2, which is of course incompatible with the rest of your system.
I was planning to do an ‘upgrade’ about a week ago and had begun the process by adding the 13.2 repo, but then thought better of going any further. I could have swore I had disabled the repo but apparently not…
Well, you only added the 13.2 update repo. An “upgrade” is not possible that way, you need the full oss repo as well.
Any ideas how I can find out what I might need to remove ??
First and foremost, that repo.
Then, search for gtk in YaST, in select “Update Unconditionally” for all packages that are marked red.
Or even browse through the “@System” repo and look for packages marked in red.
The easiest way to revert fully to 13.1 would probably be running “sudo zypper dup” though.
But you should also run a “sudo zypper dup --from 9” afterwards to make sure you have all necessary packages from Packman.
Thanks a lot. I used your suggestion of zypper dup which found 70 packages needing upgrade and 44 to downgrade along with switching ownership of another bundle from Suse to packman. All seems fine now.
Dunno what I was thinking really ‘upgrading’, as that is something I never ever do - be it Linux or Windows I’ve always gone for a fresh install of a newer version. Hopefully this little escapade will remind me in future to not even get tempted down that route
