Is Gnome 3 broken (Tumbleweed)?

English Install/Boot/Login
#1

I did a “zypper dup” this morning.

I just tried to login to Gnome, and I get the “Something has gone wrong” screen.

The “zypper dup” downgraded several packages to those for 3.10. As best I recall, they were all “gtk3” related. I’m guessing that’s the cause of the problem.

I did a search for “gtk3” in Yast Software Management, and attempted to upgrade those 3.10 packages back to 3.12, but got a chain of dependency conflicts. (I could probably tell it to ignore the conflicts for Vietnamese language, and maybe that would then work).

I’m guessing that something went wrong with the dependency lists.

Note that I mainly use KDE, so this is not a critical problem for me.

#2

Bear in mind I’m on Tumbleweed KDE and ok here, where my system is showing these installed today from these repos:

2014-05-16 10:30:26|install|gtk3-data|3.10.4-12.1|noarch||openSUSE Current OSS updates
...
2014-05-16 10:30:29|install|gtk3-immodule-amharic|3.10.4-12.1|x86_64||openSUSE Current OSS updates
2014-05-16 10:30:30|install|gtk3-immodule-inuktitut|3.10.4-12.1|x86_64||openSUSE Current OSS updates
2014-05-16 10:30:30|install|gtk3-immodule-thai|3.10.4-12.1|x86_64||openSUSE Current OSS updates
2014-05-16 10:30:31|install|gtk3-immodule-vietnamese|3.10.4-12.1|x86_64||openSUSE Current OSS updates

From YaST, the last four require “gtk3 = 3.10.4” and “gtk3-tools” which happens to be at 3.12

HTH in some way. :slight_smile:

#3

Yes, that’s about what I am seeing as installed. That 3.10 and 3.12 mix looks wrong, and is probably why Gnome is crashing for me.

KDE is fine, however.

#4

Yes KDE is fine, and so are e.g. SeaMonkey, Firefox, LO, and Gimp. Interestingly pavucontrol (usually looks like a gtk app) fails to open with following error:

pavucontrol: symbol lookup error: /usr/lib64/libgiomm-2.4.so.1: undefined symbol: g_notification_get_type
#5

Those packages are back to 3.12 now, and for example the above “pavucontrol” error here has gone, so I hope your “crashes” have ceased.

#6

Well, SeaMonkey, Firefox, LO, and Gimp all use GTK2, that’s why they were not affected. Whereas pavucontrol uses GTK3.

IIRC, the exactly same problem existed about a year ago, when GNOME was upgraded to 3.10 in Tumbleweed. Probably branding-related again.

#7

I’m running “zypper dup” right now. I’ll check when that is done.

#8

I thought they might be GTK2, but didn’t realize pavucontrol was different. Now after a more careful look I see it has the flatter, cleaner style of GTK3 :|.

Oh yes, branding continues to flip-flop.

#9

After running updates (“zypper dup”) this morning, I rechecked. And the “gtk3” stuff was still at version 3.10.

So I didn’t bother to try Gnome.

Instead, I changed the Tumbleweed and Packman-Tumbleweed repos to priority 98. Then I did “zypper dup” again. There were 96 changes made, due to that repo priority change.

After that, the “gtk3” packages looked good. So I tried Gnome, and it is now fine.

Maybe those priority changes need to be in the documentation for Tumbleweed.

#10

Yes, maybe.
But consused already critizised me for advising this last year… :wink:

You could switch to the GTK/GNOME upstream branding instead of the openSUSE one. That’s the Tumbleweed maintainer’s advice by the way.
This should work with equal priorities. AFAICS the problem is mainly related to gio-branding, so install gio-branding-upstream.

As I see it, the problem is again that the openSUSE branding packages in Tumbleweed have a lower revision number than in standard 13.1 (and same version, i.e. 13.1). But the 13.1 branding will prevent the upgrade of the libraries (libgio f.e.) to the higher Tumbleweed versions resulting in an incompatible mix.

Just like it was last year.

#11

Yes, with an “only required by user @nrickert and his Tumbleweed version”. lol!

#12

Because it’s not the recommended way to run Tumbleweed. Users can and do ignore recommendations on there own system. That doesn’t change the overall recommendation. :slight_smile:

Why did my “zypper dup” catch all the latest updates with equal priorities, and nrickert’s didn’t? If I had to guess, his system contains modifications not applied to mine or many others.

e.g. installed without a fuss:

~> rpm -q gio-branding-openSUSE
gio-branding-openSUSE-13.1-2.1.noarch

#13

