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 ... 9, 10, 11 ... 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: 561
Location: Earth

PostPosted: Mon May 22, 2017 6:38 pm    Post subject: Reply with quote

Shibotto wrote:
dantrell wrote:
It would have helped to see your clean emerge output before you began upgrading because that's something I can readily compare.

The only thing I have from before starting anything is this http://i.imgur.com/AnUwvR1.jpg , but I don't think it will be very helpful.

That's actually exactly what I wanted to see. It helped me rule out 99% of what could have gone wrong.

saboya wrote:
Yeah, neither r1 or r2 helped.

Third time's the charm. :lol:

No really, I reproduced the issue and everything. There was a divergence between what I had in development and what went to production. I also improved the patches while I was at it.
_________________
Dantrell B.
Back to top
View user's profile Send private message
saboya
Guru
Guru


Joined: 28 Nov 2006
Posts: 442
Location: Brazil

PostPosted: Mon May 22, 2017 8:43 pm    Post subject: Reply with quote

Third time is the charm indeed :)

Everything seems to work fine. The transition between GDM and Gnome Shell seems weird tho, not sure if it's a first boot thing.
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 109
Location: Italy

PostPosted: Tue May 23, 2017 7:13 am    Post subject: Reply with quote

dantrell wrote:
That's actually exactly what I wanted to see. It helped me rule out 99% of what could have gone wrong.

That's the first time that being a compulsive hoarder comes in handy lol!

Anyway I confirm that GDM is now working for me too. Before next week I'll put 3.24 on my laptop, so I can test suspension, lid closing and everything I can't on my desktop PC. EDIT: I may be able to build it tonight, webkit-gtk takes ~4h, a huge pain in the... back.

Regarding the transition saboya was talking about, maybe it's not the same thing he's talking about, but I noticed a difference too and I made a comparison.
GNOME 3.24 (Desktop PC): https://youtu.be/D5bhxEf3u-4 (you can even see TopIcons Plus being stupid in the end)
GNOME 3.20 (Laptop): https://youtu.be/WoqWvRchlqo
It doesn't seem to break anything, though.


Last edited by Shibotto on Tue May 23, 2017 3:47 pm; edited 1 time in total
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 109
Location: Italy

PostPosted: Tue May 23, 2017 12:23 pm    Post subject: Extensions now compatible Reply with quote

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
Back to top
View user's profile Send private message
saboya
Guru
Guru


Joined: 28 Nov 2006
Posts: 442
Location: Brazil

PostPosted: Tue May 23, 2017 1:10 pm    Post subject: Reply with quote

I'm not sure if this could be related to the update, but my Xbox 360 controller no longer works, at least with Steam games. It connects fine, is recognized, the kernel module (xpad) is loaded, but no input reaches the applications.

*edit* - Adding myself to the input group did it. Don't know why it worked before. There's another group called "uinput", which I believe is the one needed before.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 561
Location: Earth

PostPosted: Tue May 23, 2017 11:13 pm    Post subject: Reply with quote

saboya wrote:
The transition between GDM and Gnome Shell seems weird tho, not sure if it's a first boot thing.

Shibotto wrote:
Regarding the transition saboya was talking about, maybe it's not the same thing he's talking about, but I noticed a difference too and I made a comparison.

You can try enabling the vanilla-motd and vanilla-screen USE flags on gnome-base/gnome-shell to rule out my QoL patches:

Code:
USE="vanilla-motd vanilla-screen" emerge --ask --oneshot --nodeps gnome-base/gnome-shell

If that's not it, then I need to recheck how the relevant packages are interacting with each other.
_________________
Dantrell B.
Back to top
View user's profile Send private message
saboya
Guru
Guru


Joined: 28 Nov 2006
Posts: 442
Location: Brazil

PostPosted: Wed May 24, 2017 10:08 am    Post subject: Reply with quote

This new behavior was not an issue in my desktop with a "regular" Nvidia setup, but it broke my laptop with Optimus.

According to https://wiki.gentoo.org/wiki/NVIDIA/Optimus, you had to add:

Code:
exec xrandr --setprovideroutputsource modesetting NVIDIA-0
exec xrandr --auto


to /etc/gdm/Init/Default in order to make Optimus work, and that's how it was on my laptop with 3.22, working fine.

With 3.24, the GDM login screen works fine, but when I enter my password and press enter, when the session is about to start, the screen goes black and nothing happens. I get this on dmesg:

Code:
[    7.698284] elogind[2464]: New session c1 of user gdm.
[    7.793286] nvidia-modeset: Allocated GPU:0 (GPU-4a513c24-2227-f3a9-08c9-366f5cba8c54) @ PCI:0000:04:00.0
[    7.793446] nvidia-modeset: Freed GPU:0 (GPU-4a513c24-2227-f3a9-08c9-366f5cba8c54) @ PCI:0000:04:00.0
[   13.060615] Bluetooth: hci0 command 0x0c12 tx timeout
[   14.858331] elogind[2464]: New session 1 of user saboya.
[   15.325725] nvidia-modeset: Allocated GPU:0 (GPU-4a513c24-2227-f3a9-08c9-366f5cba8c54) @ PCI:0000:04:00.0
[   15.325862] nvidia-modeset: Freed GPU:0 (GPU-4a513c24-2227-f3a9-08c9-366f5cba8c54) @ PCI:0000:04:00.0
[   15.964586] fuse init (API version 7.26)
[   16.249465] gnome-shell[3014]: segfault at 28 ip 00007fce3eaa0908 sp 00007fff57eced18 error 4 in libmutter-0.so.0.0.0[7fce3ea62000+ed000]
[   16.340880] gnome-shell[3019]: segfault at 28 ip 00007fb8f776c908 sp 00007ffec73652b8 error 4 in libmutter-0.so.0.0.0[7fb8f772e000+ed000]
[   16.362801] gnome-session-f[3024]: segfault at 0 ip 00007ff53c260009 sp 00007ffc96d494e0 error 4 in libgtk-3.so.0.2200.15[7ff53bf7f000+700000]


