Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Dantrell's GNOME Without Systemd Project (Part 1)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 10, 11, 12 ... 27, 28, 29  Next  
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Fri Jun 16, 2017 12:25 am    Post subject: Re: Compile errors, emerging Gnome Reply with quote

[Moderator note: the immediately preceding post was originally a separate thread, and this post was the sole response in that thread. Per hint from dantrell in this post, I merged that thread into this one. -Hu]

Tsigorf wrote:
I selected Gnome 3.24 from dantrell overlays as described right here : https://wiki.gentoo.org/wiki/GNOME/GNOME_Without_systemd

For the record, the support thread for GNOME Without Systemd is here.

Please post there in the future (or at the very least in Unsupported Software if you think you might derail the thread).

That said, GNOME 3.24 defaults to an elogind implementation which is not yet covered by the Wiki page. Reference the official documentation to be apprised of changes.

Tsigorf wrote:
Here are the errors (extract):

[...]

Can someone help me find the problem?

Please share the full emerge output starting from the emerge command as well as:

Code:
emerge --info dev-lang/vala | grep -A1 vala

_________________
Dantrell B.
Back to top
View user's profile Send private message
Yamakuzure
Advocate
Advocate


Joined: 21 Jun 2006
Posts: 2273
Location: Bardowick, Germany

PostPosted: Fri Jun 16, 2017 8:25 am    Post subject: Reply with quote

Yamakuzure wrote:
dantrell wrote:
Shibotto wrote:
Do you want me to report it upstream?

Please do.
Yes, please.
And thanky you very much!

The issue is fixed in Release v229.6 and a gentoo bug to bump elogind has been opened. :-)
_________________
Important German:
  1. "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
  2. "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Fri Jun 16, 2017 10:48 am    Post subject: Reply with quote

Yamakuzure wrote:
And thanky you very much!

No, thank you. :)

davidbrooke wrote:
Has anyone gotten this extension to work with 3.22?
https://extensions.gnome.org/extension/427/workspaces-to-dock/
When installed, it either shows "ERROR" via the browser or the on/off switch in gnome-tweak-tool is grayed out with an "!" inside a triangle.
I'm mainly posting this is find out whether there is an openrc problem or just an extension problem.

Shibotto wrote:
A little update to notify you that Workspace to Dock and Gno-Menu (which previously crashed with the same error) are now working fine with 3.24 :D

dantrell wrote:
Shibotto wrote:
The infamous background corruption after resuming from suspend is still there however and I assume it will be there till the end of time, since GNOME team doesn't plan to fix it. It doesn't bother me much anymore, though; restarting the shell fixes it anyway.

I forward ported the related patches for GNOME 3.24 but it is not on by default as I want to investigate the incompatibility with certain GNOME Shell extensions.

I finished investigating this. Turns out, less is more. :lol:

To those affected, please confirm that (a) those extensions work; and (b) there is no wallpaper corruption when resuming from suspend:

Code:
USE="deprecated-background" emerge --ask --nodeps --oneshot mutter gnome-shell-3.24.2

Don't forget to restart GNOME Shell.
_________________
Dantrell B.


Last edited by dantrell on Sat Jun 17, 2017 11:26 am; edited 1 time in total
Back to top
View user's profile Send private message
Tsigorf
n00b
n00b


Joined: 15 Jun 2017
Posts: 11

PostPosted: Fri Jun 16, 2017 5:17 pm    Post subject: Re: Compile errors, emerging Gnome Reply with quote

dantrell wrote:
Please post there in the future (or at the very least in Unsupported Software if you think you might derail the thread).


Thanks for the tip, didn't know where to post my problem.

dantrell wrote:
Please share the full emerge output starting from the emerge command


I avoided to post the whole build log here; please curl it on http://termbin.com/96jl

dantrell wrote:
Code:
emerge --info dev-lang/vala | grep -A1 vala


Code:
dev-lang/vala-0.36.3::dantrell-gnome was built with the following:
USE="-test" ABI_X86="64"


I am still on dantrell-gnome-3-22.
Since I readed the Incompatibilities section for elogind on the documentation you linked, I prefer not to try the 3.24.

