Hide Forgot
Description of problem: 1. Log into MATE 2. Open 'Control Center' 3. Attempt to open 'Monitors' - it crashes I think this one's reproducible. Version-Release number of selected component: mate-control-center-1.6.1-3.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: mate-display-properties crash_function: mate_rr_config_new_current executable: /usr/bin/mate-display-properties kernel: 3.11.9-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Dec 1 21:51:05 AlgoCompSynth abrt-hook-ccpp[2048]: Saved core dump of pid 2046 (/usr/bin/mate-display-properties) to /var/tmp/abrt/ccpp-2013-12-01-21:51:05-2046 (11485184 bytes) Truncated backtrace: Thread no. 1 (3 frames) #4 mate_rr_config_new_current at mate-rr-config.c:607 #5 on_screen_changed at xrandr-capplet.c:138 #6 run_application at xrandr-capplet.c:2515
Created attachment 831436 [details] File: backtrace
Created attachment 831437 [details] File: cgroup
Created attachment 831438 [details] File: core_backtrace
Created attachment 831439 [details] File: dso_list
Created attachment 831440 [details] File: environ
Created attachment 831441 [details] File: limits
Created attachment 831442 [details] File: maps
Created attachment 831443 [details] File: open_fds
Created attachment 831444 [details] File: proc_pid_status
Does display settings crash during opening the application or did it crashed if you try to set the display size of your monitor?
Step one: open mate-control-center Step two: press the 'Monitors' button in hardware It crashes but mate-control-center stays open. Repeated presses cause repeated crashes.
OK, do you use the closed source fglrx ati driver?
(In reply to Wolfgang Ulbrich from comment #12) > OK, > do you use the closed source fglrx ati driver? No ... the system is using Fedora. I haven't been able to get the closed-source drivers to work and gave up on them.
I can't reproduce the problem with MATE on F20 and a Radeon 5770 video card. Please tell us more about your configuration. How many monitors? How are they connected? What model ATI video card do you have?
(In reply to Dan Mashal from comment #14) > I can't reproduce the problem with MATE on F20 and a Radeon 5770 video card. > > Please tell us more about your configuration. How many monitors? How are > they connected? What model ATI video card do you have? Funny you should mention F20. It's a new machine and I initially wanted to run F20 but had some dependency issues in the packages - I load a lot of stuff on it. So I dropped back to F19. I found a workaround for F20 and the machine is now on F20. Here's the F20 lspci - I'll attach an Xorg.0.log as well: 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) (rev 02) 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD/ATI] RD990 I/O Memory Management Unit (IOMMU) 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40) 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42) 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40) 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) 00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon HD 7790/8770] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 0002 02:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Created attachment 833295 [details] Xorg.0.log
Created attachment 833297 [details] xorg.conf
The symptoms are different on F20, however. All of the common desktops work fine *except* MATE! When I log into MATE, the screen tears and ripples to a nearly unusuable state. I haven't tried to troubleshoot it or find a workaround. I'm going to run through all the other ABRT bugs and close them as Unable to Reproduce.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.