You are not logged in.
Well, I do have both wayland and xwayland installed, but for the moment, I prefer to start gnome with startx instead of gnome-session --session=gnome-wayland, which does not work as expected. Before the release of gnome there was much writing on phoronix about wayland being enabled in gnome 3.14 and fedora going to make it default, but now after the release, the reports about gnome 3.14 and wayland do not look so reassuring.
But I am glad that I started to look into wayland in time, so that it does not come as a shock, when (and if) it eventually hits Archlinux.
You actually use startx? Why don't you just enable gdm as a service in systemd?
I don't really know what I'm doing.
Offline
You actually use startx? Why don't you just enable gdm as a service in systemd?
Yes I do. I am oldfashioned and prefer to do upgrades before i start x. When I started with linux that was the way to go. I like it that way. I also like to keep an eye on the booting process for possible failures. I have gdm, but did systemctl disable gdm.
Offline
brittyazel wrote:You actually use startx? Why don't you just enable gdm as a service in systemd?
Yes I do. I am oldfashioned and prefer to do upgrades before i start x. When I started with linux that was the way to go. I like it that way. I also like to keep an eye on the booting process for possible failures. I have gdm, but did systemctl disable gdm.
That's cool I guess. However, when the time comes that you want to use Wayland full time instead of X, you will have to drop your startx habit, as wayland (from my understanding) has no such command, and you may either have to adopt the new syntax, or just leverage GDM to manage that stuff for you.
I don't really know what I'm doing.
Offline
@linfan: I also prefer to boot into a TTY and then start the graphical interface manually, but instead of startx, I just use "systemctl start gdm" for gnome. That way you get the best of both worlds (GDM doesn't autostart, so you boot into terminal, but you get GDM's lockscreen behavior in gnome after starting it manually). I also use XFCE sometimes, so I just have startx set to start XFCE instead, which makes switching DE's easy.
Last edited by mwillems (2014-10-04 01:48:31)
Offline
@brittyazel
I added an alias to my bashrc, it works great but there's no real reason to move to Wayland, as a default Gnome launching everything (even gnome-shell) through XWayland.
alias wayland='gnome-session --session=gnome-wayland'
Offline
@brittyazel
I added an alias to my bashrc, it works great but there's no real reason to move to Wayland, as a default Gnome launching everything (even gnome-shell) through XWayland.
alias wayland='gnome-session --session=gnome-wayland'
Nice, that's a nifty alias.
But I disagree, the general overall feel of the UI in Wayland is snappier and smoother, even if everything is being rendered by Xwayland. There is no longer any tearing when dragging a window from one monitor to another with dual monitors, and many bugs regarding X specific issues are (obviously) gone. Unfortunately, things such as drag-and-drop, the lack of ability to scroll in the applications overview, and the lack of "bottom edge" response to activate the messaging menu leave me using X right now. But I very much plan on switching to Wayland first thing upon those being fixed.
I can only imagine how great things will be once Wayland actually takes charge of rendering the shell and the gtk windows.
I don't really know what I'm doing.
Offline
Does anybody know how much work is still left to do in the testing repository? It's been almost three weeks since GNOME 3.14 was released...
Offline
You can use with `testing` repo.
Web Developer.
Offline
Oh sorry, maybe I haven't expressed myself clearly enough. I know that I can use it by enabling the testing repository - what I'm wondering is how much is left to do until it makes it into the extra repository?
Offline
At this point the only Gnome package which hasn't been promoted from [Gnome-Unstable] to [Testing] is the recently added Packagekit frontend: Gnome-Software. There's a high-priority bug report filed against it. Perhaps this or some other bugs in [Testing] are holding Gnome back ???
Whatever the issue may be, packagers know better. As people here say to eager upgraders: it will be ready when it's ready.
Last edited by isacdaavid (2014-10-12 19:05:48)
Offline
Oh sorry, maybe I haven't expressed myself clearly enough. I know that I can use it by enabling the testing repository - what I'm wondering is how much is left to do until it makes it into the extra repository?
Probably shortly after the release of 3.14.1.
Arch x64 on Thinkpad X200s/W530
Offline
Probably shortly after the release of 3.14.1.
This is what I wanted to hear, thank you!
Offline
Hello everyone,
Cannot pass the GDM Login screen, when I choose "Gnome on Wayland" I see a black screen with the mouse cursor for 2 secondes and the login screen appear again.
I have installed "xorg-server-xwayland" and my graphic card is Intel:
Intel Corporation 82G33/G31 Express Integrated Graphics Controller
Any idea?
Last edited by bluebyt (2014-10-12 14:55:44)
Offline
Hello everyone,
Cannot pass the GDM Login screen, when I choose "Gnome on Wayland" I see a black screen with the mouse cursor for 2 secondes and the login screen appear again.
I have installed "xorg-server-xwayland" and my graphic card is Intel:
Intel Corporation 82G33/G31 Express Integrated Graphics ControllerAny idea?
"journalctl /usr/bin/gnome-session" will tell you what went wrong.
Offline
Does anyone else have a completely flawless experience with GNOME 3.14 so far? Usually I expect some kind of hiccups after GNOME updates (as I had them in previous versions), but this time it runs without any issues at all. Even though I'm forced to use the default Adwaita theme (because Numix hasn't been updated yet for 3.14), I still like the new experience a lot - the animations really make a difference compared to GNOME 3.12.
Can't wait for 3.14.1 to arrive tomorrow/in a few days, which is usually the time when new GNOME releases get moved to extra, if I remember correctly.
~
Offline
Why do they have to wait till 3.x.1 is released? Are 3.x.0 releases too buggy?
Last edited by isacdaavid (2014-10-14 01:36:02)
Offline
Does anyone else have a completely flawless experience with GNOME 3.14 so far?
My experience with the core gnome software was flawless, but some third party gtk stuff didn't work quite right, and all my extensions were naturally borked. Nothing works to remind one how reliant one is on extensions quite so well as a Gnome version upgrade.
Offline
$journalctl /usr/bin/gnome-session Give me this:
"Unrecoverable failure in required component gnome-shell-wayland.desktop"
What is gnome-shell-wayland.desktop?
Last edited by bluebyt (2014-10-13 00:14:05)
Offline
Does anyone else have a completely flawless experience with GNOME 3.14 so far?
My experience has been almost flawless, but I don't run too many extensions. I use the Elegance Colors theme from the AUR, and it worked out of the box except the "Type to Search..." text area in the Activities Overview uses the default styling instead of the styling in the theme.
Gnome also doesn't recognize anymore the styling I have in ~/.config/gtk-3.0/gtk.css for padding the borders of gnome terminal (as recommended here). Does anyone know how to get that working again?
Last edited by whitebrice (2014-10-13 20:26:23)
Offline
Does anyone else have a completely flawless experience with GNOME 3.14 so far?
It has been smooth, so far. - No crashes; no major problems to cause me some trouble; Basically, no nothing. Shell seems a lot faster than 3.12. Quite interesting that Stable 3.12 feels much more buggy, sluggish and problematic with all the Nautilus problems it caused me than Gnome 3.14 in Testing Repository.
Loving it.
Offline
Just updated from the extra repository, yay. However, GNOME doesn't start up with `exec gnome-session' in .xinitrc and says that something went wrong, as well as GDM refuses to launch but I guess this is Catalyst's fault since this problem has already been introduced in 3.12. Any suggestions?
Edit: Obviously Catalyst is now completely incompatible with GNOME, switched to the open source driver.
Last edited by milli-961227 (2014-10-18 12:07:46)
Offline