Nevertheless, do you recommand the dantrell-gnome-3-20 overlay?

Thank you :)
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Sat Jun 17, 2017 11:42 am    Post subject: Re: Compile errors, emerging Gnome Reply with quote

Tsigorf wrote:
dantrell wrote:
Please share the full emerge output starting from the emerge command

I avoided to post the whole build log here; please curl it on http://termbin.com/96jl

In the future please start the log output from the emerge command used so that the package USE flags are obvious.

That said, this was an interesting one but I figured it out. Sync up and you should be good to go.

Tsigorf wrote:
Since I readed the Incompatibilities section for elogind on the documentation you linked, I prefer not to try the 3.24.

I think you misinterpreted that section. All it means is that those versions of elogind most likely have problems for those reasons. The overlays will correctly provide a working version.

Tsigorf wrote:
Nevertheless, do you recommand the dantrell-gnome-3-20 overlay?

I consider GNOME 3.14 the GNOME release version that should have been first.

3.16 and 3.18 took steps backwards.

3.20 made some concessions.

3.22 and 3.24 also took steps backwards.

That is not to say that bugs weren't fixed and features weren't added. The problem, from my perspective, is that accessibility and usability decreased (i.e. behaviour was changed and features were removed).

If you are not sensitive to changes and/or don't have specific requirements, stick the latest version. The older versions are fine as long as you are mindful of any packages that use the online capabilities of insecure versions of WebKitGTK+ (e.g. Epiphany/GNOME Web).

Basically, security aside, the difference is mostly aesthetic.

For the record, I still run GNOME 3.14 (it's gold). ;)
_________________
Dantrell B.
Back to top
View user's profile Send private message
Tsigorf
n00b
n00b


Joined: 15 Jun 2017
Posts: 11

PostPosted: Sat Jun 17, 2017 1:56 pm    Post subject: Re: Compile errors, emerging Gnome Reply with quote

dantrell wrote:
In the future please start the log output from the emerge command used so that the package USE flags are obvious.


Oh, my bad. I don't know if you still need it, but in case, that was:

Code:
localhost / # emerge --ask --verbose --keep-going gnome-base/gnome

 * IMPORTANT: 11 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N     ] gnome-extra/gnome-contacts-3.22.1::dantrell-gnome  USE="-v4l" 771 KiB
