Bug 1336618 - Why abrt not catch crashes of Wayland server?
Summary: Why abrt not catch crashes of Wayland server?
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matej Habrnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-17 03:01 UTC by Mikhail
Modified: 2016-05-26 17:32 UTC (History)
8 users (show)

Fixed In Version: abrt-2.8.1-1.fc24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-26 17:32:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl -b (5.22 MB, text/x-vhdl)
2016-05-17 03:01 UTC, Mikhail
no flags Details
json-pretty (1.41 MB, application/x-gzip)
2016-05-17 08:56 UTC, Mikhail
no flags Details

Description Mikhail 2016-05-17 03:01:40 UTC
Created attachment 1158156 [details]
journalctl -b

Description of problem:
Why abrt not catch crashes of Xorg server?

май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE)
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) Backtrace:
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x139) [0x5922c9]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7f013ddfdecf]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 2: /usr/bin/Xwayland (ddxProcessArgument+0x152) [0x424cb2]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 3: /usr/bin/Xwayland (CloseInput+0x7cc) [0x42754c]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 4: /usr/bin/Xwayland (FreeCursor+0x53) [0x54a673]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 5: /usr/bin/Xwayland (AddTraps+0x75f7) [0x4f6397]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 6: /usr/bin/Xwayland (FreeCursor+0x53) [0x54a673]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 7: /usr/bin/Xwayland (RegisterResourceName+0x235) [0x57bca5]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 8: /usr/bin/Xwayland (FreeClientResources+0x76) [0x57cd56]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 9: /usr/bin/Xwayland (CloseDownClient+0x6f) [0x5562bf]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 10: /usr/bin/Xwayland (SendErrorToClient+0x2ac) [0x556e4c]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 11: /usr/bin/Xwayland (remove_fs_handlers+0x463) [0x55aee3]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 12: /lib64/libc.so.6 (__libc_start_main+0xf1) [0x7f013dde9731]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 13: /usr/bin/Xwayland (_start+0x29) [0x4236a9]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) 14: ? (?+0x29) [0x29]
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE)
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) Segmentation fault at address 0x20
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE)
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: Fatal server error:
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE) Caught signal 11 (Segmentation fault). Server aborting
май 17 07:33:59 localhost.localdomain org.gnome.Shell.desktop[1951]: (EE)

Comment 1 Matej Habrnal 2016-05-17 08:49:46 UTC
Thank you for the bug report.

ABRT definitely should catch the crash. 
Was the ' /usr/bin/abrt-dump-journal-xorg' running while the crash occurred?
$ ps aux | grep abrt-dump-journal-xorg

'/usr/bin/abrt-dump-journal-xorg' filters out journal lines with '_COMM=gdm-x-session'. Could you please provide me more detailed information about the journal log you've attached to this bugzilla?
# journalctl -b -o json-pretty

Comment 2 Mikhail 2016-05-17 08:56:45 UTC
Created attachment 1158220 [details]
json-pretty

Comment 3 Mikhail 2016-05-17 19:55:53 UTC
> Was the ' /usr/bin/abrt-dump-journal-xorg' running while the crash occurred?

If it occurs again I think it impossible to check because this crash throws to login screen and all GUI applications will be closed.

Comment 4 Matej Habrnal 2016-05-18 07:32:36 UTC
The problem is the wayland crash is logged under different _COMM (namely '_COMM=gnome-shell') in journal so abrt cannot read them.

If you can reproduce the crash, please add '_COMM=gnome-shell' value to the 'JournalFilters' option in '/etc/abrt/plugins/xorg.conf' (after adding the value the configuration option should be 'JournalFilters = _COMM=gdm-x-session, _COMM=gnome-shell') and reproduce the crash.

Or you can manually run (with added '_COMM=gnome-shell' in '/etc/abrt/plugins/xorg.conf'):
# abrt-dump-journal-xorg -xDo

to extract crashes from journal.

Comment 5 Mikhail 2016-05-22 06:42:38 UTC
Thanks, I am added '_COMM=gnome-shell' in '/etc/abrt/plugins/xorg.conf' and run # abrt-dump-journal-xorg -xDo  and seems it worked.


[root@localhost ~]# nano /etc/abrt/plugins/xorg.conf
[root@localhost ~]# abrt-dump-journal-xorg -xDo
abrt-dump-journal-xorg: Found crashes: 4
abrt-dump-journal-xorg: Can't open file 'uid': No such file or directory
0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x5a4ad9]
1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7f10ba4c317f]
2: /usr/libexec/Xorg (present_extension_init+0x121) [0x520201]
3: /usr/libexec/Xorg (present_extension_init+0x67e) [0x520c5e]
4: /usr/libexec/Xorg (present_event_notify+0x216) [0x5215b6]
5: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xf0a35) [0x7f10b5502355]
6: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x5c763) [0x7f10b53d9c23]
7: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x5dfc7) [0x7f10b53dce27]
8: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x606be) [0x7f10b53e1c2e]
9: /usr/libexec/Xorg (InitExtensions+0x20a) [0x4af9ca]
10: /usr/libexec/Xorg (AddTraps+0x9182) [0x528af2]
11: /usr/libexec/Xorg (CompositeRegisterImplicitRedirectionException+0x413a) [0x4d1f5a]
12: /usr/libexec/Xorg (AddTraps+0x7441) [0x525011]
13: /usr/libexec/Xorg (remove_fs_handlers+0x580) [0x43ada0]
14: /lib64/libc.so.6 (__libc_start_main+0xf1) [0x7f10ba4ad721]
15: /usr/libexec/Xorg (_start+0x29) [0x424b39]
16: ? (?+0x29) [0x29]
Segmentation fault at address 0x10

