Version-Release number of selected component: gnome-shell-3.26.2-1.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: raise executable: /usr/bin/gnome-shell journald_cursor: s=f7c4202e5e48451092604b36df4c49b7;i=94422;b=245285af7fad4d5bbcda7aa08bfef181;m=45c04e4;t=55f09879c4c06;x=7cc9ddc14cc215a0 kernel: 4.13.15-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (2 frames) #0 raise at ../sysdeps/unix/sysv/linux/raise.c:51 #1 dump_gjs_stack_on_signal_handler at ../src/main.c:372 This is a private, duplicate bug report of bug 1517009. The report has been created because Bugzilla cannot grant access to a comment for a specific group.
Created attachment 1359793 [details] File: backtrace
Created attachment 1359794 [details] File: cgroup
Created attachment 1359795 [details] File: core_backtrace
Created attachment 1359796 [details] File: cpuinfo
Created attachment 1359797 [details] File: dso_list
Created attachment 1359798 [details] File: environ
Created attachment 1359799 [details] File: limits
Created attachment 1359800 [details] File: maps
Created attachment 1359801 [details] File: mountinfo
Created attachment 1359802 [details] File: open_fds
Created attachment 1359803 [details] File: proc_pid_status
Created attachment 1359804 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 1517009 ***
This does not in fact look like a duplicate of 1517009 or 1510059. This seems to be another case of "Too many open files", like #1516553 and #1513492. The error here appears to be "Creating pipes for GWakeup: Too many open files", which looks the same as #1516553. I'm still not sure if they can be truly considered dupes, though, so leaving open for now.
*** Bug 1520228 has been marked as a duplicate of this bug. ***
So, using the debugging tip Ray provided in https://bugzilla.redhat.com/show_bug.cgi?id=1516553#c15 (and modifying it a bit), we see: 252 anon_inode:[timerfd] 269 /home/jun/Pictures/Wallpapers 299 /home/jun/Pictures/Wallpapers/bak so we do have the leak identified in that bug active here too (252 open fds for timerfd), but we also have something else going on - open fds for your wallpapers directories. The update to fix the timerfd bug - https://bodhi.fedoraproject.org/updates/FEDORA-2017-7758521ad4 - should help you, but it may not fully solve the problem. Can you try it and see? Do you have any extensions that deal with wallpapers at all, that could be involved here? Ray, any ideas on this one? Thanks!
var_log_messages here lists these extensions: dash-to-dock.com sound-output-device-chooser drop-down-terminal.org alternate-tab.github.com apps-menu.github.com launch-new-instance.github.com places-menu.github.com window-list.github.com user-theme.github.com gravatar.io but that may not be exhaustive, as it's a filtered log.
*** Bug 1499587 has been marked as a duplicate of this bug. ***
i have an extension about that is https://extensions.gnome.org/extension/1000/random-walls/ if i can be of any help to you.
Yes, in fact, that could very well be the cause: I just came across another crash report with similar symptoms where the reporter had the same extension enabled - https://bugzilla.redhat.com/show_bug.cgi?id=1506435 . I filed an upstream issue for this - https://github.com/rodakorn/randwall/issues/34 . Can you try disabling that extension and see if it makes the crashes go away, if they're happening frequently? Thanks!
OK. i will try to disable that extension a couple of week and report again in this year.
i had down gnome-shell and report below.(it may be another reason) https://bugzilla.redhat.com/show_bug.cgi?id=1517433 btw, i can NOT access below url (not authorized) Is it related issue ? https://bugzilla.redhat.com/show_bug.cgi?id=1506435
The other crash you're hitting is different, yes. As the duplication closures indicate, it's https://bugzilla.redhat.com/show_bug.cgi?id=1469129 . Not the same as this at all. "btw, i can NOT access below url (not authorized)" yeah, lots of the crash reports we're dealing with here are set to private because abrt defaults to reporting private bugs any time it thinks it saw sensitive information in the bug report data, and it's *way* too sensitive; it will assume any occurrence of 'key' or 'user' in the data could indicate sensitive information, for instance. So bug reports often wind up getting set private when they don't need to be. I'm trying to get the important ones marked as *not* private, but it requires me to check through the attachments carefully and (ideally) contact the reporter, so it's slow.
On that note...do you mind if I mark this report as public, and mark the backtrace and open_fds attachments as public, but leave the other attachments private? I'm pretty sure there's no personal data in any of the attachments, but just opening up those two should be all people need to understand the bug.
I will report again as I promised. I spent a couple week that removed random-walls extension and I had never killed gnome-shell by this issue. I think effective was.
OK, thanks. On that basis I'll close this as UPSTREAM, indicating it's an issue in the extension, and thus we can't fix it in Fedora - it needs to be fixed by the extension author upstream. Thanks!
*** Bug 1559825 has been marked as a duplicate of this bug. ***
*** Bug 1562420 has been marked as a duplicate of this bug. ***
I've had a few of these crashes which bugzilla now when reported 1562420 thinks is a duplicate of this now CLOSED UPSTREAM bug. However, I have never used random-walls extension, so hardly that is a reason for my gnome-shell crashes.
*** Bug 1565161 has been marked as a duplicate of this bug. ***
*** Bug 1565216 has been marked as a duplicate of this bug. ***
*** Bug 1565238 has been marked as a duplicate of this bug. ***
I don't use this "random-walls" extension either, but report-cli detected my bug as a duplicate of this one.
*** Bug 1572829 has been marked as a duplicate of this bug. ***
Similar problem has been detected: opena torcs game and crash after 1 minutes reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: raise executable: /usr/bin/gnome-shell journald_cursor: s=f437cb100a7645e6a861f4cdb121bb69;i=de66;b=ca1ff82c12e342cd8a9678ab7bb22aad;m=2c80b11af;t=56bd7e373b37a;x=1d0b87d005d60bba kernel: 4.14.6-300.fc27.x86_64 package: gnome-shell-3.26.2-5.fc27 reason: gnome-shell killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: VLC crashed me reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: raise executable: /usr/bin/gnome-shell journald_cursor: s=a2c7ec1885d74083a4fa5a1e34d765f0;i=5971;b=a264d3f2af1745a2a87e99bc5a49838c;m=c3c1e922a;t=56bf983d348a9;x=6e263d5100505e92 kernel: 4.16.6-202.fc27.x86_64 package: gnome-shell-3.26.2-5.fc27 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I had already pluged in a monitor on my mini-display port of my laptop and wanted to add another monitor (AOC) on the HDMI port. First there was no reaction at all and I unplugged it again, then in, then out, then in and I waited for a couple of seconds. The monitor seemed to have been noticed but then I was thrown back to the login screen... There cable might be a bit broken or the port is a bit lose because sometimes it doesn't work continuesly after plugin. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: raise executable: /usr/bin/gnome-shell journald_cursor: s=7f5c42992a8e4a8b87b1bcba09adb589;i=2f9c3;b=ddcafd8da16a407e98052bb23de3fd9e;m=259e13c7c4;t=56e9516e3c58a;x=ce5ed294e219a7ab kernel: 4.16.13-200.fc27.x86_64 package: gnome-shell-3.26.2-5.fc27 reason: gnome-shell killed by SIGFPE rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1643643 has been marked as a duplicate of this bug. ***