[ebuild  N     ] media-gfx/gnome-photos-3.22.6::dantrell-gnome-3-22  USE="-flickr {-test} -upnp-av" 940 KiB
[ebuild  N     ] app-misc/bijiben-3.21.2::dantrell-gnome-3-22  USE="-zeitgeist" 0 KiB
[ebuild  N     ] media-sound/gnome-music-3.22.2-r1::dantrell-gnome-3-22  PYTHON_TARGETS="python3_4 (-python3_5) (-python3_6)" 1 512 KiB
[ebuild  N     ] sci-geosciences/gnome-maps-3.22.2::dantrell-gnome-3-22  1 061 KiB
[ebuild  N     ] net-im/empathy-3.12.13::dantrell-gnome  USE="geolocation gnome gnome-online-accounts map spell v4l -debug {-test}" 0 KiB
[ebuild  N     ] gnome-base/nautilus-3.22.3::dantrell-gnome-3-22  USE="exif gnome introspection previewer tracker (-packagekit) (-selinux) -sendto {-test} -vanilla-icon -vanilla-icon-grid -vanilla-menu -vanilla-menu-compress -vanilla-rename -vanilla-search -xmp" 0 KiB
[ebuild  N     ] gnome-extra/nautilus-tracker-tags-1.10.5::dantrell-gnome-3-22  0 KiB
[ebuild  N     ] media-video/totem-3.22.1-r1::dantrell-gnome-3-22  USE="introspection nautilus python -debug -lirc {-test} -zeitgeist" PYTHON_SINGLE_TARGET="python3_4 (-python3_5) (-python3_6)" PYTHON_TARGETS="python3_4 (-python3_5) (-python3_6)" 0 KiB
[ebuild  N     ] app-text/evince-3.22.1:0/evd3.4-evv3.3::dantrell-gnome-3-22  USE="gnome gnome-keyring introspection nautilus postscript tiff -djvu -dvi -gstreamer -nsplugin -t1lib -xps" 0 KiB
[ebuild  N     ] gnome-extra/sushi-3.21.91::dantrell-gnome-3-22  USE="-office" 0 KiB
[ebuild  N     ] app-cdr/brasero-3.12.1-r1:0/3.1::dantrell-gnome  USE="css introspection libburn mp3 nautilus tracker (-packagekit) -playlist {-test}" 0 KiB
[ebuild  N     ] gnome-extra/gnome-documents-3.22.4::dantrell-gnome-3-22  2 258 KiB
[ebuild  N     ] gnome-extra/gnome-user-share-3.18.3::dantrell-gnome  340 KiB
[ebuild  N     ] app-arch/file-roller-3.22.3-r1::dantrell-gnome-3-22  USE="libnotify nautilus (-packagekit)" 0 KiB
[ebuild  N     ] media-sound/sound-juicer-3.22.1::dantrell-gnome-3-22  USE="flac vorbis -debug {-test}" 0 KiB
[ebuild  N     ] x11-libs/xcb-util-0.4.0::gentoo  USE="-doc -static-libs {-test}" ABI_X86="(64) -32 (-x32)" 0 KiB
[ebuild  N     ] x11-libs/xcb-util-image-0.4.0::gentoo  USE="-doc -static-libs {-test}" ABI_X86="(64) -32 (-x32)" 0 KiB
[ebuild  N     ] x11-libs/xcb-util-cursor-0.1.3-r1::gentoo  USE="-doc -static-libs {-test}" ABI_X86="(64) -32 (-x32)" 0 KiB
[ebuild  N     ] x11-libs/startup-notification-0.12-r1::gentoo  USE="-static-libs" 0 KiB
[ebuild  N     ] x11-wm/mutter-3.22.4-r1::dantrell-gnome-3-22  USE="deprecated-background gles2 introspection udev -debug {-test} (-wayland)" INPUT_DEVICES="wacom" 0 KiB
[ebuild  N     ] x11-libs/libwnck-3.20.1:3::dantrell-gnome  USE="introspection startup-notification -tools" 0 KiB
[ebuild  N     ] gnome-base/gnome-core-libs-3.22.0-r1:3.0::dantrell-gnome-3-22  USE="cups -python" 0 KiB
[ebuild  N     ] gnome-extra/gnome-system-monitor-3.22.2::dantrell-gnome-3-22  USE="X (-systemd)" 887 KiB
[ebuild  N     ] gnome-base/gnome-shell-3.22.3-r3::dantrell-gnome-3-22  USE="bluetooth deprecated deprecated-background ibus networkmanager -browser-extension -nsplugin (-systemd) -vanilla-motd -vanilla-screen (-xephyr)" PYTHON_TARGETS="python3_4 (-python3_5) (-python3_6)" 1 907 KiB
[ebuild  N     ] gnome-base/gdm-3.22.3-r1::dantrell-gnome-3-22  USE="branding deprecated introspection ipv6 tcpd -accessibility -audit -fprint -plymouth (-selinux) -smartcard (-systemd) {-test} -wayland -xinerama" 0 KiB
[ebuild  N     ] x11-terms/gnome-terminal-3.22.2::dantrell-gnome-3-22  USE="deprecated-transparency gnome-shell nautilus -debug -vanilla-hotkeys" 1 907 KiB
[ebuild  N     ] app-eselect/eselect-gnome-shell-extensions-20120911::gentoo  0 KiB
[ebuild  N     ] gnome-extra/gnome-tweak-tool-3.22.0::dantrell-gnome-3-22  PYTHON_TARGETS="python2_7" 255 KiB
[ebuild  N     ] gnome-extra/gnome-shell-extensions-3.22.2-r1::dantrell-gnome-3-22  USE="-examples" 332 KiB
[ebuild  N     ] gnome-base/gnome-extra-apps-3.22.0:3.0::dantrell-gnome-3-22  USE="bijiben evolution fonts games share shotwell todo tracker -boxes -builder -california -epiphany (-flashback) -geary -latexila" 0 KiB
[ebuild  N     ] gnome-base/gnome-core-apps-3.22.0:3.0::dantrell-gnome-3-22  USE="bluetooth cdr cups" 0 KiB
[ebuild  N     ] gnome-base/gnome-shell-common-0.0.1-r1::dantrell-gnome  0 KiB
[ebuild  N     ] gnome-base/gnome-3.22.0:2.0::dantrell-gnome-3-22  USE="bluetooth cdr classic cups extras -accessibility" 0 KiB

