| View previous topic :: View next topic |
| Author |
Message |
simonvanderveldt
Apprentice
Joined: 26 Jan 2016
Posts: 151
|
 Posted: Sat Apr 14, 2018 9:43 am Post subject: |
 |
|
Just updated my profile to "dantrell-gnome-3-26:default/linux/amd64/17.0/desktop/gnome/3.26" and gcc 7.3.0 and apart from 1 package it all worked in 1 go 
Unfortunately I'm still unable to login through GDM directly, I figured rebuilding everything might help somehow, but no change there.
The only package that failed to build was media-gfx/inkscape-0.91-r4.
It threw the following error a couple of times:
| Code: | ui/tools/flood-tool.cpp:271:119: error: call of overloaded 'abs(unsigned int)' is ambiguous
+= abs(static_cast<int>(amc ? unpremul_alpha(rmc, amc) : 0) - (amop ? unpremul_alpha(rmop, amop) : 0));
^
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/cstdlib:75:0,
from /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/stdlib.h:36,
from ./trace/trace.h:17,
from ./trace/potrace/inkscape-potrace.h:20,
from ui/tools/flood-tool.cpp:24:
|
I see there are a couple of other versions in your overlay but none of them seem to be keyworded:
| Code: | Keywords for media-gfx/inkscape:
| | u |
| a a p a s | n |
| l m h i p r m m s p | e u s | r
| p d a p a p c x m 6 i 3 a | a s l | e
| h 6 r p 6 p 6 8 6 8 p 9 s r | p e o | p
| a 4 m a 4 c 4 6 4 k s 0 h c | i d t | o
-------------+-----------------------------+-------+---------------
[I]0.91-r4 | o o o o o o o o o o o o o o | 6 o 0 | dantrell-gnome
0.92.1-r2 | o o o o o o o o o o o o o o | 6 # | dantrell-gnome
[M]0.92.2 | o + ~ ~ o + + + o o o o o o | 6 o | gentoo
0.92.2-r1 | o o o o o o o o o o o o o o | 6 # | dantrell-gnome
0.92.3 | o ~ ~ ~ o ~ ~ ~ o o o o o o | 6 o | gentoo
0.92.3 | o o o o o o o o o o o o o o | 6 o | dantrell-gnome
|
|
|
| Back to top |
|
 |
