How to upgrade GNOME 3.12 to 3.14

onoakino · 2014-09-25 08:30:34

I don't know what I'm doing wrong but I constantly update using "pacman -Syu" every week but I'm still stuck with GNOME 3.12 since February. Can someone direct me on how to install Gnome 3.14? Your help will be much appreaciated.

drenninghoff · 2014-09-25 08:36:45

You are doing nothing wrong. Every two GNOME releases are stable releases, that means after 3.10 comes 3.12 comes 3.14. Yes there is 3.13 but it is never packaged in the distributions because it is an unstable release that has no real testing done. GNOME 3.14 was released yesterday, so it is not available in the arch repos yet because it must be tested first. Wait 1 - 2 weeks and it should be there. If you want to try it right now, you need to enable the [gnome-unstable] and [testing] repos.

anarchticgrimm · 2014-09-25 08:36:47

Hi,

It hasn't even been a day since Gnome 3.14 released and I don't think it made it to the Testing repository, just yet. So you should probably give it a week or two to be tested and released for everyday usage.

onoakino · 2014-09-25 08:54:12

Now I'm enlightened! Thank you very much dreninghoff. I was not aware that the release cycle of GNOME was like that. And I also totally forgot about enabling the unstable and testing repos and here I was wondering why 3.13 isn't even showing up in pacman. Haha I'm a noob. Thanks to you and to anacrhticgrimm as well. You are both very helpful.

conley · 2014-09-25 13:01:51

See also https://bbs.archlinux.org/viewtopic.php?id=186641.

If you're in the mood to break things (only joking, haha!), you can enable the gnome-unstable and testing repositories to try the upcoming 3.14 release. It was only officially released on the 24th (yesterday), so it will probably be a week or two before it makes it to the stable reposities. However, the gnome-unstable repo does appear to be working well - moreso than it was with the upgrade from 3.10 -> 3.12, in my opinion.

P.S. Gnome 3.13 is the version of Gnome that is developed; 3.14 is the version that is released. Odd numbers are development, even numbers are release.

Last edited by conley (2014-09-25 13:03:05)

titaniumbones · 2014-09-25 20:07:15

Hi Everyone,

I have just enabled the gnome-unstable repositories and upgraded to gnome 3.14 -- unfortunately,GDM will no longer run, booting into gnome gives a blank screen, and even under cinnamon or xfce the gtk theme is almosti mpossible to use (for instance, I can't see the text I'm typing right now).

1. anyone else having this kind of problem?
2. the problem I'm having in xfce right now seems like a gtk theming problem -- is htere a way for me to ix this?
3. if all else fails, how do I downgrade ot 3.12?

Thanks,
Matt

markzz · 2014-09-25 20:34:59

titaniumbones wrote:

Hi Everyone,
I have just enabled the gnome-unstable repositories and upgraded to gnome 3.14 -- unfortunately,GDM will no longer run, booting into gnome gives a blank screen, and even under cinnamon or xfce the gtk theme is almosti mpossible to use (for instance, I can't see the text I'm typing right now).
1. anyone else having this kind of problem?
2. the problem I'm having in xfce right now seems like a gtk theming problem -- is htere a way for me to ix this?
3. if all else fails, how do I downgrade ot 3.12?
Thanks,
Matt

This is why they call it gnome-unstable. I am running 3.14 on one of my computers and I had to reinstall all packages to get GDM to run.

# pacman -Qqen | pacman -S -

If you use this computer for something other than testing, I would suggest waiting until gnome gets released in extra. You will not have a good time using it yet.

To downgrade, remove gnome-unstable from your pacman.conf and run a forced pacman upgrade (pacman -Syu --force).

Last edited by markzz (2014-09-25 20:41:10)

titaniumbones · 2014-09-25 20:45:41

markzz wrote:

This is why they call it gnome-unstable. I am running 3.14 on one of my computers and I had to reinstall all packages.
# pacman -Qqn | pacman -S -
If you use this computer for something other than testing, I would suggest waiting until gnome gets released in extra. You will not have a good time using it yet.

huh, interesting. That wouldn't work for me due to some conflicts (that I guess I should be concerned about!). But running

pacman -Qqn | grep "gtk|gnome" | pacman -S s

seems to have done the trick. It seems to me some gtk packages may not have been brought along by the upgrade, or something.

Thanks!!

brittyazel · 2014-09-25 23:27:32

You have to put gnome-unstable at the top of the repo list. If you ammend it to the end of the file, things will break. It must be first to get global priority

markzz · 2014-09-26 02:58:43

brittyazel wrote:

You have to put gnome-unstable at the top of the repo list. If you ammend it to the end of the file, things will break. It must be first to get global priority