If I add the same commands to /etc/gdm/Xsession, when I enter my password and press enter, the screen goes black and then I get the GDM login screen again, with no segfaults in the dmesg output.

gnome-shell[vanilla-motd,vanilla-screen] did not help.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 561
Location: Earth

PostPosted: Sat May 27, 2017 9:49 pm    Post subject: Reply with quote

saboya wrote:
This new behavior was not an issue in my desktop with a "regular" Nvidia setup, but it broke my laptop with Optimus.

Although I have completed the elogind whatever-fecta, I still haven't found the cause of the new behavior or the reason behind the issue with Optimus

Comparing my elogind implementation against others shows that I didn't miss anything but I'll be triple checking this.

Could it be the NVIDIA drivers as per Launchpad bug #1559576? Comment #121 suggests it was fixed. What version are you using?
_________________
Dantrell B.
Back to top
View user's profile Send private message
saboya
Guru
Guru


Joined: 28 Nov 2006
Posts: 442
Location: Brazil

PostPosted: Sun May 28, 2017 3:55 am    Post subject: Reply with quote

I'm using 375.66. I could try 381.22.

Gnome 3.24 supposedly has a "vga switcheroo" feature with a DBUS service, maybe this has something to do with it?

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.
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 109
Location: Italy

PostPosted: Mon May 29, 2017 8:19 am    Post subject: Reply with quote

I upgraded my laptop so I can finally test some other things.

