Bug 1062796
| Summary: | [abrt] mate-control-center: gdk_event_apply_filters(): mate-display-properties killed by SIGSEGV | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vladmir Poplavskij <float45> | ||||||||||||||||||||||||||||
| Component: | gtk2 | Assignee: | Matthias Clasen <mclasen> | ||||||||||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||||
| Version: | rawhide | CC: | aaron.lwe, admin, al.dunsmuir, beniciu, blackpearl, brian, bugzilla, bugzilla, clintpollitt, dan.mashal, david.valdez, diego.ml, dir2006, d.kraemer, dominik, edgardo.rios, fedora, giuseppemfusco, jfrieben, jonataszv, jwrigley7, leigh123linux, mclasen, panos.ioannidis, pascal, patrick, Petaris, rabin, rdieter, rhce_v6, rokeso, samtygier, ScientificEquality, sdijkstra, skycarl, smeisner, softwaveltd, stefano, twegener, uma.angeldos, unixi, wielkipiec, Wilhelm.Buchmueller, william, zbechir, zhoujian8585169 | ||||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||||
| Hardware: | All | ||||||||||||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/32f0686be19c48944a177e75c2ae6b12855f4f1e | ||||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:d846a348b491fadcb493916daf11e77732bc4a5d | ||||||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||||
| Last Closed: | 2015-02-24 13:15:38 UTC | Type: | --- | ||||||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||||
|
Description
Vladmir Poplavskij
2014-02-08 02:58:38 UTC
Created attachment 860786 [details]
File: backtrace
Created attachment 860787 [details]
File: cgroup
Created attachment 860788 [details]
File: core_backtrace
Created attachment 860789 [details]
File: dso_list
Created attachment 860790 [details]
File: environ
Created attachment 860791 [details]
File: limits
Created attachment 860792 [details]
File: maps
Created attachment 860793 [details]
File: open_fds
Created attachment 860794 [details]
File: proc_pid_status
Created attachment 860795 [details]
File: var_log_messages
Created attachment 860796 [details]
File: exploitable
Can you describe a little more detailed what happend? Did this issue occurs frequently ? *** Bug 925996 has been marked as a duplicate of this bug. *** abrt directs here - I always have this problem when I use system->preference->monitors to change resolution, e.g. the native resolution is 2560x1440 for my monitor, when I change it to 1280x720 I get the abrt icon pop up. But when I change resolution back to 2560x1440 from 1280x720, there is no abrt icon pop up. I often need to change resolution in VNC session and saw this problem often: 1 change from 1360x768 -> 1280x800, abrt pop up; 2 change from 1280x800 -> 1360x768, no abrt icon; 3 change from 1360x768 -> 1280x720, abrt pop up; 4 change from 1280x720 -> 1360x768, no abrt icon. Please let me know if you need any more information, thanks. forward to upstream https://github.com/mate-desktop/mate-control-center/issues/86 Pls answer there if upstream asked for more info's. new upstream report for this. https://github.com/mate-desktop/mate-control-center/issues/48 Running fedora 20 in KVM. When I change display to 1440x900 resolution this happens. Seems pretty repeatable. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.11.10-301.fc20.x86_64 package: mate-control-center-1.6.2-2.fc20 reason: Process /usr/bin/mate-display-properties was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000 Used nvidia-settings to set up dual monitor and then opened mate-display-properties to see if it propagated and hit apply. Then it crashed. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.11.10-301.fc20.x86_64 package: mate-control-center-1.6.1-3.fc20 reason: Process /usr/bin/mate-display-properties was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000 Crashed while logged into root to reorient the login screen. Used mate-display before nvidia-settings. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.11.10-301.fc20.x86_64 package: mate-control-center-1.6.1-3.fc20 reason: Process /usr/bin/mate-display-properties was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 0 Another user experienced a similar problem: I simply changed the layout of the monitors and hit apply. The main program disappeared and after the screen refresh the confirmation box of keeping this configuration remained. I clicked keep configuration and then I noticed this error. Thanks. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.14.4-200.fc20.x86_64 package: mate-control-center-1.6.2-2.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 *** Bug 1112075 has been marked as a duplicate of this bug. *** *** Bug 1114093 has been marked as a duplicate of this bug. *** Another user experienced a similar problem: Occured after update of mate control panel reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.14.9-200.fc20.x86_64 package: mate-control-center-1.6.2-2.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 *** Bug 1058429 has been marked as a duplicate of this bug. *** *** Bug 1121722 has been marked as a duplicate of this bug. *** *** Bug 1028952 has been marked as a duplicate of this bug. *** Another user experienced a similar problem: switching on gdmi between 24 and 25 hz reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.16.3-200.fc20.i686+PAE package: mate-control-center-1.8.2-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 *** Bug 879663 has been marked as a duplicate of this bug. *** Another user experienced a similar problem: Resumed from hibernate and monitors were not setup properly. I ran display properties to try and fix it. This is when I got the notification that there was a segv fault. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.17.2-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: Plugged in external monitor into the HDMI port on the docking station (Platform is Lenovo T440s with an Ultra Dock) reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.17.2-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 *** Bug 1167287 has been marked as a duplicate of this bug. *** Another user experienced a similar problem: Turning off laptop lcd. Using external monitor reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.17.3-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I just was trying to change display settings and turn laptop monitor off. Usual sequence seems to have changed. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.17.3-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: When configuring to use two monitors, extended desktop. Installed NVIDIA official drivers. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.17.3-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I was configuring a two-monitor display setup. My promary monitor was set up properly at 1366x768 @60Hz at boot. I set my secondary to its maximum resolution of 1920x1080 @60Hz. By default, the secondary monitor was set to the right side. I moved it to the right side, with the bottom edge aligned with the bottom edge of the primary monitor. The primary monitor is identified by the program as an Acer Technologies 19" monitor, but is an eMachines E181H TFT. The secondary monitor is identified as a WDT 52", but is a Westinghouse EW32S5KW. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.17.3-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: plugged external monitor to laptop after power came back reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.17.3-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 *** Bug 1168919 has been marked as a duplicate of this bug. *** Another user experienced a similar problem: Switching HDMI monitor 1920x1080 from 30Hz (60i) to 25Hz (50i) and vice versa. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.17.3-200.fc20.i686+PAE package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: As far as I can tell, this problem happened as follows. 1. Initial Configuration, two displays: eDP-0 - Off HDMI - On (default display) 2. Select 'Lock Screen' 3. After I selected 'Lock Screen', both displays were enabled, and 'eDP-0' become default display. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.17.4-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: Resuming from suspend reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.17.4-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I changed the screen resolution and even though the resolution changed to the new one, I also got this message. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.17.6-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: Resumed from hibernate reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.17.6-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: After attaching a 1360x768 VGA TV I opened mate-display-properties and it crashed immediately reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.17.4-200.fc20.i686 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I clicked on System->Preferences->Hardware->Monitors and the screen went blank for a second and came back with factory set resolution. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.17.6-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 hi guys, sorry for that, i'm aware of this issue and me and upstream can reproduce it. We're working on it but it seems to be a low-level problem which isn't easy. Good news, it never happens in Mate GTK3. Another user experienced a similar problem: Dell Precision M6700 with NVidia 340 drivers. Was configuring dual head. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.17.7-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I switched my desktop display to have my laptop screen on the right side rather than the left. Immediately thereafter, I saw the error. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.17.4-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: plugged in rom projector to vga port reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.17.7-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: It happens everytime when I change settings in Monitor Preferences app. The error occurs when I click on the Aply button. I use Dell Latitude E7440 laptop with external monitor. The laptop is docked and the external monitor is connected to the dock. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.17.7-200.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 A Mate dev has track down the issue, it's a problem with gtk2 package. There is a GTK3 commit which was never been applied to GTK2 branch. https://git.gnome.org/browse/gtk+/commit/?id=323df2b2800383832ed3c2e43626f2c6821c33ec A adjusted patch for gtk2 package fixes the issue in a local build. Created attachment 988860 [details]
fix for gtk2 package
Another user experienced a similar problem: Change display resolution. Always occurs. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.18.5-101.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 The patch doesn't apply here. Created attachment 991450 [details]
fix-gdk-event-apply-filters
updated patch
Opps, for some reasons there was 1 unnecessary space line at the end of the patch. New version builds fine at koji. f20: http://koji.fedoraproject.org/koji/taskinfo?taskID=8922543 f21: http://koji.fedoraproject.org/koji/taskinfo?taskID=8922569 f22 fails due an issue with autotools https://kojipkgs.fedoraproject.org//work/tasks/2645/8922645/build.log I quess support for automake-1.15 is missing in autogen. Please try again. Thanks for the updated patch. Pushed to the gtk-2-24 branch upstream. I'll do a release in a bit. Thank you very much. Another user experienced a similar problem: Just changing the display resolution. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mate-display-properties crash_function: gdk_event_apply_filters executable: /usr/bin/mate-display-properties kernel: 3.18.7-100.fc20.x86_64 package: mate-control-center-1.8.3-1.fc20 reason: mate-display-properties killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 gtk2-2.24.26-1 is in updates-testing, please test and leave karma. https://admin.fedoraproject.org/updates/FEDORA-2015-2371/gtk2-2.24.26-1.fc21?_csrf_token=3ff876e2c65be5f6177b2dbc8e75f51c927ffc72 https://admin.fedoraproject.org/updates/FEDORA-2015-2346/gtk2-2.24.26-1.fc20?_csrf_token=3ff876e2c65be5f6177b2dbc8e75f51c927ffc72 gtk2-2.24.26-1 is in stable, closed. |