That's not quite true, I put mine after miltilib in my pacman.conf. I just have to install the packages as gnome-unstable/package-name rather than just the package name. I actually like doing that because it allows me to choose if I want to install the unstable gnome packages when available rather than me having to ignore it or accidentially installing it (which I'm most worried about).

Last edited by markzz (2014-09-26 02:59:59)

brittyazel · 2014-09-26 03:30:51

markzz wrote:

brittyazel wrote:
You have to put gnome-unstable at the top of the repo list. If you ammend it to the end of the file, things will break. It must be first to get global priority
That's not quite true, I put mine after miltilib in my pacman.conf. I just have to install the packages as gnome-unstable/package-name rather than just the package name. I actually like doing that because it allows me to choose if I want to install the unstable gnome packages when available rather than me having to ignore it or accidentially installing it (which I'm most worried about).

Yes that would work. It does mean you keep the repository enabled full time though, whereas I only enable it on rare occasion lol

But in this case, have it on the bottom and running -Syu would almost certainly break things

Last edited by brittyazel (2014-09-26 03:31:47)

Sracinas · 2014-10-02 09:12:37

You also should enable testing and community testing and put gnome-unstable before extra. Some gnome-unstable packages depend on testing.

Last edited by Sracinas (2014-10-02 09:13:09)

titaniumbones · 2014-10-02 11:02:18

For the record, on my system, which had some trouble, I had testing enabled but not community-testing, while gnome-unstable was the first repository listed in pacman.conf. I'm not sure if the lack of community testing was part of the problem.

The upgrade to testing is working great.

fredbezies · 2014-10-03 20:23:03

titaniumbones wrote:

For the record, on my system, which had some trouble, I had testing enabled but not community-testing, while gnome-unstable was the first repository listed in pacman.conf. I'm not sure if the lack of community testing was part of the problem.
The upgrade to testing is working great.

Gnome 3.14 moved to testing one week ago or so. Gnome unstable is an empty repository. And you have to enable both testing repositories.

blackout23 · 2014-10-04 13:22:26

I think gnome-software is still in gnome-unstable, though.

Amphitryon · 2014-10-07 00:05:10

Ok, so I enabled the testing repo and my machine appears to have update to GNOME 3.14. I didn't see any obvious difference in GNOME but I note the "GNOME Wayland Session" option in gdm now works, i.e. I get a working GNOME session if I choose it.

Noting that most applications still appear to run with the X11 backend rather the wayland one I have been trying some applications with the wayland backend an dmost of the ones I used work fine. I have /usr/local/bin in my path before /usr/bin so I created a wrapper script in /usr/localbin that checks for running under wayland and sets the GDK_BACKEND and CLUTTER_BACKEND variables accordingly then executes the /usr/bin version. I then symlinked it to the names of know working apps.

So far it is looking very promising. I have noticed a couple of quirks - sometimes menus suffer because the mouse is not grabbed and sometimes a keystroke can be picked up by more than one application, for example Control-D to close a terminal (which happens as expected) then the web browser creates a bookmark too.

Arch Linux

#1 2014-09-25 08:30:34

How to upgrade GNOME 3.12 to 3.14

#2 2014-09-25 08:36:45

Re: How to upgrade GNOME 3.12 to 3.14

#3 2014-09-25 08:36:47

Re: How to upgrade GNOME 3.12 to 3.14

#4 2014-09-25 08:54:12

Re: How to upgrade GNOME 3.12 to 3.14

#5 2014-09-25 13:01:51

Re: How to upgrade GNOME 3.12 to 3.14

#6 2014-09-25 20:07:15

Re: How to upgrade GNOME 3.12 to 3.14

#7 2014-09-25 20:34:59

Re: How to upgrade GNOME 3.12 to 3.14

#8 2014-09-25 20:45:41

Re: How to upgrade GNOME 3.12 to 3.14

#9 2014-09-25 23:27:32

Re: How to upgrade GNOME 3.12 to 3.14

#10 2014-09-26 02:58:43

Re: How to upgrade GNOME 3.12 to 3.14

#11 2014-09-26 03:30:51

Re: How to upgrade GNOME 3.12 to 3.14

#12 2014-10-02 09:12:37

Re: How to upgrade GNOME 3.12 to 3.14

#13 2014-10-02 11:02:18

Re: How to upgrade GNOME 3.12 to 3.14

#14 2014-10-03 20:23:03

Re: How to upgrade GNOME 3.12 to 3.14

#15 2014-10-04 13:22:26

Re: How to upgrade GNOME 3.12 to 3.14

#16 2014-10-07 00:05:10

Re: How to upgrade GNOME 3.12 to 3.14

Board footer