First of all, screen turning off as soon as GDM starts (https://forums.gentoo.org/viewtopic-p-7923978.html#7923978) is now solved, as expected from dropping ConsoleKit. :wink:

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.

Again on suspension, there seems to be something missing from NetworkManager (I always use your latest updates before posting here, so updated to yesterday version): it goes in sleeping mode when suspension is triggered, but nothing makes it wake on resume. I'll past some uncut syslog:

--- Starting sleep ---
Code:
May 29 09:49:36 VPCS11E7E NetworkManager[4742]: <info>  [1496044176.9409] manager: sleep requested (sleeping: no  enabled: yes)
May 29 09:49:36 VPCS11E7E NetworkManager[4742]: <info>  [1496044176.9409] manager: sleeping...
May 29 09:49:36 VPCS11E7E NetworkManager[4742]: <info>  [1496044176.9410] device (eth0): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
May 29 09:49:36 VPCS11E7E NetworkManager[4742]: <info>  [1496044176.9588] device (38:2C:4A:29:96:4F): state change: disconnected -> unmanaged (reason 'sleeping') [30 10 37]
May 29 09:49:36 VPCS11E7E NetworkManager[4742]: <info>  [1496044176.9591] manager: NetworkManager state is now ASLEEP
May 29 09:49:36 VPCS11E7E NetworkManager[4742]: <info>  [1496044176.9598] device (wlan0): state change: activated -> deactivating (reason 'sleeping') [100 110 37]
May 29 09:49:37 VPCS11E7E dbus[4542]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 29 09:49:37 VPCS11E7E NetworkManager[4742]: <info>  [1496044177.0347] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping') [110 30 37]
May 29 09:49:37 VPCS11E7E avahi-daemon[4952]: Withdrawing address record for fe80::223:14ff:fe3c:99cc on wlan0.
May 29 09:49:37 VPCS11E7E dbus[4542]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 29 09:49:37 VPCS11E7E nm-dispatcher: req:1 'connectivity-change': new request (2 scripts)
May 29 09:49:37 VPCS11E7E nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
May 29 09:49:37 VPCS11E7E NetworkManager[4742]: <info>  [1496044177.0619] dhcp4 (wlan0): canceled DHCP transaction, DHCP client pid 9783
May 29 09:49:37 VPCS11E7E NetworkManager[4742]: <info>  [1496044177.0620] dhcp4 (wlan0): state changed bound -> done
May 29 09:49:37 VPCS11E7E avahi-daemon[4952]: Withdrawing address record for 155.185.77.141 on wlan0.
May 29 09:49:37 VPCS11E7E avahi-daemon[4952]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 155.185.77.141.
May 29 09:49:37 VPCS11E7E kernel: [ 2866.851711] wlan0: deauthenticating from 18:64:72:c6:78:91 by local choice (Reason: 3=DEAUTH_LEAVING)
May 29 09:49:37 VPCS11E7E avahi-daemon[4952]: Interface wlan0.IPv4 no longer relevant for mDNS.
May 29 09:49:37 VPCS11E7E NetworkManager[4742]: <info>  [1496044177.0787] device (wlan0): set-hw-addr: set MAC address to 36:DC:88:95:B5:F1 (scanning)
May 29 09:49:37 VPCS11E7E kernel: [ 2866.868115] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
May 29 09:49:37 VPCS11E7E kernel: [ 2866.874880] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
May 29 09:49:37 VPCS11E7E kernel: [ 2866.874994] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
May 29 09:49:37 VPCS11E7E kernel: [ 2867.093429] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
May 29 09:49:37 VPCS11E7E kernel: [ 2867.100190] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
May 29 09:49:37 VPCS11E7E kernel: [ 2867.100296] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
May 29 09:49:37 VPCS11E7E kernel: [ 2867.175794] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 29 09:49:37 VPCS11E7E NetworkManager[4742]: <info>  [1496044177.3884] dns-mgr: Removing DNS information from /sbin/resolvconf
May 29 09:49:37 VPCS11E7E nm-dispatcher: req:2 'down' [wlan0]: new request (2 scripts)
May 29 09:49:37 VPCS11E7E nm-dispatcher: req:2 'down' [wlan0]: start running ordered scripts...
May 29 09:49:37 VPCS11E7E NetworkManager[4742]: <warn>  [1496044177.4462] sup-iface[0x1f90b40,wlan0]: connection disconnected (reason -3)
May 29 09:49:37 VPCS11E7E NetworkManager[4742]: <info>  [1496044177.4465] device (wlan0): supplicant interface state: completed -> disconnected
May 29 09:49:37 VPCS11E7E NetworkManager[4742]: <warn>  [1496044177.4467] sup-iface[0x1f90b40,wlan0]: connection disconnected (reason -3)
May 29 09:49:37 VPCS11E7E NetworkManager[4742]: <info>  [1496044177.4476] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping') [30 10 37]
May 29 09:49:37 VPCS11E7E NetworkManager[4742]: <info>  [1496044177.4778] device (wlan0): set-hw-addr: reset MAC address to 00:23:14:3C:99:CC (unmanage)
May 29 09:49:37 VPCS11E7E ntpd[9917]: ntp engine exiting
May 29 09:49:37 VPCS11E7E ntpd[9919]: dispatch_imsg in main: pipe closed
May 29 09:49:37 VPCS11E7E ntpd[9915]: Terminating
May 29 09:49:37 VPCS11E7E /etc/init.d/ntpd[11396]: WARNING: ntpd is already stopped
May 29 09:49:42 VPCS11E7E kernel: <37>[ 2871.848972] elogind[4586]: Delay lock is active (UID 0/root, PID 7026/upowerd) but inhibitor timeout is reached.
May 29 09:49:42 VPCS11E7E kernel: <38>[ 2871.849396] elogind[4586]: Suspending system...
May 29 09:49:42 VPCS11E7E kernel: [ 2871.849425] PM: Syncing filesystems ... done.
May 29 09:49:42 VPCS11E7E kernel: [ 2872.498495] PM: Preparing system for sleep (mem)
May 29 09:50:01 VPCS11E7E kernel: [ 2874.476925] Freezing user space processes ... (elapsed 0.002 seconds) done.
May 29 09:50:01 VPCS11E7E kernel: [ 2874.479553] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
May 29 09:50:01 VPCS11E7E kernel: [ 2874.480886] PM: Suspending system (mem)
May 29 09:50:01 VPCS11E7E kernel: [ 2874.480968] Suspending console(s) (use no_console_suspend to debug)
May 29 09:50:01 VPCS11E7E kernel: [ 2874.481833] sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 29 09:50:01 VPCS11E7E kernel: [ 2874.481927] sd 0:0:0:0: [sda] Stopping disk
May 29 09:50:01 VPCS11E7E kernel: [ 2874.522737] ACPI : EC: event blocked
May 29 09:50:01 VPCS11E7E kernel: [ 2875.075762] PM: suspend of devices complete after 594.607 msecs
May 29 09:50:01 VPCS11E7E kernel: [ 2875.076401] PM: late suspend of devices complete after 0.635 msecs
May 29 09:50:01 VPCS11E7E kernel: [ 2875.076763] ACPI : EC: interrupt blocked
May 29 09:50:01 VPCS11E7E kernel: [ 2875.077845] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
May 29 09:50:01 VPCS11E7E kernel: [ 2875.078004] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
May 29 09:50:01 VPCS11E7E kernel: [ 2875.090700] PM: noirq suspend of devices complete after 14.296 msecs
May 29 09:50:01 VPCS11E7E kernel: [ 2875.090851] ACPI: Preparing to enter system sleep state S3
May 29 09:50:01 VPCS11E7E kernel: [ 2875.091095] ACPI : EC: EC stopped
May 29 09:50:01 VPCS11E7E kernel: [ 2875.091096] PM: Saving platform NVS memory
May 29 09:50:01 VPCS11E7E kernel: [ 2875.091450] Disabling non-boot CPUs ...
May 29 09:50:01 VPCS11E7E kernel: [ 2875.102093] smpboot: CPU 1 is now offline
May 29 09:50:01 VPCS11E7E kernel: [ 2875.116898] smpboot: CPU 2 is now offline
May 29 09:50:01 VPCS11E7E kernel: [ 2875.129863] smpboot: CPU 3 is now offline

--- Starting resume ---
Code:
May 29 09:50:01 VPCS11E7E kernel: [ 2875.134076] ACPI: Low-level resume complete
May 29 09:50:01 VPCS11E7E kernel: [ 2875.134150] ACPI : EC: EC started
May 29 09:50:01 VPCS11E7E kernel: [ 2875.134150] PM: Restoring platform NVS memory
May 29 09:50:01 VPCS11E7E kernel: [ 2875.134579] Suspended for 15.654 seconds
May 29 09:50:01 VPCS11E7E kernel: [ 2875.134649] Enabling non-boot CPUs ...
May 29 09:50:01 VPCS11E7E kernel: [ 2875.137016] x86: Booting SMP configuration:
May 29 09:50:01 VPCS11E7E kernel: [ 2875.137017] smpboot: Booting Node 0 Processor 1 APIC 0x1
May 29 09:50:01 VPCS11E7E kernel: [ 2875.139503]  cache: parent cpu1 should not be sleeping
May 29 09:50:01 VPCS11E7E kernel: [ 2875.139943] CPU1 is up
May 29 09:50:01 VPCS11E7E kernel: [ 2875.144054] smpboot: Booting Node 0 Processor 2 APIC 0x4
May 29 09:50:01 VPCS11E7E kernel: [ 2875.146426]  cache: parent cpu2 should not be sleeping
May 29 09:50:01 VPCS11E7E kernel: [ 2875.146877] CPU2 is up
May 29 09:50:01 VPCS11E7E kernel: [ 2875.154089] smpboot: Booting Node 0 Processor 3 APIC 0x5
May 29 09:50:01 VPCS11E7E kernel: [ 2875.156473]  cache: parent cpu3 should not be sleeping
May 29 09:50:01 VPCS11E7E kernel: [ 2875.156927] CPU3 is up
May 29 09:50:01 VPCS11E7E kernel: [ 2875.159466] ACPI: Waking up from system sleep state S3
May 29 09:50:01 VPCS11E7E kernel: [ 2875.160403] ACPI : EC: interrupt unblocked
May 29 09:50:01 VPCS11E7E kernel: [ 2875.172582] sdhci-pci 0000:03:00.0: MMC controller base frequency changed to 50Mhz.
May 29 09:50:01 VPCS11E7E kernel: [ 2875.174618] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
May 29 09:50:01 VPCS11E7E kernel: [ 2875.174653] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
May 29 09:50:01 VPCS11E7E kernel: [ 2875.174713] PM: noirq resume of devices complete after 14.496 msecs
May 29 09:50:01 VPCS11E7E kernel: [ 2875.175087] PM: early resume of devices complete after 0.349 msecs
May 29 09:50:01 VPCS11E7E kernel: [ 2875.175175] ACPI : EC: event unblocked
May 29 09:50:01 VPCS11E7E kernel: [ 2875.179755] sd 0:0:0:0: [sda] Starting disk
May 29 09:50:01 VPCS11E7E kernel: [ 2875.183089] rtc_cmos 00:01: System wakeup disabled by ACPI
May 29 09:50:01 VPCS11E7E kernel: [ 2875.487887] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 29 09:50:01 VPCS11E7E kernel: [ 2875.500644] ata2.00: configured for UDMA/100
May 29 09:50:01 VPCS11E7E kernel: [ 2875.681840] sdhci-pci 0000:03:00.4: Will use DMA mode even though HW doesn't fully claim to support it.
May 29 09:50:01 VPCS11E7E kernel: [ 2875.681885] sdhci-pci 0000:03:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
May 29 09:50:01 VPCS11E7E kernel: [ 2875.682877] PM: resume of devices complete after 507.804 msecs
May 29 09:50:01 VPCS11E7E kernel: [ 2875.729857] firewire_core 0000:03:00.3: rediscovered device fw0
May 29 09:50:01 VPCS11E7E kernel: [ 2875.759660] PM: Finishing wakeup.
May 29 09:50:01 VPCS11E7E kernel: [ 2875.759661] Restarting tasks ... done.
May 29 09:50:01 VPCS11E7E kernel: <38>[ 2875.952228] elogind[4586]: System resumed.
May 29 09:50:01 VPCS11E7E kernel: [ 2875.962832] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 29 09:50:01 VPCS11E7E kernel: [ 2875.963439] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
May 29 09:50:01 VPCS11E7E kernel: [ 2875.964276] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
May 29 09:50:01 VPCS11E7E kernel: [ 2875.964498] ata1.00: configured for UDMA/100
May 29 09:50:01 VPCS11E7E kernel: [ 2876.013487] psmouse serio1: synaptics: queried max coordinates: x [..5644], y [..4728]
May 29 09:50:02 VPCS11E7E acpid: client 7256[0:1000] has disconnected
May 29 09:50:02 VPCS11E7E acpid: client connected from 7256[0:1000]
May 29 09:50:02 VPCS11E7E acpid: 1 client rule loaded

--- Manually exit NetworkManager sleeping mode, calling dbus ---
Code:
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.5323] manager: wake requested (sleeping: yes  enabled: yes)
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.5323] manager: waking up...
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.5324] device (eth0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 29 09:50:22 VPCS11E7E kernel: [ 2896.666625] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 29 09:50:22 VPCS11E7E kernel: [ 2896.681436] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.5493] device (wlan0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 29 09:50:22 VPCS11E7E kernel: [ 2896.683704] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 29 09:50:22 VPCS11E7E kernel: [ 2896.685981] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
May 29 09:50:22 VPCS11E7E kernel: [ 2896.692594] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
May 29 09:50:22 VPCS11E7E kernel: [ 2896.692678] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
May 29 09:50:22 VPCS11E7E kernel: [ 2896.908463] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
May 29 09:50:22 VPCS11E7E kernel: [ 2896.915101] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
May 29 09:50:22 VPCS11E7E kernel: [ 2896.915185] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
May 29 09:50:22 VPCS11E7E kernel: [ 2896.991042] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.8586] device (38:2C:4A:29:96:4F): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.8591] manager: NetworkManager state is now DISCONNECTED
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.8592] audit: op="sleep-control" arg="off" pid=11243 uid=0 result="success"
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.8680] device (38:2C:4A:29:96:4F): state change: unavailable -> disconnected (reason 'none') [20 30 0]
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.9042] sup-iface[0x1f8f0a0,wlan0]: supports 5 scan SSIDs
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.9050] device (wlan0): supplicant interface state: starting -> ready
May 29 09:50:22 VPCS11E7E NetworkManager[4742]: <info>  [1496044222.9050] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
[ etc... ]