Total: 34 packages (34 new), Size of downloads: 12 165 KiB

Would you like to merge these packages? [Yes/No] yes

>>> Verifying ebuild manifests

>>> Emerging (1 of 34) gnome-extra/gnome-contacts-3.22.1::dantrell-gnome


dantrell wrote:
That said, this was an interesting one but I figured it out. Sync up and you should be good to go.


I'm not sure what you mean by "sync up". I've done an:
Code:
emerge-webrsync

followed by
Code:
emerge --sync


I know there's something I missed somewhere :lol:

dantrell wrote:
Tsigorf wrote:
Since I readed the Incompatibilities section for elogind on the documentation you linked, I prefer not to try the 3.24.

I think you misinterpreted that section. All it means is that those versions of elogind most likely have problems for those reasons. The overlays will correctly provide a working version.


Indeed, thanks for the correction.

dantrell wrote:
That is not to say that bugs weren't fixed and features weren't added. The problem, from my perspective, is that accessibility and usability decreased (i.e. behaviour was changed and features were removed).

If you are not sensitive to changes and/or don't have specific requirements, stick the latest version. The older versions are fine as long as you are mindful of any packages that use the online capabilities of insecure versions of WebKitGTK+ (e.g. Epiphany/GNOME Web).

Basically, security aside, the difference is mostly aesthetic.

For the record, I still run GNOME 3.14 (it's gold). ;)


I had this discussion with a KDE fan who told that about Gnome too. I quickly had a look on changelogs and there's some features I'd love to have on latest versions. Considering the grading table on the Github doc, I might try to compile the 3.20 if I don't success to compile gnome-contacts.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Sat Jun 17, 2017 10:59 pm    Post subject: Re: Compile errors, emerging Gnome Reply with quote

Tsigorf wrote:
I'm not sure what you mean by "sync up".

I mean I fixed it and you need to resync with the project overlays to get the changes then reissue your emerge command.

Tsigorf wrote:
I've done an:
Code:
emerge-webrsync

Unless things changed, this fetches a ~1 day old snapshot of the portage tree. It is optional during the installation process and only for specific use cases during daily use.

Tsigorf wrote:
I know there's something I missed somewhere :lol:

This is the basic method for resuming installing:

Code:
emerge --sync
layman --sync-all
emerge --ask --keep-going gnome-base/gnome

and updating:

Code:
emerge --sync
layman --sync-all
emerge --ask --update --deep --changed-use --with-bdeps=y @world

You can simplify the sync process (it probably already is simplified) but I leave that as an exercise for the reader. ;)

Tsigorf wrote:
Considering the grading table on the Github doc, I might try to compile the 3.20 if I don't success to compile gnome-contacts.

Fun fact, all (probably) versions of gnome-extra/gnome-contacts were previously affected. :P
_________________
Dantrell B.
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 5879

PostPosted: Sun Jun 18, 2017 12:55 am    Post subject: Reply with quote

