Created attachment 942632 [details]
File: backtrace

Created attachment 942633 [details]
File: cgroup

Created attachment 942634 [details]
File: core_backtrace

Created attachment 942635 [details]
File: dso_list

Created attachment 942636 [details]
File: environ

Created attachment 942637 [details]
File: exploitable

Created attachment 942638 [details]
File: limits

Created attachment 942639 [details]
File: maps

Created attachment 942640 [details]
File: open_fds

Created attachment 942641 [details]
File: proc_pid_status

Created attachment 942642 [details]
File: var_log_messages

Probably the same bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1141232
for Gnome 3.13

I'm seing the same crash with:
gnome-shell-3.14.2-1.fc21.x86_64
wayland-1.6.0-1.fc21.x86_64

So far this seems to happen every time I try to log in to a gnome wayland session from gdm. I don't see gnome-shell at all and are left with a black screen.

I found a workaround to fix the problem for me:
rmmod acer_wmi
or blacklist it. If the acer_wmi module is not loaded I can succesfully log into wayland gnome and everything works flawlessly. My laptop is a lenovo and not an acer

(In reply to Ermanno Saglione from comment #14)
> I found a workaround to fix the problem for me:
> rmmod acer_wmi
> or blacklist it. If the acer_wmi module is not loaded I can succesfully log
> into wayland gnome and everything works flawlessly. My laptop is a lenovo
> and not an acer

I've finally been able to launch a Wayland session after 'rmmod acer_wmi'. Mine is an Acer laptop.

(In reply to Ermanno Saglione from comment #14)
> I found a workaround to fix the problem for me:
> rmmod acer_wmi

Confirming, this works for me as well. I can successfully log in to a wayland session after removing the acer_wmi module.

This is a Sony laptop with Intel integrated graphics using the i915 driver.

kernel-3.17.8-300.fc21.x86_64

(In reply to Ermanno Saglione from comment #14)

Works for me with blacklisted acer_wmi. Thanks!
Notebook Acer Aspire One 756

I have removed Fedora. Now I have Debian 8 Jessie with Gnome 3.14. With default kernel acer_wmi is loaded on my Acer Aspire E1-531G laptop and Gnome/Wayland doesn't work. When I unloaded acer_wmi module Gnome/Wayland could indeed start.

(In reply to Ermanno Saglione from comment #14)

Ok, so this workaround works. I ended up blacklisting the module myself for my Acer Aspire 5742-7789. I have to thank you for that. 

But that does ask a question, why does wayland fail when the module is active? I am guessing that there might be a conflict with it, considering that the module does have screen control functions (namely for the LCD backlighting). But as of right now... I would not know. 

Would it be worth it to dig into this deeper?

Can one of you attach the full journal output around the time it crashes?

Another experiment that might be useful is switch to a VT and run:

$ gnome-session --session=gnome-wayland > /tmp/gnome-session.txt 2>&1

And then attach the /tmp/gnome-session.txt file here after it crashes.

*** Bug 1113711 has been marked as a duplicate of this bug. ***

I tried and /tmp/gnome-session.txt is empty.
The acer_wmi supports the accelerometer in my laptop:

[77355.728992] acer_wmi: Acer Laptop ACPI-WMI Extras
[77355.732062] acer_wmi: Brightness must be controlled by acpi video driver
[77355.733695] input: Acer BMA150 accelerometer as /devices/virtual/input/input14
[77367.388938] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[77367.500451] gnome-shell[15672]: segfault at 28 ip 00007fa642bb3eb5 sp 00007fff86252e78 error 4 in libgobject-2.0.so.0.4200.1[7fa642b81000+4f000]

There is a bug reports regarding weston and the input device provided by acer_wmi:
https://bugs.freedesktop.org/show_bug.cgi?id=64506
maybe it is the same problem?

There isn't a lot going on the journal as well:
feb 16 20:52:25 lenovo gdm-Xorg-:0[14527]: (II) config/udev: Adding input device Acer BMA150 accelerometer (/dev/input/event7)
feb 16 20:52:25 lenovo gdm-Xorg-:0[14527]: (II) No input driver specified, ignoring this device.
feb 16 20:52:25 lenovo gdm-Xorg-:0[14527]: (II) This device may have been added with another device file.
feb 16 20:53:01 lenovo gnome-session[15539]: gnome-session[15539]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
feb 16 20:53:01 lenovo gnome-session[15539]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
feb 16 20:53:01 lenovo kernel: SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
feb 16 20:53:01 lenovo gnome-session[15539]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
feb 16 20:53:01 lenovo gnome-session[15539]: gnome-session[15539]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
feb 16 20:53:01 lenovo kernel: gnome-shell[15564]: segfault at 28 ip 00007fe501ce5eb5 sp 00007fff6b7153b8 error 4 in libgobject-2.0.so.0.4200.1[7fe501cb30
feb 16 20:53:02 lenovo gnome-session[15539]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 11
feb 16 20:53:02 lenovo gnome-session[15539]: gnome-session[15539]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 11

Debian 8 Jessie with Gnome 3.14 with acer_wmi module loaded.


[   89.596307] gnome-shell[1410]: segfault at 18 ip 00007f7401fc27ee sp 00007fffe759a2b0 error 4 in libcogl.so.20.2.0[7f7401f50000+a0000]
Next
[   12.587375] acer_wmi: Acer Laptop ACPI-WMI Extras
[   12.587541] acer_wmi: Function bitmap for Communication Button: 0x1
[   13.254337] acer_wmi: Brightness must be controlled by acpi video driver
[   13.485951] acer_wmi: Enabling Launch Manager failed: 0xe2 - 0x0
-- Logs begin at pon 2015-02-16 22:12:38 CET, end at pon 2015-02-16 22:17:02 CET. --
lut 16 22:13:04 debian gnome-session[1243]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary
lut 16 22:13:04 debian gnome-session[1243]: gnome-session[1243]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary
lut 16 22:13:07 debian gnome-session[1243]: Entering running state
lut 16 22:13:07 debian gnome-session[1243]: openConnection: connect: Nie ma takiego pliku ani katalogu
lut 16 22:13:07 debian gnome-session[1243]: cannot connect to brltty at :0
lut 16 22:13:18 debian gnome-session[1243]: Gjs-Message: JS LOG: Failed to launch ibus-daemon: Wykonanie procesu potomnego "ibus-daemon" (Nie ma takiego pliku ani katalogu) się nie powiodło
lut 16 22:13:22 debian gnome-session[1243]: Gjs-Message: JS LOG: GNOME Shell started at Mon Feb 16 2015 22:13:19 GMT+0100 (CET)
lut 16 22:13:40 debian gnome-session[1243]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
lut 16 22:13:40 debian gnome-session[1243]: (gnome-settings-daemon:1264): GLib-GIO-WARNING **: Error releasing name org.gnome.SettingsDaemon: Połączenie jest zamknięte
lut 16 22:13:40 debian gnome-session[1243]: (gnome-shell:1293): Gdk-WARNING **: gnome-shell: Fatal IO error 4 (Przerwane wywołanie systemowe) on X server :0.
lut 16 22:13:40 debian gnome-session[1243]: (gnome-settings-daemon:1264): GLib-GIO-WARNING **: Invalid id 6 passed to g_bus_unown_name()
lut 16 22:13:40 debian gnome-session[1243]: (gnome-settings-daemon:1264): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 2 (Nie ma takiego pliku ani katalogu) on X server :0.
lut 16 22:14:01 debian gnome-session[1401]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
lut 16 22:14:01 debian gnome-session[1401]: gnome-session[1401]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
lut 16 22:14:03 debian gnome-session[1401]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 11
lut 16 22:14:03 debian gnome-session[1401]: gnome-session[1401]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 11
lut 16 22:14:03 debian gnome-session[1401]: Unrecoverable failure in required component gnome-shell-wayland.desktop
gnome-session 3.14.0

Created attachment 992639 [details]
full journalctl using gnome-session --session=gnome-wayland --debug

full journal right after the crash with gnome-session --session=gnome-wayland --debug

BTW I have filled bug report upstream, because as I said, it affects also Debian 8 Jessie with Gnome 3.14:
https://bugzilla.gnome.org/show_bug.cgi?id=744545

Created attachment 992844 [details]
strace log of gnome-shell-wayland

the last thing it does before crashing is open the accelerometer input device:

[ermanno@lenovo erm67]$ cat /sys/devices/virtual/input/input12/name 
Acer BMA150 accelerometer

I am installing all the required debuginfo, I will attempt later to start it under gdb.

@ Ermanno Scaglione 
I am not a developer but I think this maybe helpfull for them. Can you provide what prints this command from root account?
lsmod | grep -i -e wmi -e acpi

I cannot start it unde gdb because it grabs the keyboard and I cannot interact with gdb. If I can find some time I will set up a gdb-server and debug remotely.


6911  read(24, "I:591374737\nE:ID_INPUT=1\nE:ID_IN"..., 4096) = 52
6911  read(24, "", 4096)                = 0
-->>  6911  close(24)                         = 0
6911  munmap(0x7fcf46d88000, 4096)      = 0
6911  stat("/dev/input/event11", {st_mode=S_IFCHR|0660, st_rdev=makedev(13, 75), ...}) = 0
6911  eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 24
-->>  6911  write(24, "\1\0\0\0\0\0\0\0", 8)  = 8
6911  write(7, "\1\0\0\0\0\0\0\0", 8)   = 8

Looking at the strace hwever it looks like it closes the filedescriptor 24 and the very last thing it does is write to a closed file descriptor a few syscalls later.

nope, sorry for the noise, the fledescriptor 24 is closed and reopened agan by eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 24
The lsmod wth and without acer_wmi.

[ermanno@lenovo erm67]$ lsmod | grep -i -e wmi -e acpi
thinkpad_acpi          79105  2 
wmi                    18820  0 
rfkill                 21980  3 cfg80211,thinkpad_acpi
snd                    80001  24 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device
[ermanno@lenovo erm67]$ modprobe acer_wmi
[ermanno@lenovo erm67]$ lsmod | grep -i -e wmi -e acpi
acer_wmi               19691  0 
sparse_keymap          13584  1 acer_wmi
thinkpad_acpi          79105  2 
wmi                    18820  1 acer_wmi
rfkill                 21980  4 cfg80211,acer_wmi,thinkpad_acpi
snd                    80001  24 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device
video                  19905  2 i915,acer_wmi

The problem disappeared in Fedora 22 Alpha, there are no more problems starting gnome-wayland with the acer_wmi module enabled

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.