- EDIT -
For anyone who doesn't know how to use D-Bus, use this in your terminal as root:
Code:
gdbus call --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep false

- /EDIT -

I have some other problems, but they may be related to my particular configuration, so I'll refrain from posting them here until I'm sure.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 561
Location: Earth

PostPosted: Tue May 30, 2017 5:58 am    Post subject: Reply with quote

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.

Would you happen to know if systemd does this too?

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 actually noticed that since I was tracking GNOME bug #739178 but mentioning it slipped my mind.

Investigating the new background code for the cause has never panned out for me and every fix thus far by GNOME has been incomplete so my preference has always been been to restore the old background code. Of course this comes at the cost of introducing incompatibilities (e.g. breaking certain GNOME Shell extensions).

Shibotto wrote:
Again on suspension, there seems to be something missing from NetworkManager (I always use your latest updates before posting here, so updated to yesterday version): it goes in sleeping mode when suspension is triggered, but nothing makes it wake on resume.

I actually activated elogind on NetworkManager (1.8.0) to avoid this but either I missed something or it's not ready.
_________________
Dantrell B.
Back to top
View user's profile Send private message
Leio
Developer
Developer


Joined: 27 Feb 2003
Posts: 487
Location: Estonia

PostPosted: Fri Jun 02, 2017 12:32 am    Post subject: Reply with quote