redeltaglio
n00b
Joined: 04 Apr 2018
Posts: 7
Location: Barcelona, Spain
|
| Posted: Sun Apr 15, 2018 12:14 pm Post subject: error persist en 3.24.4 |
|
|
| Code: |
* ERROR: gnome-base/gnome-control-center-3.24.4::dantrell-gnome-3-24 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=gnome-base/gnome-control-center-3.24.4::dantrell-gnome-3-24'`,
* the complete build log and the output of `emerge -pqv '=gnome-base/gnome-control-center-3.24.4::dantrell-gnome-3-24'`.
* The complete build log is located at '/var/tmp/portage/gnome-base/gnome-control-center-3.24.4/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/gnome-base/gnome-control-center-3.24.4/temp/environment'.
* Working directory: '/var/tmp/portage/gnome-base/gnome-control-center-3.24.4/work/gnome-control-center-3.24.4'
* S: '/var/tmp/portage/gnome-base/gnome-control-center-3.24.4/work/gnome-control-center-3.24.4'
* Messages for package gnome-base/gnome-control-center-3.24.4:
* Package: gnome-base/gnome-control-center-3.24.4
* Repository: dantrell-gnome-3-24
* Maintainer: gnome@gentoo.org
* USE: abi_x86_64 amd64 bluetooth colord cups elibc_glibc elogind gnome-online-accounts ibus kernel_linux networkmanager userland_GNU wayland
* FEATURES: preserve-libs sandbox userpriv usersandbox
* Applying gnome-control-center-3.24.2-user-accounts-prevent-segfault-when-user-list-is-empty.patch ...
* Applying gnome-control-center-3.24.2-optional.patch ...
* Applying gnome-control-center-3.24.4-optional-wayland.patch ...
* Applying gnome-control-center-3.24.2-optional-networkmanager.patch ...
* Applying gnome-control-center-3.24.2-optional-cups.patch ...
* Applying gnome-control-center-3.24.2-gentoo-paths.patch ...
* Applying gnome-control-center-3.24.2-fix-without-gdkwayland.patch ...
* Applying gnome-control-center-3.18.2-disable-automatic-datetime-and-timezone-options.patch ...
* Applying gnome-control-center-3.18.2-disable-changing-hostname.patch ...
* Running eautoreconf in '/var/tmp/portage/gnome-base/gnome-control-center-3.24.4/work/gnome-control-center-3.24.4' ...
* Running intltoolize --automake --copy --force ...
* Running libtoolize --install --copy --force --automake ...
* Running aclocal -I m4 -I libgd ...
* Running autoconf --force ...
* Running autoheader ...
* Running automake --add-missing --copy --force-missing ...
* Disabling deprecation warnings ...
* ERROR: gnome-base/gnome-control-center-3.24.4::dantrell-gnome-3-24 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=gnome-base/gnome-control-center-3.24.4::dantrell-gnome-3-24'`,
* the complete build log and the output of `emerge -pqv '=gnome-base/gnome-control-center-3.24.4::dantrell-gnome-3-24'`.
* The complete build log is located at '/var/tmp/portage/gnome-base/gnome-control-center-3.24.4/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/gnome-base/gnome-control-center-3.24.4/temp/environment'.
* Working directory: '/var/tmp/portage/gnome-base/gnome-control-center-3.24.4/work/gnome-control-center-3.24.4'
* S: '/var/tmp/portage/gnome-base/gnome-control-center-3.24.4/work/gnome-control-center-3.24.4'
|
_________________
https://twitter.com/taglio
PGP: 90DC 1D49 FC85 DD2E 38AC 5301 6DAE 5C27 DFAF 0D6
"...a broken clock is always right twice a day..." |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Mon Apr 16, 2018 7:39 am Post subject: Re: error persist en 3.24.4 |
|
|
| dantrell wrote: |
| saboya wrote: | | Looking forward to testing 3.28! |
I have been a bit lazy with this but I blame Meson 100%. |
I finished the third pass for GNOME 3.28 and there are ~10 packages that fail to build (due to Meson).
They are easy enough to fix but might take a bit. 
| redeltaglio wrote: | | dantrell wrote: | | In the meanwhile, do you remember your last buildable version of gnome-base/gnome-control-center? Was it 3.24.3? |
hello there. Yes it was, |
I wasn't able to reproduce this issue so gnome-base/gnome-control-center-3.24.3 has been restored.
Please mask as needed.
| simonvanderveldt wrote: | | Unfortunately I'm still unable to login through GDM directly, I figured rebuilding everything might help somehow, but no change there. |
This makes me sad. 
| simonvanderveldt wrote: | | The only package that failed to build was media-gfx/inkscape-0.91-r4. |
This one might actually actually require GCC 6 or older.
_________________
Dantrell B. |
|
| Back to top |
|
|
simonvanderveldt
Apprentice
Joined: 26 Jan 2016
Posts: 151
|
| Posted: Mon Apr 16, 2018 8:46 am Post subject: Re: error persist en 3.24.4 |
|
|
| dantrell wrote: |
| simonvanderveldt wrote: | | Unfortunately I'm still unable to login through GDM directly, I figured rebuilding everything might help somehow, but no change there. |
This makes me sad.
|
I switched to AMD (AMDGPU) graphics this weekend, coming from nvidia, so another item that might help, but alas, still unable to login. Small difference being the GDM background now stays on the screen whilst with nvidia I got a black screen/no input message from my monitor.
Guess I'll just have to get lucky sometime with an elogind update.
| dantrell wrote: |
| simonvanderveldt wrote: | | The only package that failed to build was media-gfx/inkscape-0.91-r4. |
This one might actually actually require GCC 6 or older.
|
Seems like you're right https://forums.gentoo.org/viewtopic-p-8066454.html#8066454
I'll have a look at upgrading it to a newer version that has the patch mentioned in that bug report. |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Tue Apr 17, 2018 4:36 pm Post subject: |
|
|
| simonvanderveldt wrote: | | I'll have a look at upgrading it to a newer version that has the patch mentioned in that bug report. |
For you, every version offered except Inkscape 0.91-r4 should build as those have the GCC 7 and Poppler >= 0.58.0 fixes.
But since more users are moving to GCC 7, I should either backport the fixes or move the stable versions up.
Edit: I ended up enforcing specific Poppler version ranges for Inkscape.
| dantrell wrote: | | I finished the third pass for GNOME 3.28 and there are ~10 packages that fail to build (due to Meson). |
I'm down to ~2 packages that fail to build.
I would like the minds behind Meson to please stand up.
_________________
Dantrell B. |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Sun Apr 22, 2018 2:54 pm Post subject: |
|
|
| The Gentoo team has masked x11-libs/xpyb recently, which is depended upon by <dev-python/pycairo-1.16. In the portage tree, 1.16 is stable but on the dantrell-gnome overlays the 1.16 ebuild is not keyworded. |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Sun Apr 22, 2018 11:09 pm Post subject: |
|
|
| saboya wrote: | | The Gentoo team has masked x11-libs/xpyb recently, which is depended upon by <dev-python/pycairo-1.16. In the portage tree, 1.16 is stable but on the dantrell-gnome overlays the 1.16 ebuild is not keyworded. |
Thanks for the heads up.
I'll be keeping the older pycairo around for a bit long but things have been adjusted accordingly.
Sync up and you should be good to go.
_________________
Dantrell B. |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Mon Apr 23, 2018 1:41 am Post subject: |
|
|
| dantrell wrote: | Thanks for the heads up.
I'll be keeping the older pycairo around for a bit long but things have been adjusted accordingly.
Sync up and you should be good to go. |
Np, but I think you missed something
x11-libs/xpyb is masked in the profile, but I still need =dev-python/pycairo-1.16* ~amd64 in my package.accept_keywords or portage will try to install =dev-python/pycairo-1.15.4.
And since x11-libs/xpyb is now masked, portage asks me to... unmask it |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Mon Apr 23, 2018 2:14 am Post subject: |
|
|
| saboya wrote: | | Np, but I think you missed something |
You saw nothing. 
_________________
Dantrell B. |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Mon Apr 23, 2018 3:33 am Post subject: |
|
|
Also, I've been following this issue:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
Was backporting some of those patches but when I hit gjs I realized there's no way those can be (quickly) safely backported to the current version being used in 3.26, and some of the fixes didn't even get a release tag yet.
But my point is: In your experience, do you think would it be safe to use gjs-1.52.3 (assuming that's the next tag that will contain most of the fixes) with 3.26? gnome-shell and mutter are easily solvable, but gjs is too far behind. |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Tue Apr 24, 2018 6:23 am Post subject: |
|
|
| saboya wrote: | | https://gitlab.gnome.org/GNOME/gnome-shell/issues/64 |
Thanks for the heads up, I'll be keeping an eye on this issue.
| saboya wrote: | | In your experience, do you think would it be safe to use gjs-1.52.3 (assuming that's the next tag that will contain most of the fixes) with 3.26? |
I try to avoid mixing packages from different GNOME release versions as they can turn out to be more trouble than they are worth but for some packages this is a non-issue.
As I'm not familiar with how gjs would fare, you just have to try it out and watch for breakage.
| dantrell wrote: | As for this, I made time to lay some groundwork for GNOME 3.28.
After my next pass (or two) GNOME 3.28.0 (alpha) will be available for testing. |
| dantrell wrote: | | I finished the third pass for GNOME 3.28 and there are ~10 packages that fail to build (due to Meson). |
| dantrell wrote: | | I would like the minds behind Meson to please stand up. |
I just want to talk.
| dantrell wrote: | | That will be my primary task as I begin prepping for GNOME 3.28 which is on the horizon. |
| Juippisi wrote: | | Sounds sweet! |
| saboya wrote: | | Looking forward to testing 3.28! |
GNOME 3.28.1 is now available for testing.
As is common nowadays, GNOME 3.28 defaults to an elogind implementation. If you are new, reference the official documentation to be apprised of changes in the installation process.
That said, just a few things:
- ConsoleKit support for GNOME 3.24+ is still pending.
- Nautilus is temporarily missing thumbnail support (for reasons previously mentioned).
- Nautilus is temporarily missing all but one of its Quality of Life improvements.
- It turns out that multilib ebuilds which use Meson and have configure options will ignore the options and build with their defaults (they also aren't actually multilib).
Also, while my stress testing showed that everything built (for me at least), there may be a couple packages that don't quite run. I'll be dealing those as I get to them.
Edit: Nautilus has regained thumbnail support although thumbnailing in a sandbox still doesn't work (for details see GNOME bug #792250).
_________________
Dantrell B. |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Tue Apr 24, 2018 2:47 pm Post subject: |
|
|
Thanks for your great work
I'll be testing 3.28 later today in my home box.
Funnily enough, I also had to deal with Meson.eclass issues last week, and I noticed he does generate a build file for each multilib profile on its own. You might have to fork the eclass if you want to avoid that. |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Tue Apr 24, 2018 3:01 pm Post subject: |
|
|
| *edit* - nvm, im stupid. |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Tue Apr 24, 2018 11:48 pm Post subject: |
|
|
| saboya wrote: | | I'll be testing 3.28 later today in my home box. |
I put some more work in and found a couple of packages that were acting funny:
- GNOME Builder
- GNOME Notes (Bijiben)
While fixing them I also forward-ported another Quality of Life improvement for Nautilus (i.e. slow double click to rename) and noticed that Nautilus made it easier to track import files and folders. Which sounds neat right? But wait...
The ability to star only shows up unconditionally in list view after you add the column but you can only star some things (i.e. dot files and folders can't be starred).
Furthermore, in icon view, the ability to star only shows up conditionally after you right click a file or folder that is tracked (i.e. starring currently only works for indexed locations). 
| saboya wrote: | | Funnily enough, I also had to deal with Meson.eclass issues last week, and I noticed he does generate a build file for each multilib profile on its own. You might have to fork the eclass if you want to avoid that. |
To trigger multilib meson has has to to come before it in the ebuild inherit function like so:
| Code: | | inherit gnome2 meson multilib-minimal |
The configure options will then be passed correctly but the package will probably fail to build. I'll be investigating but this is a low priority issue so if you find out the cause I won't complain.
P.S. I already have the elcass forked.
| dantrell wrote: | | There's also the even less unofficially supported GNOME+Plasma profiles. I will only test these to make sure they get clean emerge output. The rest, I leave [as] an exercise to the user. |
| Elleni wrote: | | Just want to report, that everything compiled fine with new plasma+gnome profile. |
Since you were the reason GNOME+Plasma profiles were added, just let me know when you want the profiles to be switched from GNOME 3.26 to GNOME 3.28.
That is, after someone other than me confirms that it builds.
_________________
Dantrell B. |
|
| Back to top |
|
|
Juippisi
Developer
Joined: 30 Sep 2005
Posts: 723
Location: /home
|
| Posted: Wed Apr 25, 2018 7:30 am Post subject: |
|
|
Nice to hear that 3.28 is available :) I will definitely try it, maybe this weekend. However Ive ran into problems after emerging the latest updates.
First of all, some of my gnome programs dont work. They give me an error,
| Quote: |
Error creating terminal: Message recipient disconnected from message bus without replying
|
Then my gtk3 dont work either,
| Quote: |
firefox: symbol lookup error: /usr/lib64/libgtk-3.so.0: undefined symbol: g_log_structured_standard
gedit: symbol lookup error: /usr/lib64/libgtk-3.so.0: undefined symbol: g_log_structured_standard
|
etc
I guess I could revert your github repo to a state it was before commits done in the last.... 36 hours I guess, but Ive got no time to "maintain" my desktop right now. Im kind of lucky because I wont be using my desktop for few days, but I saw these errors and wanted to get the info out ASAP so you can check whether the breakage is my fault or yours ;)
Ill get back to it in 2 days.
EDIT: Currently on 3.26 with elogind. |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Wed Apr 25, 2018 8:21 am Post subject: |
|
|
Ok, one miss in the compile phase: First, gnome-base/gnome-control-center needs >=sys-power/upower-0.99.8 because of UP_DEVICE_KIND_GAMING_INPUT.
I believe that was solved, but now I have another error:
| Code: | um-photo-dialog.c:567:58: error: ‘webcam_icon_selected’ undeclared (first use in this function); did you mean ‘g_relation_select’?
gtk_widget_class_bind_template_callback (wclass, webcam_icon_selected); |
That one I don't want to figure out right now, I'm heading to bed. But all other packages compiled fine, that is the only one missing (and gnome-light meta, but duh). |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Wed Apr 25, 2018 9:36 am Post subject: |
|
|
...and turns out I can't sleep at all, so:
gnome-base/gnome-control-center-3.28* is missing a dependency on >=media-video/cheese-3.28. This has been fixed recently by this patch:
https://gitlab.gnome.org/GNOME/gnome-control-center/commit/f957ce177601318fd428a105be6a5944f7bbc093
Which makes cheese an optional dependency, which can be turned into an USE flag (I'd very much like that since I don't want to have cheese installed because of Gnome CC). I just user-patched this here with the aforementioned patch (with no changes) and gnome-control-center finally compiled.
Off to restart. |
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 8935
|
| Posted: Wed Apr 25, 2018 10:37 am Post subject: |
|
|
| Simple question from a non-Gnome user: Why is this awesome work not being contributed to at least the official gnome overlay? I hear they are notoriously understaffed and this seems like a serious duplication of efforts... |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Wed Apr 25, 2018 11:17 am Post subject: |
|
|
| saboya wrote: | | Off to restart. |
Well this didn't end well at all.
Apparently you forgot the elogind patches for gnome-base/gnome-session, so gdm was just stuck to a grey screen. I switched to sddm, but that just moved the grey screen past the login box =P
So I tried to go back to 3.26, and... had the same issue. I'm now stuck in this state =/
I tried to patch gnome-session myself by modifying the meson.build, which I apparently did with success, but had errors with undefined references to what I assume to be systemd functions that are supposed to be fulfilled by elogind. Can't link you the logs here since I'm on windows, but you probably know what's happening.
So yeah, this is it for now =P |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Thu Apr 26, 2018 12:07 am Post subject: |
|
|
| dantrell wrote: | | Nautilus is temporarily missing all but one of its Quality of Life improvements. |
All of Nautilus's Quality of Life improvements have been accounted for.
| Juippisi wrote: | | However Ive ran into problems after emerging the latest updates. |
I spun up test installs for GNOME 3.14 through 3.28 and did not encounter this issue.
At face value, it sounds like you did the updates without doing the rebuilds but I'm not sure how that could have happened.
GTK+ did get bumped from 3.22.29 to 3.22.30 but that was a bug fix release. Also, your latter errors sound Pango related but that was updated a little over 2 weeks ago.
| Juippisi wrote: | | I guess I could revert your github repo to a state it was before commits done in the last.... 36 hours I guess, but Ive got no time to "maintain" my desktop right now. |
I think you are you going to have to do a couple rollbacks to confirm.
| saboya wrote: | | Ok, one miss in the compile phase: First, gnome-base/gnome-control-center needs >=sys-power/upower-0.99.8 because of UP_DEVICE_KIND_GAMING_INPUT. |
It was actually 0.99.6. Nice catch.
I'll be reviewing this to make sure only 3.28 is impacted.
| saboya wrote: | | ...and turns out I can't sleep at all |
| saboya wrote: | | gnome-base/gnome-control-center-3.28* is missing a dependency on >=media-video/cheese-3.28. |
Cheese has been an optional dependency of GNOME Control Center for a long time now. It may not have been obvious because it is managed through the v4l USE flag.
The build failure happened because GNOME Control Center added new Cheese dependent code for 3.28 but forgot the code guards (provided by that patch which I have gone ahead and backported).
| asturm wrote: | | Simple question from a non-Gnome user: Why is this awesome work not being contributed to at least the official gnome overlay? I hear they are notoriously understaffed and this seems like a serious duplication of efforts... |
If you thinking I didn't try, I did and the result was that I ended up assisting Funtoo Linux in officially implementing my patchset for GNOME 3.12 through 3.16.
Later, after learning of user interest, I created the GNOME Without Systemd project to directly support Gentoo Linux (and closely-related derivatives).
Given the choice between dealing with the challenges of collaborative efforts and getting work done, I chose the latter.
| saboya wrote: | | Well this didn't end well at all. |
This one was all my fault.
Sync up and you should be good to go.
| saboya wrote: | | So I tried to go back to 3.26, and... had the same issue. I'm now stuck in this state =/ |
This one is a mystery though?
Why wouldn't going back to 3.26 work? 
_________________
Dantrell B. |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Thu Apr 26, 2018 1:09 am Post subject: |
|
|
I don't know how I nuked my gnome installation, but it's not fixed =P
Here are my greeter.log and last 100 lines from messages:
https://gist.github.com/saboya/4336137aa458009ecca0e46c84254e89
I'm using gcc-7.3.0, which might have something to do with it but I highly doubt it. |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Thu Apr 26, 2018 2:14 am Post subject: |
|
|
| saboya wrote: | | I don't know how I nuked my gnome installation, but it's not fixed =P |
I probably going to pull out another machine to triple check but if it works, I got nothing.
| saboya wrote: | | Here are my greeter.log and last 100 lines from messages |
Most of those warnings can be ignored as they have been around since the switch to elogind and my patches don't touch them.
This one though, I'm going to look into:
| Code: | | (gnome-shell:3621): mutter-WARNING **: 21:57:30.877: Failed to load background 'file:///usr/share/backgrounds/gnome/adwaita-lock.jpg': Error opening file /usr/share/backgrounds/gnome/adwaita-lock.jpg: No such file or directory |
But my guess is your problem is here:
| Code: | | (gnome-shell:3621): Clutter-CRITICAL **: 21:57:30.941: clutter_input_focus_set_content_purpose: assertion 'clutter_input_focus_is_focused (focus)' failed |
I last updated this package ~1 month ago so I'm not sure it's me (unless it's referring to Mutter). Did you fork it for the memory leak shenanigans?
Edit: I decided to use my workstation to triple check. It got upgraded from GNOME 3.14 to 3.28 which was pretty straightforward (of course, I downgraded back to GNOME 3.14 not long afterwards which wasn't that straightforward).
In the process I was able to confirm that GDM does work and that my guess about Clutter-CRITICAL was wrong (i.e. that particular message wouldn't prevent GNOME from starting).
My next guess is that maybe I didn't break anything.
P.S. I fixed the mutter-WARNING regarding the missing background file.
_________________
Dantrell B. |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Thu Apr 26, 2018 9:30 pm Post subject: |
|
|
I think my issue is session-related, since neither gdm or gnome-shell starts (if I try to login with sddm).
I'm considering 3 possibilities right now:
1 - GCC 7.3.0 - When I switched GCC versions, I didn't emerge @system or @world, so maybe I have to recompile some dependency with the same GCC version. Or maybe GCC 7.3.0 just straight up messes something up with Gnome (I don't think so)
2 - I'm on gnome-light, I don't know if you tested with full featured gnome or gnome-light, but there might be some dependency issues with gnome-light. I don't think that's likely either, considering I can't even try to login with gdm.
3 - I just managed to put my gnome into some bizarre state, somehow. I think I'm going to unmerge everything gnome-related, purge all my configs and try again.
Here's a gdm log with debug on, might have something for you (I couldn't make anything of it): https://gist.github.com/saboya/3472c6c508ef7a045ee2131ab0fcf13f
I'm on xfce4 for now, will post later with my findings. |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Thu Apr 26, 2018 10:22 pm Post subject: |
|
|
| saboya wrote: | | 1 - GCC 7.3.0 - When I switched GCC versions, I didn't emerge @system or @world, so maybe I have to recompile some dependency with the same GCC version. Or maybe GCC 7.3.0 just straight up messes something up with Gnome (I don't think so) |
Before I started I performed emerge --emptytree (-e) on GNOME 3.14 through 3.26 and later upgraded a 3.26 install to 3.28.
However, everything was built against GCC 6.4.0 so I don't know if the GCC 7 series has issues.
| saboya wrote: | | 2 - I'm on gnome-light, I don't know if you tested with full featured gnome or gnome-light, but there might be some dependency issues with gnome-light. I don't think that's likely either, considering I can't even try to login with gdm. |
For initial GNOME releases I build gnome-base/gnome with pretty much every GNOME-related USE flag enabled so that got tested.
But I personally run gnome-base/gnome-light so that was also tested.
| saboya wrote: | 3 - I just managed to put my gnome into some bizarre state, somehow. I think I'm going to unmerge everything gnome-related, purge all my configs and try again.
Here's a gdm log with debug on, might have something for you (I couldn't make anything of it): https://gist.github.com/saboya/3472c6c508ef7a045ee2131ab0fcf13f
I'm on xfce4 for now, will post later with my findings. |
I'm still not seeing anything so I'll be waiting for your results.
_________________
Dantrell B. |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Fri Apr 27, 2018 2:22 am Post subject: |
|
|
Are you on a multilib profile?
I just noticed I got this permanent warning, no matter what I do:
| Code: | !!! existing preserved libs:
>>> package: app-accessibility/at-spi2-core-2.28.0-r1
* - /usr/lib32/libatspi.so.0
* - /usr/lib32/libatspi.so.0.0.1
* used by /usr/lib32/libatk-bridge-2.0.so.0.0.0 (app-accessibility/at-spi2-atk-2.26.2) |
|
|
| Back to top |
|
|
|
Unsupported Software