I noticed some people here complaining about screen corruption after suspend; I've been having a problem like that since Xorg 1.16 or thereabouts and I'm wondering if this is a problem in X itself (since I'm running completely different software). Looks like a "garbled palette", screenshots can't capture it and switching VTs makes it go away.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Sun Jun 18, 2017 2:51 am    Post subject: Reply with quote

Ant P. wrote:
Looks like a "garbled palette", screenshots can't capture it and switching VTs makes it go away.

Like this?

Ant P. wrote:
I noticed some people here complaining about screen corruption after suspend; I've been having a problem like that since Xorg 1.16 or thereabouts and I'm wondering if this is a problem in X itself (since I'm running completely different software).

Wallpaper corruption when resuming from suspend only started occurring from GNOME 3.14 when they introduced the new background code. The rationale being that the old background code "had major performance issues with certain background setups".

What they did was switch to using a OpenGL Frame Buffer Object (FBO) to store pre-cached content. The problem is that the contents of FBOs are not guaranteed to persist across mode/power switch events. The NVIDIA drivers, for instance, has never preserved the contents of FBOs hence why screen corruption is more predominant with it.

For the purposes of this project, I restored the old background code as a Qualtiy of Life (QoL) patch. This previously came at the cost of breaking GNOME Shell extensions (I recently rewrote the patch to account for this although I'm still waiting for confirmation from someone other than myself).

Basically, if the software you are using is suffering from screen corruption, investigate if their code uses FBOs and incorrectly assumes that the contents of FBOs persist across mode/power switch events.
_________________
Dantrell B.
Back to top
View user's profile Send private message
simonvanderveldt
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2016
Posts: 105

PostPosted: Sun Jun 18, 2017 9:08 am    Post subject: Reply with quote

Bit of a noob question, but if I understand it correctly elogind replaces/will replace pm-utils and consolekit, is that correct?
Is there any reason to switch to elogind right now? I'm still on GNOME 3.20 if that matters.

Just now installed GNOME without systemd on a laptop and suspend seems to be working fine so far with pm-utils. I've only done a couple of suspend, resume cycles so need to get some more experience to determine if it's really stable.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Sun Jun 18, 2017 10:27 am    Post subject: Reply with quote

simonvanderveldt wrote:
Bit of a noob question, but if I understand it correctly elogind replaces/will replace pm-utils and consolekit, is that correct?

That is correct.

simonvanderveldt wrote:
Is there any reason to switch to elogind right now?

The ConsoleKit implementation has better X11 integration (i.e. the GDM to GNOME Shell transition) but touchy power management.

The elogind implementation has better power management but touchy X11 integration (you should probably be using Wayland instead).

If you want to try GNOME 3.24, Wayland, are not using NVIDIA Optimus and understand that I don't consider the elogind implemenation stable just yet, you can switch.

simonvanderveldt wrote:
I'm still on GNOME 3.20 if that matters.

Just so you know, the elogind implementation will be backported towards 3.14 and the ConsoleKit implementation will be considered for forwardporting upon request for 3.26 and onwards.

So if you particularly like a certain GNOME release version, you will be able to use it (just be sure to keep up with any related security advisories).
_________________
Dantrell B.
Back to top
View user's profile Send private message
simonvanderveldt
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2016
Posts: 105

PostPosted: Sun Jun 18, 2017 10:35 am    Post subject: Reply with quote

dantrell wrote:
The ConsoleKit implementation has better X11 integration (i.e. the GDM to GNOME Shell transition) but touchy power management.

The elogind implementation has better power management but touchy X11 integration (you should probably be using Wayland instead).

If you want to try GNOME 3.24, Wayland, are not using NVIDIA Optimus and understand that I don't consider the elogind implemenation stable just yet, you can switch.

...

Just so you know, the elogind implementation will be backported towards 3.14 and the ConsoleKit implementation will be considered for forwardporting upon request for 3.26 and onwards.

So if you particularly like a certain GNOME release version, you will be able to use it (just be sure to keep up with any related security advisories).


Thanks for the confirmation and information!
I'm totally fine with using elogind for 3.24, wanted to try Wayland anyway :)

Are you going to make elogind work for the older and consolekit for the newer GNOME versions in your overlay? Isn't that a lot of work?
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Sun Jun 18, 2017 10:52 am    Post subject: Reply with quote

simonvanderveldt wrote:
Are you going to make elogind work for the older and consolekit for the newer GNOME versions in your overlay?

Just elogind for the older ones. ConsoleKit will be considered on a case-by-case basis.

I will probably drop ConsoleKit once I correct the quirky GDM to GNOME Shell transition behaviour and resolve the NVIDIA Optimus regression.

simonvanderveldt wrote:
Isn't that a lot of work?

Hours, tops. :wink:
_________________
Dantrell B.
Back to top
View user's profile Send private message
simonvanderveldt
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2016
Posts: 105

PostPosted: Sun Jun 18, 2017 10:56 am    Post subject: Reply with quote

dantrell wrote:
simonvanderveldt wrote:
Are you going to make elogind work for the older and consolekit for the newer GNOME versions in your overlay?

Just elogind for the older ones. ConsoleKit will be considered on a case-by-case basis.

I will probably drop ConsoleKit once I correct the quirky GDM to GNOME Shell transition behaviour and resolve the NVIDIA Optimus regression.

Makes sense. We're already a small group, would be nice to have as much people use the same thing so we get more feedback/results how well it's working.

Quote:
simonvanderveldt wrote:
Isn't that a lot of work?

Hours, tops. :wink:


Thanks for being so dedicated to the cause! ;)
Back to top
View user's profile Send private message
Tsigorf
n00b
n00b


Joined: 15 Jun 2017
Posts: 11

PostPosted: Mon Jun 19, 2017 8:17 am    Post subject: Re: Compile errors, emerging Gnome Reply with quote

dantrell wrote:
I mean I fixed it and you need to resync with the project overlays to get the changes then reissue your emerge command.


Oh! I didn't understand that! Thanks a lot, you're wonderful, it works! :D

(And, indeed. I had some problems understanding layman, I missed the “sync” concept.)


dantrell wrote:
Fun fact, all (probably) versions of gnome-extra/gnome-contacts were previously affected. :P


Well. My CPU says thanks too for the time saved.

Now I am on Gentoo, I'll go configuring everything. Thanks again! :)


Maybe just one more issue. When I log in via GDM, the desktop manager starts Gnome, but Gnome locks instantly (lock screen) asking me for typing my password again.

Do you have any track to the problem?
Code:
gnome-base/gdm-3.22.3-r1::dantrell-gnome-3-22 was built with the following:
USE="branding deprecated introspection ipv6 tcpd -accessibility -audit -fprint -plymouth (-selinux) -smartcard (-systemd) -test -wayland -xinerama" ABI_X86="64"


EDIT: it doesn't seem to be a problem from GDM but a problem from the Gnome desktop itself. Gnome locks wheneven I restart it (from [Atl]+[F2], then ”r”).
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Mon Jun 19, 2017 12:13 pm    Post subject: Re: Compile errors, emerging Gnome Reply with quote

Tsigorf wrote:
When I log in via GDM, the desktop manager starts Gnome, but Gnome locks instantly (lock screen) asking me for typing my password again.

That's an old one; never pinned it down. It happens with some setups and a workaround is not to log in too fast after GDM starts. It might be ConsoleKit specific and not present with elogind but don't quote me on that.

Tsigorf wrote:
Gnome locks wheneven I restart it (from [Atl]+[F2], then ”r”).

That's a new one. You broke it. I hope you are happy. :lol:

(Actually, I wasn't able to reproduce this so I have no idea. Do you have some extensions activated or something?)
_________________
Dantrell B.
Back to top
View user's profile Send private message
Tsigorf
n00b
n00b


Joined: 15 Jun 2017
Posts: 11

PostPosted: Mon Jun 19, 2017 12:56 pm    Post subject: Re: Compile errors, emerging Gnome Reply with quote

dantrell wrote:
Tsigorf wrote:
Gnome locks wheneven I restart it (from [Atl]+[F2], then ”r”).

That's a new one. You broke it. I hope you are happy. :lol:

(Actually, I wasn't able to reproduce this so I have no idea. Do you have some extensions activated or something?)


(I tried to disable all extensions (since I reused my home from an old Fedora, this broke some of them) but the problem remains…)
May I create a new topic for that?
Back to top
View user's profile Send private message
Yamakuzure
Advocate
Advocate


Joined: 21 Jun 2006
Posts: 2273
Location: Bardowick, Germany

PostPosted: Tue Jun 20, 2017 7:29 am    Post subject: Reply with quote

dantrell wrote:
The ConsoleKit implementation has better X11 integration (i.e. the GDM to GNOME Shell transition) but touchy power management.

The elogind implementation has better power management but touchy X11 integration (you should probably be using Wayland instead).
What is the problem with elgoind+GDM+X11 ? Is GDM really needed? SDDM works just fine with elogind, and is Wayland aware.
_________________
Important German:
  1. "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
  2. "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Tue Jun 20, 2017 8:25 am    Post subject: Reply with quote

Tsigorf wrote:
May I create a new topic for that?

I suppose because none of the work I have done goes anywhere near the code that could result in that behaviour. I wonder if this is one of those cases where shortcuts and certain keypresses in GNOME have gone haywire?

Yamakuzure wrote:
What is the problem with elgoind+GDM+X11?

It's not that it doesn't work, it's how it works.

dantrell wrote:
saboya wrote:
The difference between the GDM transition before and now is that before it seemed that GDM "handed control" over to Gnome Shell without actually changing modesets, but now it seems that GDM exits and then Gnome Shell kicks in, kind of like 2 separate X sessions.

I'm starting to think that this behavior is expected unless you are using Wayland to alleviate the issue (or ConsoleKit which apparently didn't have this problem).

For reference see the Wayland/GDM Initiative page on the GNOME Wiki:

Quote:
Typically, after a user has typed their username and password successfully, GDM kills the GDM-mode gnome-shell from the currently running X server, and then starts the user session on the same X server. In a model where the user's session is wayland based, we don't need to transition the X server over from the login screen program to the user sesssion. Instead of killing the login screen, we can reset it so it's available for user switching later. Alternatively we could kill the login screen and the X server, but doing that has the potential to disrupt the login process.

If this doesn't happen with systemd then maybe elogind is missing something?

The quickest way to rule out elogind is to check if it happens with systemd+GDM+X11. If it does, then it is what it is.
_________________
Dantrell B.
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 122
Location: Italy

PostPosted: Mon Jun 26, 2017 11:42 am    Post subject: Reply with quote

I'm trying to compile Wayland support (out of curiosity, maybe it won't even work with my Nvidia card), but something in mutter still requires systemd:
Code:
configure: error: Package requirements (libdrm libsystemd libinput >= 1.4 gudev-1.0 gbm >= 10.3) were not met:

No package 'libsystemd' found

My USE flags for mutter:
Code:
shiba ~ > emerge -pv mutter

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   #] x11-wm/mutter-3.24.2::dantrell-gnome-3-24  USE="egl* introspection udev wayland* -debug -deprecated-background% -gles2 {-test}" INPUT_DEVICES="-wacom" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Tue Jun 27, 2017 12:50 pm    Post subject: Reply with quote

Shibotto wrote:
I'm trying to compile Wayland support (out of curiosity, maybe it won't even work with my Nvidia card), but something in mutter still requires systemd:
Code:
configure: error: Package requirements (libdrm libsystemd libinput >= 1.4 gudev-1.0 gbm >= 10.3) were not met:

No package 'libsystemd' found

If it was only that, sync up and you should be good to go.

Good luck. :wink:
_________________
Dantrell B.
Back to top
View user's profile Send private message
Yamakuzure
Advocate
Advocate


Joined: 21 Jun 2006
Posts: 2273
Location: Bardowick, Germany

PostPosted: Wed Jun 28, 2017 9:41 am    Post subject: Reply with quote

dantrell wrote:
Yamakuzure wrote:
What is the problem with elgoind+GDM+X11?

It's not that it doesn't work, it's how it works.

dantrell wrote:
saboya wrote:
The difference between the GDM transition before and now is that before it seemed that GDM "handed control" over to Gnome Shell without actually changing modesets, but now it seems that GDM exits and then Gnome Shell kicks in, kind of like 2 separate X sessions.

I'm starting to think that this behavior is expected unless you are using Wayland to alleviate the issue (or ConsoleKit which apparently didn't have this problem).
I do not really understand the issue here. That is the way other login managers do it, too. Kill their X session and the launched DM starts a new one. For sddm+plasma it is either X11 or Wayland.