Some random thought dumps.

Does accountsservice have elogind support there for gdm?

With systemd gdm always is on VT7 with USE=-plymouth and VT1 with USE=plymouth.
All other user sessions are opened on separate VTs. With systemd that tends to be VT2 and forward, unless you have went there before with an agetty (or whatever), so basically first free one (keeping in mind systemd doesn't open agetty's for VTs before you go to them).
If you switch back to gdm VT and log in to a user that's already logged in graphically, it simply switched to that VT and unlocks the screen if it was locked (as the password was entered into gdm). This is basically how fast-user-switching work now - if choosing "Log in with another user" (or whatever it's called in English, I have it translated), it simply switches to GDM's VT, then you log in from there - if the user isn't logged in yet, it opens another VT for it to log in, if already logged in, it switches to its VT and unlocks the screen.
This should be more seamless with wayland, atomic modesettings, and all that.

I presume the most of the 3.24 stuff in there are mostly just copy-pastes of the 3.22 or earlier ebuilds, without minimum dependency updates, any needed patch updates, etc? So nothing for me to grab for main tree?

For main tree integration I can't really make use of such an overlay, would really want a PR against main tree or something of that sort. Of course gnome-settings-daemon future is a bit worrying for the longevity of this exercise, and thus if there's a point in integrating it when it will stop working in a couple months. Forward looking work on settings-daemon 3.25 stuff once they land it (systemd user units usage) would be encouraging here.
_________________
GNOME team lead; GStreamer; MIPS/ARM64
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 109
Location: Italy

PostPosted: Tue Jun 06, 2017 7:56 am    Post subject: Reply with quote

dantrell wrote:
I actually activated elogind on NetworkManager (1.8.0) to avoid this but either I missed something or it's not ready.

For now I reverted to --with-suspend-resume=upower, which of course never suspends NetworkManager and so far never failed me once after resuming. I don't like this approach very much and I consider it a last resort. Since we don't rely on pm-utils anymore, what could be the best way to trigger NetworkManager wakeup on resuming?
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 561
Location: Earth

PostPosted: Sun Jun 11, 2017 11:38 pm    Post subject: Reply with quote

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?

Shibotto wrote:
dantrell wrote:
I actually activated elogind on NetworkManager (1.8.0) to avoid this but either I missed something or it's not ready.

For now I reverted to --with-suspend-resume=upower, which of course never suspends NetworkManager and so far never failed me once after resuming. I don't like this approach very much and I consider it a last resort. Since we don't rely on pm-utils anymore, what could be the best way to trigger NetworkManager wakeup on resuming?

After investigating, it appears the problem is with elogind >=228 so I added the last known working version. Sync up and test with:

Code:
emerge --ask --nodeps --oneshot =sys-auth/elogind-227.4