We had this discussion last year already.
So you still think the recommended way to run Tumbleweed is to have a broken system? :wink:

This problem is obvious just by looking at the packages in the repos. “zypper dup” (with equal priorities) will break gtk3 at the moment because it has to downgrade libgio to the 13.1 version because of the dependencies, whereas libgtk-3 will be installed from Tumbleweed because it has a higher version there.

Why did my “zypper dup” catch all the latest updates with equal priorities, and nrickert’s didn’t? If I had to guess, his system contains modifications not applied to mine or many others.

Maybe you have the upstream branding installed, as already mentioned?

#14

Hm, but 13.1 contains a higher version:
rpm -q gio-branding-openSUSE
gio-branding-openSUSE-13.1-2.13.1.noarch

Why didn’t you get this then?

Maybe the problem is restricted to nrickert’s system, I don’t know.

#15

I didn’t do anything special.

I did install: KDE, Gnome, XFCE, LXDE, Latex, all browsers in the standard repos – not too much else.

#16

Going back to your comment about “zypper dup” initially not catching the latest 3.10 → 3.12 changes, mine are shown amongst this log section (hex removed for readability):

2014-05-18 13:37:24|install|gio-branding-openSUSE|13.1-2.1|noarch||Tumbleweed|
2014-05-18 13:37:26|install|libgio-2_0-0|2.40.0-2.6|x86_64||Tumbleweed|
2014-05-18 13:37:29|install|gtk3-data|3.12.1-2.8|noarch||Tumbleweed|
2014-05-18 13:37:30|install|libgtk-3-0|3.12.1-2.8|x86_64||Tumbleweed|
2014-05-18 13:37:32|install|gtk3-immodule-amharic|3.12.1-2.8|x86_64||Tumbleweed|
2014-05-18 13:37:33|install|gtk3-immodule-inuktitut|3.12.1-2.8|x86_64||Tumbleweed|
2014-05-18 13:37:34|install|gtk3-immodule-thai|3.12.1-2.8|x86_64||Tumbleweed|
2014-05-18 13:37:35|install|gtk3-immodule-vietnamese|3.12.1-2.8|x86_64||Tumbleweed|
2014-05-18 13:37:35|install|gtk3-branding-openSUSE|13.1-2.1|noarch||Tumbleweed|

I don’t see any 3.10 stuff there.

#17

I’m not sure what’s the difference.

After I changed the repo priorities, here is part of what I saw (with “zypper -v dup”):


The following 16 packages are going to be upgraded:
  flash-player              11.2.202.356-46.1 -> 11.2.202.359-50.1
  flash-player-gnome        11.2.202.356-46.1 -> 11.2.202.359-50.1
  flash-player-kde4         11.2.202.356-46.1 -> 11.2.202.359-50.1
  glib2-devel               2.38.2-8.2 -> 2.40.0-2.6              
  glib2-tools               2.38.2-8.2 -> 2.40.0-2.6              
  gtk3-data                 3.10.4-12.1 -> 3.12.1-2.8             
  gtk3-immodule-amharic     3.10.4-12.1 -> 3.12.1-2.8             
  gtk3-immodule-inuktitut   3.10.4-12.1 -> 3.12.1-2.8             
  gtk3-immodule-thai        3.10.4-12.1 -> 3.12.1-2.8             
  gtk3-immodule-vietnamese  3.10.4-12.1 -> 3.12.1-2.8             
  libgio-2_0-0              2.38.2-8.2 -> 2.40.0-2.6              
  libglib-2_0-0             2.38.2-8.2 -> 2.40.0-2.6              
  libgmodule-2_0-0          2.38.2-8.2 -> 2.40.0-2.6              
  libgobject-2_0-0          2.38.2-8.2 -> 2.40.0-2.6              
  libgthread-2_0-0          2.38.2-8.2 -> 2.40.0-2.6              
  libgtk-3-0                3.10.4-12.1 -> 3.12.1-2.8             