abrt-dump-journal-xorg: Can't open file 'uid': No such file or directory
0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59fb99]
1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7f927234117f]
2: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x17617) [0x7f926d1cdb47]
3: /usr/libexec/Xorg (present_extension_init+0x5cd) [0x51bd4d]
4: /usr/libexec/Xorg (present_extension_init+0x695) [0x51bf25]
5: /usr/libexec/Xorg (present_extension_init+0xe02) [0x51cdf2]
6: /usr/libexec/Xorg (AddTraps+0x9103) [0x523cb3]
7: /usr/libexec/Xorg (CompositeRegisterImplicitRedirectionException+0x412a) [0x4cd36a]
8: /usr/libexec/Xorg (AddTraps+0x73e1) [0x520201]
9: /usr/libexec/Xorg (remove_fs_handlers+0x580) [0x43ae50]
10: /lib64/libc.so.6 (__libc_start_main+0xf1) [0x7f927232b721]
11: /usr/libexec/Xorg (_start+0x29) [0x424b89]
12: ? (?+0x29) [0x29]
Segmentation fault at address 0x20

abrt-dump-journal-xorg: Can't open file 'uid': No such file or directory
0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59fbd9]
1: /lib64/libc.so.6 (?+0x139) [0x7fa4782432b8]
2: /usr/libexec/Xorg (present_event_notify+0x37) [0x51c747]
3: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xf0a35) [0x7fa473282355]
4: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x5c763) [0x7fa473159c23]
5: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x60478) [0x7fa473161758]
6: /usr/libexec/Xorg (WakeupHandler+0xa4) [0x43b894]
7: /usr/libexec/Xorg (WaitForSomething+0x1e9) [0x598569]
8: /usr/libexec/Xorg (SendErrorToClient+0x10e) [0x436b4e]
9: /usr/libexec/Xorg (remove_fs_handlers+0x463) [0x43ad83]
10: /lib64/libc.so.6 (?+0x463) [0x7fa47822da93]
11: /usr/libexec/Xorg (_start+0x29) [0x424bc9]
12: ? (?+0x29) [0x29]
Segmentation fault at address 0x50

abrt-dump-journal-xorg: Can't open file 'uid': No such file or directory
0: /usr/bin/Xwayland (OsLookupColor+0x139) [0x5922c9]
1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7f013ddfdecf]
2: /usr/bin/Xwayland (ddxProcessArgument+0x152) [0x424cb2]
3: /usr/bin/Xwayland (CloseInput+0x7cc) [0x42754c]
4: /usr/bin/Xwayland (FreeCursor+0x53) [0x54a673]
5: /usr/bin/Xwayland (AddTraps+0x75f7) [0x4f6397]
6: /usr/bin/Xwayland (FreeCursor+0x53) [0x54a673]
7: /usr/bin/Xwayland (RegisterResourceName+0x235) [0x57bca5]
8: /usr/bin/Xwayland (FreeClientResources+0x76) [0x57cd56]
9: /usr/bin/Xwayland (CloseDownClient+0x6f) [0x5562bf]
10: /usr/bin/Xwayland (SendErrorToClient+0x2ac) [0x556e4c]
11: /usr/bin/Xwayland (remove_fs_handlers+0x463) [0x55aee3]
12: /lib64/libc.so.6 (__libc_start_main+0xf1) [0x7f013dde9731]
13: /usr/bin/Xwayland (_start+0x29) [0x4236a9]
14: ? (?+0x29) [0x29]
Segmentation fault at address 0x20

Comment 6 Mikhail 2016-05-22 06:43:44 UTC
What means this message "Can't open file 'uid': No such file or directory"?

Comment 9 Matej Habrnal 2016-05-24 05:59:57 UTC
(In reply to Mikhail from comment #6)
> What means this message "Can't open file 'uid': No such file or directory"?

In same cases uid doesn't have to exist in time of dumdir creating, following commit fixes the issue:
https://github.com/abrt/libreport/commit/460cfda0ed256c5358e72fc41d7f76042efd971b

I've opened pull request which fixes the bugzilla:
https://github.com/abrt/abrt/pull/1147

Comment 10 Matej Habrnal 2016-05-25 07:47:45 UTC
This upstream commit fixes the issue:
https://github.com/abrt/abrt/commit/8473a6bb8dcf086b31a9eb0b76b0a182dc9a1b1e

Comment 11 Fedora Update System 2016-05-25 10:21:39 UTC
abrt-2.8.1-1.fc24 libreport-2.7.1-1.fc24 satyr-0.21-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d1a3dbcc35

Comment 12 Fedora Update System 2016-05-26 05:02:19 UTC
abrt-2.8.1-1.fc24, libreport-2.7.1-1.fc24, satyr-0.21-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d1a3dbcc35

Comment 13 Fedora Update System 2016-05-26 17:32:12 UTC
abrt-2.8.1-1.fc24, libreport-2.7.1-1.fc24, satyr-0.21-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.