If that works, then this issue probably needs to be forwarded appropriately.
_________________
Dantrell B.
Back to top
View user's profile Send private message
saboya
Guru
Guru


Joined: 28 Nov 2006
Posts: 442
Location: Brazil

PostPosted: Mon Jun 12, 2017 12:27 am    Post subject: Reply with quote

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 fact that it kills GDM and starts Gnome Shell is fine, it works like this in my desktop with no issues. But on my laptop it creates issues with Optimus, but I have no idea why. Like I said, gnome 3.24 has some special handling for Optimus setups, maybe the DBus service is missing, but I honestly don't know.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 561
Location: Earth

PostPosted: Mon Jun 12, 2017 1:19 am    Post subject: Reply with quote

saboya wrote:
The fact that it kills GDM and starts Gnome Shell is fine, it works like this in my desktop with no issues. But on my laptop it creates issues with Optimus, but I have no idea why. Like I said, gnome 3.24 has some special handling for Optimus setups, maybe the DBus service is missing, but I honestly don't know.

I checked as well and came up with nothing. Not to mention, I lack the necessary hardware.

Since I have no idea where the cause is, perhaps the easiest thing for me to do is to just forward port the ConsoleKit patchset and rearrange 3.24 like so:

Quote:
[31] dantrell-gnome:default/amd64/3.24
[32] dantrell-gnome:default/amd64/3.24/extended
[33] dantrell-gnome:default/amd64/3.24/extended/elogind

Thoughts?
_________________
Dantrell B.
Back to top
View user's profile Send private message
saboya
Guru
Guru


Joined: 28 Nov 2006
Posts: 442
Location: Brazil

PostPosted: Mon Jun 12, 2017 2:17 am    Post subject: Reply with quote

dantrell wrote:
saboya wrote:
The fact that it kills GDM and starts Gnome Shell is fine, it works like this in my desktop with no issues. But on my laptop it creates issues with Optimus, but I have no idea why. Like I said, gnome 3.24 has some special handling for Optimus setups, maybe the DBus service is missing, but I honestly don't know.

I checked as well and came up with nothing. Not to mention, I lack the necessary hardware.

Since I have no idea where the cause is, perhaps the easiest thing for me to do is to just forward port the ConsoleKit patchset and rearrange 3.24 like so:

Quote:
[31] dantrell-gnome:default/amd64/3.24
[32] dantrell-gnome:default/amd64/3.24/extended
[33] dantrell-gnome:default/amd64/3.24/extended/elogind

Thoughts?

It might help to track down the issue, but to be honest it's not causing me huge issues personally, I'm just using the Intel card and it's working just fine.
Back to top
View user's profile Send private message
Juippisi
Guru
Guru


Joined: 30 Sep 2005
Posts: 337
Location: /home

PostPosted: Mon Jun 12, 2017 7:52 am    Post subject: Reply with quote

Hey dantrell, thanks for your magnificent work on Gnome without systemd!

I got a question: How stable would you consider 3.24 to be for everyday desktop usage? And should elogind be used with it? Been using 3.22 for a while now and I figured I got to update at some point, but whats the correct time then...
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 109
Location: Italy

PostPosted: Mon Jun 12, 2017 3:15 pm    Post subject: Reply with quote

dantrell wrote:
After investigating, it appears the problem is with elogind >=228 so I added the last known working version. Sync up and test with:

Code:
emerge --ask --nodeps --oneshot =sys-auth/elogind-227.4

If that works, then this issue probably needs to be forwarded appropriately.


It seems to work fine with 227.4. Relevant syslog (I have it all if you ever need it):
Code:
Jun 12 16:57:59 VPCS11E7E NetworkManager[4857]: <info>  [1497279479.5918] manager: sleep requested (sleeping: no  enabled: yes)
Jun 12 16:57:59 VPCS11E7E NetworkManager[4857]: <info>  [1497279479.5918] manager: sleeping...
Jun 12 16:58:04 VPCS11E7E kernel: <38>[  230.154793] elogind[4701]: Suspending system...
<...>
Jun 12 17:02:27 VPCS11E7E kernel: <38>[  235.920858] elogind[4701]: System resumed.
Jun 12 17:02:27 VPCS11E7E NetworkManager[4857]: <info>  [1497279747.7668] manager: wake requested (sleeping: yes  enabled: yes)
Jun 12 17:02:27 VPCS11E7E NetworkManager[4857]: <info>  [1497279747.7669] manager: waking up...

Do you want me to report it upstream?
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 561
Location: Earth

PostPosted: Tue Jun 13, 2017 12:36 am    Post subject: Reply with quote

Juippisi wrote:
How stable would you consider 3.24 to be for everyday desktop usage?

As per the project documenation:

Quote:
Full GNOME release versions are in the form of MAJOR.MINOR.PATCH. For the purposes of this project, PATCH at: 0 is considered "alpha", 1 is considered "beta" and 2 or higher is considered "stable".

So right now, GNOME 3.24 itself can be considered stable. The reason why it was marked as "alpha" despite that is because elogind integration is still being tested.

Juippisi wrote:
And should elogind be used with it? Been using 3.22 for a while now and I figured I got to update at some point, but whats the correct time then...

If you were holding back until elogind was somewhat reliable, you can go ahead and update. The only things to keep in mind at this point are that:

1. Wayland hasn't been tested

Quote:
Install with:

Code:
USE="egl libinput wayland" emerge --ask --update --deep --changed-use --with-bdeps=y gnome

or update with:

Code:
USE="egl libinput wayland" emerge --ask --update --deep --changed-use --with-bdeps=y @world

and then restart GDM (or reboot).

2. wallpaper corruption when resuming from suspend should be expected until I forward port the related patches

I have updated the project documentation accordingly, although, 3.22 is still the default.

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

Please do.
_________________
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: Tue Jun 13, 2017 8:41 am    Post subject: Reply with quote

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

Please do.
Yes, please.

I do not follow, or better, really follow the "Gnome without systemd"-Project.
I am using mainly Plasma and some LxQT. And that is what I test elogind with. I do neither have the time, nor the resources to test a fully fledged "Gnome without systemd"-installation.

This means, that I depend heavily on others to test such things.
A good example for this is "Bug 620948 - app-admin/packagekit-base: Needs elogind support". I do not use PackageKit. Hell, I do not even know exactly what it is good for. So without others reporting this, it would have lacked elogind-support forever.

So may I ask you a few favors, please?
  1. If you find something not working in elogind, please report the issue.
  2. If you have patched packages to add elogind support, please open a bug.
  3. If you have opened such a bug, please make it block the elogind integration tracker
    (Just write "elogind" into the "Blocks" field. Bugzilla knows what to do.)
    (This way I'll get pinged, as the tracker bug is mine.)
Thank you very much!
_________________
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
Juippisi
Guru
Guru


Joined: 30 Sep 2005
Posts: 337
Location: /home

PostPosted: Tue Jun 13, 2017 5:17 pm    Post subject: Reply with quote

dantrell wrote:
So right now, GNOME 3.24 itself can be considered stable. The reason why it was marked as "alpha" despite that is because elogind integration is still being tested.


Hey again, so I did the update earlier today. It went quite nice, stopped twice due to some errors. First one was a file collision between, I believe, gnome-shell-extensions-3.24 and gnome-shell-3.22. "/usr/share/gnome-shell/theme/calendar-today.svg" this was the problem file. I manually removed gnome-shell-3.22 and kept doing world update.

Then 2nd error was "No package 'mutter-clutter-0' found" when trying to emerge gnome-shell-3.24, but I manually emerged mutter and clutter, and kept doing world update which finished without problems now.

However Im not able to get GDM up. It doesnt even try to load X, just throws me to TTY. I can get a working Gnome-3.24 if I use startx from console, but I cant get gdm to work. I tried to install sddm too, but that doesnt work either. Im not sure whats up, because theres no gdm.log, but there might be something in /var/log/messages. Might have to get back on that later. I have Nvidia card, but not this "optimus", and am using the latest drivers from portage.

Anyway rest seems to be working fine! Thanks!

EDIT: And no wayland either. I booted my computer many times without difference.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 561
Location: Earth

PostPosted: Wed Jun 14, 2017 2:00 am    Post subject: Reply with quote

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.

dantrell wrote:
Shibotto wrote:
The second one when building gnome-shell-extensions-3.24: a conflict for a file named calendar-*something*.svg claimed by gnome-shell-3.22. That was trivial to solve, I mentioned it just for the record.

I know the cause and have a fix in mind but I'm going to sit on it for a bit.

Juippisi wrote:
First one was a file collision between, I believe, gnome-shell-extensions-3.24 and gnome-shell-3.22. "/usr/share/gnome-shell/theme/calendar-today.svg" this was the problem file. I manually removed gnome-shell-3.22 and kept doing world update.

I finished sitting on this. :lol:

Juippisi wrote:
Then 2nd error was "No package 'mutter-clutter-0' found" when trying to emerge gnome-shell-3.24, but I manually emerged mutter and clutter, and kept doing world update which finished without problems now.

I was able to reproduce and correct this issue.

Juippisi wrote:
However Im not able to get GDM up.

If you had GDM working before it sounds like you forgot to add and start the elogind service:

Code:
rc-update add elogind default
eselect rc start elogind
eselect rc restart xdm

Thanks for the feedback.
_________________
Dantrell B.
Back to top
View user's profile Send private message
Juippisi
Guru
Guru


Joined: 30 Sep 2005
Posts: 337
Location: /home

PostPosted: Wed Jun 14, 2017 9:16 am    Post subject: Reply with quote

dantrell wrote:

Code:
rc-update add elogind default
eselect rc start elogind
eselect rc restart xdm



I did that and restarted PC. However the problem was apparently due to not having locales correctly configured. I managed to find some errors in /var/log/messages that led me to Arch Linux forums where they said setting locales was the fix. So I did that in /etc/env.d/02locales and now its working. Im 100 % sure Ive set that file once already for this current Gentoo installation, but no idea why/where/how it mightve been removed.

Its been stable and doesnt seem to have memory leaks, thanks again!
Back to top
View user's profile Send private message
Tsigorf
n00b
n00b


Joined: 15 Jun 2017
Posts: 11

PostPosted: Thu Jun 15, 2017 11:33 am    Post subject: Compile errors, emerging Gnome Reply with quote

Hello there,

I am trying to setup my Gentoo on my new laptop so I decided to reinstall everything from the ground up.

I want to install Gnome like it was on my previous setup, however the installation failed on gnome-extra/gnome-contacts-3.22.1.

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

I tried again from a fresh official stage3 tarball, and selected Gnome 3.22 this time. Same error, from the same package.

Here are the errors (extract):

Code:

contacts-contact-editor.vala:680.19-680.30: error: Expected initializer of type `Folks.AbstractFieldDetails<string>' but got `Folks.PostalAddressFieldDetails'
   rows.set (row, { detail_field });
                    ^^^^^^^^^^^^
contacts-contact-editor.vala:680.17-680.17: error: Invalid type for argument 2
   rows.set (row, { detail_field });
                  ^
contacts-contact-editor.vala:687.23-687.26: error: Expected initializer of type `Folks.AbstractFieldDetails<string>' but got `Folks.PostalAddressFieldDetails'
       rows.set (row, { addr });
                        ^^^^
contacts-contact-editor.vala:687.21-687.21: error: Invalid type for argument 2
       rows.set (row, { addr });
                      ^
contacts-contact-pane.vala:314.17-314.72: warning: unhandled error `GLib.Error'
      var pix = icon_theme.load_icon ("avatar-default-symbolic", 144, 0);
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
contacts-contact-pane.vala:480.15-486.55: error: Too many arguments for specified format
Compilation failed: 9 error(s), 26 warning(s)


Please find my portage setup here:

Code:

localhost ~ # emerge --info '=gnome-extra/gnome-contacts-3.22.1::dantrell-gnome'
Portage 2.3.5 (python 3.4.5-final-0, !../../var/lib/layman/dantrell-gnome/profiles/default/amd64/3.22/extended, gcc-5.4.0, glibc-2.23-r3, 4.8.6-300.fc25.x86_64 x86_64)
=================================================================
                         System Settings
=================================================================
System uname: Linux-4.8.6-300.fc25.x86_64-x86_64-Intel-R-_Core-TM-_i7-7700HQ_CPU_@_2.80GHz-with-gentoo-2.3
KiB Mem:    16155860 total,   4770756 free
KiB Swap:    8388604 total,   8388604 free
Timestamp of repository gentoo: Thu, 15 Jun 2017 00:00:01 +0000
sh bash 4.3_p48-r1
ld GNU ld (Gentoo 2.26.1 p1.0) 2.26.1
app-shells/bash:          4.3_p48-r1::gentoo
dev-lang/perl:            5.24.1-r2::gentoo
dev-lang/python:          2.7.12::gentoo, 3.4.5::gentoo
dev-util/cmake:           3.7.2::gentoo
dev-util/pkgconfig:       0.28-r2::gentoo
sys-apps/baselayout:      2.3::gentoo
sys-apps/openrc:          0.26.3::gentoo
sys-apps/sandbox:         2.10-r3::gentoo
sys-devel/autoconf:       2.13::gentoo, 2.69::gentoo
sys-devel/automake:       1.11.6-r1::gentoo, 1.15-r2::gentoo
sys-devel/binutils:       2.26.1::gentoo, 2.28-r2::gentoo
sys-devel/gcc:            5.4.0-r3::gentoo
sys-devel/gcc-config:     1.7.3::gentoo
sys-devel/libtool:        2.4.6-r3::gentoo
sys-devel/make:           4.2.1::gentoo
sys-kernel/linux-headers: 4.4::gentoo (virtual/os-headers)
sys-libs/glibc:           2.23-r3::gentoo
Repositories:

gentoo
    location: /usr/portage
    sync-type: rsync
    sync-uri: rsync://rsync.gentoo.org/gentoo-portage
    priority: -1000

dantrell-gnome-3-22
    location: /var/lib/layman/dantrell-gnome-3-22
    masters: gentoo
    priority: 100

dantrell-gnome
    location: /var/lib/layman/dantrell-gnome
    masters: gentoo
    priority: 150

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe -march=native"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -pipe -march=native"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="fr_FR.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j9"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="X a52 aac acl acpi alsa amd64 berkdb bluetooth branding bzip2 cairo cdda cdr cli colord consolekit cracklib crypt cups cxx dbus dri dts dvd dvdr eds encode evo evolution exif fam flac fortran gdbm gif glamor gnome gnome-keyring gnome-online-accounts gpm gtk3 gtkstyle highlight iconv introspection ipv6 jpeg lcms ldap libnotify libsecret mad mng modules mp3 mp4 mpeg multilib nautilus ncurses nls nptl ogg opengl openmp pam pango pcre pdf png policykit ppds pulseaudio readline sdl seccomp session spell ssl startup-notification svg tcpd tiff tracker truetype udev udisks unicode upower usb vim-syntax vorbis x264 xattr xcb xml xv xvid zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx avx2 fma3 mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="evdev libinput joystick keyboard wacom" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="fr" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-6" PYTHON_SINGLE_TARGET="python3_4" PYTHON_TARGETS="python2_7 python3_4" RUBY_TARGETS="ruby21 ruby22" USERLAND="GNU" VIDEO_CARDS="intel nvidia nouveau" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CC, CPPFLAGS, CTARGET, CXX, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON


I haven't found similar errors anywhere on the internet, so I think I missed something in my setup, twice.

Can someone help me find the problem?

Thank you very much
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 ... 9, 10, 11 ... 27, 28, 29  Next
Page 10 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