dantrell wrote:
For reference see the Wayland/GDM Initiative page on the GNOME Wiki:

Quote:
Typically, after a user has typed their username and password successfully, GDM kills the GDM-mode gnome-shell from the currently running X server, and then starts the user session on the same X server. In a model where the user's session is wayland based, we don't need to transition the X server over from the login screen program to the user sesssion. Instead of killing the login screen, we can reset it so it's available for user switching later. Alternatively we could kill the login screen and the X server, but doing that has the potential to disrupt the login process.

If this doesn't happen with systemd then maybe elogind is missing something?

The quickest way to rule out elogind is to check if it happens with systemd+GDM+X11. If it does, then it is what it is.
Happens what exactly?
The wiki seems to imply, that gdm does it like everyone else. Kill their session and then start a new one.

However, there is one flaw: If you start wayland, X11 must not run. So simply resetting the login screen won't work, as wayland wouldn't start anyway. GDM needs to get out of the way of whatever comes next.
_________________
Important German:
  1. "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
  2. "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Wed Jun 28, 2017 12:35 pm    Post subject: Reply with quote

Yamakuzure wrote:
I do not really understand the issue here.

The old method was seamless (or otherwise unnoticeable) the new method is not.

You probably would have had to have been using the old method for a long time (or just be sensitive to changes) to notice the difference.

Yamakuzure wrote:
Happens what exactly?

Install GNOME <=3.22 (ConsoleKit) and GNOME 3.24 (elogind) and compare.
_________________
Dantrell B.
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 122
Location: Italy

PostPosted: Wed Jun 28, 2017 12:40 pm    Post subject: Reply with quote

dantrell wrote:
Good luck. :wink:

Bad luck :lol:
Code:
./.libs/libmutter-0.so: undefined reference to `sd_session_get_type'
./.libs/libmutter-0.so: undefined reference to `sd_pid_get_session'
./.libs/libmutter-0.so: undefined reference to `sd_session_get_seat'
./.libs/libmutter-0.so: undefined reference to `sd_uid_get_sessions'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:1922: mutter-test-runner] Error 1
make[4]: *** Waiting for unfinished jobs....
./.libs/libmutter-0.so: undefined reference to `sd_session_get_type'
./.libs/libmutter-0.so: undefined reference to `sd_pid_get_session'
./.libs/libmutter-0.so: undefined reference to `sd_session_get_seat'
./.libs/libmutter-0.so: undefined reference to `sd_uid_get_sessions'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:1898: mutter] Error 1
make[4]: Leaving directory '/var/tmp/portage/x11-wm/mutter-3.24.3/work/mutter-3.24.3/src'
make[3]: *** [Makefile:2326: all-recursive] Error 1
make[3]: Leaving directory '/var/tmp/portage/x11-wm/mutter-3.24.3/work/mutter-3.24.3/src'
make[2]: *** [Makefile:1335: all] Error 2
make[2]: Leaving directory '/var/tmp/portage/x11-wm/mutter-3.24.3/work/mutter-3.24.3/src'
make[1]: *** [Makefile:488: all-recursive] Error 1
make[1]: Leaving directory '/var/tmp/portage/x11-wm/mutter-3.24.3/work/mutter-3.24.3'
make: *** [Makefile:418: all] Error 2

Complete build.log https://www.systemli.org/paste/?01d8ad8e3733e429#tTFLTEztWqmGrrZuuksPX0EGREPV4NQmm8Xy8LLyreg=
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 580
Location: Earth

PostPosted: Wed Jun 28, 2017 1:43 pm    Post subject: Reply with quote

Shibotto wrote:
dantrell wrote:
Good luck. :wink:

Bad luck :lol:

More luck. :D

No really, I think I got it this time.
_________________
Dantrell B.
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3 ... 10, 11, 12 ... 27, 28, 29  Next
Page 11 of 29

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum