Description of problem: I simply turn on the laptop and gdm crashes. I switched to lightdm in order to login. Version-Release number of selected component: gnome-shell-3.13.91-1.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gnome-shell --mode=gdm crash_function: _cogl_set_error executable: /usr/bin/gnome-shell kernel: 3.16.2-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 42 Truncated backtrace: Thread no. 1 (10 frames) #1 _cogl_set_error at ./cogl-error.c:83 #2 allocate_from_gl_foreign at driver/gl/cogl-texture-2d-gl.c:386 #3 _cogl_texture_2d_gl_allocate at driver/gl/cogl-texture-2d-gl.c:470 #4 cogl_texture_allocate at ./cogl-texture.c:1398 #5 cogl_texture_2d_new_from_data at ./cogl-texture-2d.c:225 #6 meta_background_load_file_finish at compositor/meta-background.c:1033 #7 ffi_call_unix64 at ../src/x86/unix64.S:76 #8 ffi_call at ../src/x86/ffi64.c:525 #9 gjs_invoke_c_function at gi/function.cpp:972 #10 function_call at gi/function.cpp:1294
Created attachment 937964 [details] File: backtrace
Created attachment 937965 [details] File: cgroup
Created attachment 937966 [details] File: core_backtrace
Created attachment 937967 [details] File: dso_list
Created attachment 937968 [details] File: environ
Created attachment 937969 [details] File: limits
Created attachment 937970 [details] File: maps
Created attachment 937971 [details] File: open_fds
Created attachment 937972 [details] File: proc_pid_status
Created attachment 937973 [details] File: var_log_messages
I've got the same problem. My video card is an Intel one (i915). If booting kernel with "nomodeset" (or in "safe mode" from live) gdm doesn't crash.
'nomodeset' also avoids the crash for me. My system is an old Lenovo T60 laptop with: ~]$ lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) ~]$ grep -i intel /var/log/Xorg.0.log [ 47.447] (==) Matched intel as autoconfigured driver 0 [ 47.447] (==) Matched intel as autoconfigured driver 1 [ 47.447] (II) LoadModule: "intel" [ 47.450] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 47.450] (II) Module intel: vendor="X.Org Foundation" [ 47.458] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: [ 47.458] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [ 47.458] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [ 47.458] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 [ 47.465] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20080730 [ 47.467] (--) intel(0): Integrated Graphics Chipset: Intel(R) 945GM ...
Same here. segfault with modeset (no graphic login), all fine with nomodeset. [root@localhost lalmeras]# lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) [root@localhost lalmeras]# rpm -qa gnome-shell gnome-shell-3.13.91-1.fc21.i686 [root@localhost lalmeras]# rpm -qa xorg-x11-drv-intel xorg-x11-drv-intel-2.99.914-3.fc21.i686 [root@localhost lalmeras]# rpm -qa gnome-shell gnome-shell-3.13.91-1.fc21.i686 [root@localhost lalmeras]# rpm -qa kernel kernel-3.16.1-301.fc21.i686
The update to gdm-3.13.92-1.fc21.x86_64 *and other gnome 3.13.92 packages) has fixed this for me: gdm does not crash with kernel modesetting enabled.
Same here, gdm doesn't crash with 3.13.92 update. I think we can close this bug.
Another user experienced a similar problem: I don't know what the reason for this accident was. Maybe it is the thing with "Oh No! Something went wrong" (not loginable without this error.) reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _cogl_set_error executable: /usr/bin/gnome-shell kernel: 3.17.4-301.fc21.x86_64 package: gnome-shell-3.14.2-1.fc21 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
My gfxcard is: VGA compatible controller [0300]: NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1)
Another user experienced a similar problem: Installed Fedora 21 workstation using anaconda network installation method (booted from USB). The installation source was http://nic.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/21/Everything/i386/os I selected Workstation from the anaconda installation options. Once the Fedora 21 was installed and rebooted, the gnome presented login screen. I logged in and after a while got error "Oh no something has been gone wrong"..... Tried to boot several times, but always the same error after login. Then I ran yum update-minimal and yum install gnome* to fix the issue. Still the same results. I ran init 3 from the console window and run startx to open gnome-desktop. This opened gnome desktop. The problem reporting started from the bottom panel. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _cogl_set_error executable: /usr/bin/gnome-shell kernel: 3.17.4-301.fc21.i686+PAE package: gnome-shell-3.14.2-1.fc21 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: - synergy was running at the time of crash. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _cogl_set_error executable: /usr/bin/gnome-shell kernel: 3.18.3-201.fc21.x86_64 package: gnome-shell-3.14.3-1.fc21 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I get this error on chrome start. Perhaps related, if I start chrome and then maximize the window by double clicking on the top bar of the frame, gnome-shell crashes with the "whoops and logout button" thought it was related to: https://bugzilla.redhat.com/show_bug.cgi?id=1193801 but, I did the work around, and continue to experience it. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _cogl_set_error executable: /usr/bin/gnome-shell kernel: 3.19.3-200.fc21.x86_64 package: gnome-shell-3.14.4-2.fc21 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
(In reply to Langdon White from comment #20) > Another user experienced a similar problem: > > I get this error on chrome start. Perhaps related, if I start chrome and > then maximize the window by double clicking on the top bar of the frame, > gnome-shell crashes with the "whoops and logout button" > > thought it was related to: > https://bugzilla.redhat.com/show_bug.cgi?id=1193801 but, I did the work > around, and continue to experience it. > > reporter: libreport-2.3.0 > backtrace_rating: 4 > cmdline: /usr/bin/gnome-shell > crash_function: _cogl_set_error > executable: /usr/bin/gnome-shell > kernel: 3.19.3-200.fc21.x86_64 > package: gnome-shell-3.14.4-2.fc21 > reason: gnome-shell killed by SIGTRAP > runlevel: N 5 > type: CCpp > uid: 1000 please strike "I get this error on chrome start. " (bad c/p)
I get this only when I interact with the chrome menu bar while using synergyc. I have "Use system title bar and borders" unchecked.
(In reply to Jesus M. Rodriguez from comment #22) > I get this only when I interact with the chrome menu bar while using > synergyc. I have "Use system title bar and borders" unchecked. also happens if I check "Use system title bar and borders". synergy-1.6.2-1.fc21.x86_64 gnome-shell-3.14.4-2.fc21.x86_64
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.