The following 78 packages are going to be downgraded:
  branding-openSUSE                     13.1-10.4.13 -> 13.1-4.11            
  digikam                               3.5.0-4.1 -> 3.5.0-3.31              
  digikam-doc                           3.5.0-4.1 -> 3.5.0-3.31              
  dynamic-wallpaper-branding-openSUSE   13.1-10.4.13 -> 13.1-4.11            
  gfxboot-branding-openSUSE             13.1-10.4.13 -> 13.1-4.11            
  gio-branding-openSUSE                 13.1-2.13.1 -> 13.1-2.1              
  gnome-js-common                       0.1.2-13.1.2 -> 0.1.2-2.1            
  gnome-menus-branding-openSUSE         13.1-2.2.2 -> 13.1-2.1               
  grub2-branding-openSUSE               13.1-10.4.13 -> 13.1-4.11            
  gtk2-engines                          2.20.2-16.1.4 -> 2.20.2-2.5          
  gtk2-theme-clearlooks                 2.20.2-16.1.4 -> 2.20.2-2.5
  gtk2-theme-crux                       2.20.2-16.1.4 -> 2.20.2-2.5          
  gtk2-theme-industrial                 2.20.2-16.1.4 -> 2.20.2-2.5          
  gtk2-theme-mist                       2.20.2-16.1.4 -> 2.20.2-2.5          
  gtk2-theme-redmond95                  2.20.2-16.1.4 -> 2.20.2-2.5          
  gtk2-theme-thinice                    2.20.2-16.1.4 -> 2.20.2-2.5          
  gtk3-branding-openSUSE                13.1-2.4.2 -> 13.1-2.1               
  gtkspell3-lang                        3.0.3-2.4.1 -> 3.0.3-2.1             
  hicolor-icon-theme-branding-openSUSE  13.1-2.1.2 -> 13.1-2.1               
  kde4-kgreeter-plugins                 4.11.9-111.1 -> 4.11.8-3.14          
  kdebase4-openSUSE                     13.1-6.9.11 -> 13.1-2.19             
  kdebase4-workspace                    4.11.9-111.1 -> 4.11.8-3.14          
  kdebase4-workspace-branding-openSUSE  13.1-6.9.11 -> 13.1-2.19             
  kdebase4-workspace-ksysguardd         4.11.9-111.1 -> 4.11.8-3.14          
  kdebase4-workspace-liboxygenstyle     4.11.9-111.1 -> 4.11.8-3.14          
  kdebase4-workspace-plasma-calendar    4.11.9-111.1 -> 4.11.8-3.14          
  kdm                                   4.11.9-111.1 -> 4.11.8-3.14          
  kdm-branding-openSUSE                 13.1-10.4.13 -> 13.1-4.1

I cut the output short at that point, to not swamp readers.

There seemed to be a lot of packages that were “downgraded”, meaning that the Tumbleweed version number was lower than the version number in the standard 13.1 repos.

#18

On 05/19/2014 12:46 PM, nrickert pecked at the keyboard and wrote:
> consused;2644176 Wrote:
>> Going back to your comment about “zypper dup” initially not catching the
>> latest 3.10 → 3.12 changes, mine are shown amongst this log section
>> (hex removed for readability):
> Code:
> --------------------
> > > 2014-05-18 13:37:24|install|gio-branding-openSUSE|13.1-2.1|noarch||Tumbleweed|
> > 2014-05-18 13:37:26|install|libgio-2_0-0|2.40.0-2.6|x86_64||Tumbleweed|
> > 2014-05-18 13:37:29|install|gtk3-data|3.12.1-2.8|noarch||Tumbleweed|
> > 2014-05-18 13:37:30|install|libgtk-3-0|3.12.1-2.8|x86_64||Tumbleweed|
> > 2014-05-18 13:37:32|install|gtk3-immodule-amharic|3.12.1-2.8|x86_64||Tumbleweed|
> > 2014-05-18 13:37:33|install|gtk3-immodule-inuktitut|3.12.1-2.8|x86_64||Tumbleweed|
> > 2014-05-18 13:37:34|install|gtk3-immodule-thai|3.12.1-2.8|x86_64||Tumbleweed|
> > 2014-05-18 13:37:35|install|gtk3-immodule-vietnamese|3.12.1-2.8|x86_64||Tumbleweed|
> > 2014-05-18 13:37:35|install|gtk3-branding-openSUSE|13.1-2.1|noarch||Tumbleweed|
> --------------------
>> I don’t see any 3.10 stuff there.
> I’m not sure what’s the difference.
>
> After I changed the repo priorities, here is part of what I saw (with
> “zypper -v dup”):
>
> Code:
> --------------------
>
> The following 16 packages are going to be upgraded:
> flash-player 11.2.202.356-46.1 → 11.2.202.359-50.1
> flash-player-gnome 11.2.202.356-46.1 → 11.2.202.359-50.1
> flash-player-kde4 11.2.202.356-46.1 → 11.2.202.359-50.1
> glib2-devel 2.38.2-8.2 → 2.40.0-2.6
> glib2-tools 2.38.2-8.2 → 2.40.0-2.6
> gtk3-data 3.10.4-12.1 → 3.12.1-2.8
> gtk3-immodule-amharic 3.10.4-12.1 → 3.12.1-2.8
> gtk3-immodule-inuktitut 3.10.4-12.1 → 3.12.1-2.8
> gtk3-immodule-thai 3.10.4-12.1 → 3.12.1-2.8
> gtk3-immodule-vietnamese 3.10.4-12.1 → 3.12.1-2.8
> libgio-2_0-0 2.38.2-8.2 → 2.40.0-2.6
> libglib-2_0-0 2.38.2-8.2 → 2.40.0-2.6
> libgmodule-2_0-0 2.38.2-8.2 → 2.40.0-2.6
> libgobject-2_0-0 2.38.2-8.2 → 2.40.0-2.6
> libgthread-2_0-0 2.38.2-8.2 → 2.40.0-2.6
> libgtk-3-0 3.10.4-12.1 → 3.12.1-2.8
>
> The following 78 packages are going to be downgraded:
> branding-openSUSE 13.1-10.4.13 → 13.1-4.11
> digikam 3.5.0-4.1 → 3.5.0-3.31
> digikam-doc 3.5.0-4.1 → 3.5.0-3.31
> dynamic-wallpaper-branding-openSUSE 13.1-10.4.13 → 13.1-4.11
> gfxboot-branding-openSUSE 13.1-10.4.13 → 13.1-4.11
> gio-branding-openSUSE 13.1-2.13.1 → 13.1-2.1
> gnome-js-common 0.1.2-13.1.2 → 0.1.2-2.1
> gnome-menus-branding-openSUSE 13.1-2.2.2 → 13.1-2.1
> grub2-branding-openSUSE 13.1-10.4.13 → 13.1-4.11
> gtk2-engines 2.20.2-16.1.4 → 2.20.2-2.5
> gtk2-theme-clearlooks 2.20.2-16.1.4 → 2.20.2-2.5
> gtk2-theme-crux 2.20.2-16.1.4 → 2.20.2-2.5
> gtk2-theme-industrial 2.20.2-16.1.4 → 2.20.2-2.5
> gtk2-theme-mist 2.20.2-16.1.4 → 2.20.2-2.5
> gtk2-theme-redmond95 2.20.2-16.1.4 → 2.20.2-2.5
> gtk2-theme-thinice 2.20.2-16.1.4 → 2.20.2-2.5
> gtk3-branding-openSUSE 13.1-2.4.2 → 13.1-2.1
> gtkspell3-lang 3.0.3-2.4.1 → 3.0.3-2.1
> hicolor-icon-theme-branding-openSUSE 13.1-2.1.2 → 13.1-2.1
> kde4-kgreeter-plugins 4.11.9-111.1 → 4.11.8-3.14
> kdebase4-openSUSE 13.1-6.9.11 → 13.1-2.19
> kdebase4-workspace 4.11.9-111.1 → 4.11.8-3.14
> kdebase4-workspace-branding-openSUSE 13.1-6.9.11 → 13.1-2.19
> kdebase4-workspace-ksysguardd 4.11.9-111.1 → 4.11.8-3.14
> kdebase4-workspace-liboxygenstyle 4.11.9-111.1 → 4.11.8-3.14
> kdebase4-workspace-plasma-calendar 4.11.9-111.1 → 4.11.8-3.14
> kdm 4.11.9-111.1 → 4.11.8-3.14
> kdm-branding-openSUSE 13.1-10.4.13 → 13.1-4.1
>
> --------------------
>
> I cut the output short at that point, to not swamp readers.
>
> There seemed to be a lot of packages that were “downgraded”, meaning
> that the Tumbleweed version number was lower than the version number in
> the standard 13.1 repos.
>
>

That is normal for anyone using TumbleWeed. I would only become
concerned if operational problems arose.

Ken

#19

One difference is the fact that the comment about “3.10 stuff” remaining referred youur previous zypper dup(s) with equal priorities (and fewer downgrades).

I noticed downgrades but a lot less than 78, IIRC. I don’t install a plethora of desktops either. :slight_smile:

A downgrade could also be from the same repo e.g. Tumbleweed repo.

I was really only interested in the four or five packages that originally downgraded from 3.12 → 3.10 causing issues. They are all back to 3.12 here.

#20

That’s how I normally view mine. Also if there are real package conflicts, I will abort the upgrade and wait for a resolution from the maintainer(s).

I don’t think Tumbleweed particularly supports XFCE or LXDE, in the way it supports KDE and Gnome. Do correct me if that’s wrong. :slight_smile: