+++ This bug was initially created as a clone of Bug #700829 +++ The following error is reported to consoles, if i lock the screen for sometime and this sometimes also cause a hang which need a reboot to solve. Had this issue with F15 and updating it to F16 also does not solve it. Nov 11 12:29:11 rruban kernel: [ 3084.510821] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3] Nov 11 12:29:11 rruban kernel: [ 3084.701413] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3] # uname -a Linux 3.1.0-7.fc16.x86_64 #1 SMP Tue Nov 1 21:10:48 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Regards Ranjith Ruban
What hardware is this with?
Hello Adam, This is a laptop Dell Latitude D630 . [root@rruban etc]# lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) [root@rruban etc]# The second monitor is dell P2210. If you need any further details please get back Thanks Ranjith Ruban
Also i get the below sometimes and have to hard reboot inorder to recover from this. Nov 15 14:22:24 rruban kernel: [12717.268297] [drm:kick_ring] *ERROR* Kicking stuck wait on render ring Nov 15 14:22:26 rruban kernel: [12718.772047] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Nov 15 14:22:26 rruban kernel: [12718.772057] [drm:kick_ring] *ERROR* Kicking stuck wait on render ring Thanks Ranjith Ruban
Hello An additional info is that the above messages on comment #3 and #0 happens only if i have second monitor dell P2210 connected and if i leave the system idel for sometime after locking the screen. Thanks Ranjith Ruban
Closing this one as issue seems resolved with 3.1.2-1.fc16.x86_64. Do not see any patches which are added which fixed it but its resolved. Thanks Ranjith Ruban
Still getting this errors Mar 21 14:48:32 rruban kernel: [ 187.855197] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3] Mar 21 14:48:46 rruban kernel: [ 201.483167] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3] [rruban@rruban ~]$ uname -a Linux rruban.redhat.com 3.1.2-1.fc16.x86_64 #1 SMP Tue Nov 22 09:00:57 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
What about 3.2.10 kernels in updates, or 3.3.0 kernels in updates-testing? 3.1.2 is very old
As far as I can say, this is still an actual bug. I'm getting this error running F17, with kernel 3.6.2-4 and Xorg 1.12.3 (both of them the latest version available as Fedora 17 packages). The problem does have something to do with having two external monitors connected to my Lenovo X230.
c#6,8 re-confirmed on 3.6.7-4 and xorg 1.12.3-2. Same exact symptoms on this Lenovo x230. Fedora boots fine with 1 monitor attached, but if I attach 2 monitors to the docking station, it spits out the error in c#6.
00:02.0 VGA compatible controller: Intel Corporation Device 0166 (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21fa Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 42 Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 5000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 41b1 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915
Created attachment 673963 [details] intel_reg_snapshot > /root/snapshot This is a reg dump of the Intel area
Created attachment 673964 [details] dd if=/dev/mem of=/root/rom bs=64k skip=12 count=1 Should be a dump of the graphics memory area
Created attachment 673965 [details] dmesg >> dmsg dmesg dump after not being able to boot up with both monitors
I'm having the same problem on my Lenovo T430 laptop with Intel HD 4000 graphics card. If I unplug one monitor it will boot to the login screen and I can then plug in the 2nd monitor (unplug meaning the HDMI cable). I can also boot while it's not in the dock and then dock it and it will fire up both monitors and I can continue. # uname -a Linux colossus 3.6.11-1.fc17.x86_64 #1 SMP Mon Dec 17 22:16:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Device 0166 (rev 09) I've attached some files of some diagnostics outputs.
I have the same problem as described above. This is with a Lenovo X230 laptop with the Intel 4000 graphics. The laptop boots just fine as long as no more than 1 external monitor is attached. As a side note, which is probably related when I close the laptop lid and reopen, I lose the gnome-shell. $ uname -a Linux thinker2.localdomain 3.6.11-1.fc17.x86_64 #1 SMP Mon Dec 17 22:16:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux $ lspci -v | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Device 0166 (rev 09) (prog-if 00 [VGA controller]) I've also confirmed this bug exists in F18 beta using a LiveCD.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still persists Lenovo T530 dock station with connected external monitors 00:02.0 VGA compatible controller: Intel Corporation Device 0166 (rev 09) (prog-if 00 [VGA controller]) 3.6.11-1.fc17.x86_64 xorg-x11-drv-intel-2.20.16-1.fc17.x86_64
I am having also having this issue with a Lenovo X230 using a dock and xorg-x11-drv-intel-2.20.16-1.fc17.x86_64 One monitor connected to the dock is fine but when I connect a second I get: [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7] $ uname -a Linux work 3.7.3-101.fc17.x86_64 #1 SMP Fri Jan 18 17:40:57 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ lspci -v | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Device 0166 (rev 09) (prog-if 00 [VGA controller])
Jennifer and others: https://bugs.freedesktop.org/show_bug.cgi?id=58138 NOTABUG
Interesting. However I have a setup which works great with the same hardware as comment #17 when i boot up from a suspended state. If I start from a fresh boot then i also get that issue. (my graphics chip is i7-3520M / Intel® HD Graphics 4000) Monitors are two 24" dell U2410 left and right and center is a Dell U2311H.. The right hand screen is actually using a DisplayLink usb2 adaptor (the bug in this report happens wiht or without that one). So, I have two identical screens and a third similar screen.. are you saying I could run all three wihtout the displaylink dongle?
I have the same very repeatable issue on a Lenovo T530 with F17. Only occurs with docking station and dual monitors. I am fine with single monitor on VGA port. A second, identical monitor plugged into the DVI port with DVI to VGA cable causes the below. BUT any monitor plugged into the DVI port will cause it, doesn't seem tied to the monitor but its always with a DVI to VGA cable. I would try something else (HDMI or DVI native monitor instead of converter cable) but don't have any handy. /var/log/messages-20130120:Jan 17 14:11:43 jgpicker kernel: [ 2.929749] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:7] /var/log/messages-20130120:Jan 17 14:11:43 jgpicker kernel: [ 2.929853] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:7] /var/log/messages-20130120:Jan 17 14:11:43 jgpicker kernel: [ 2.979093] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:7Linux OS: persisted across several revisions, but currently.. 3.7.3-101.fc17.x86_64 #1 SMP Fri Jan 18 17:40:57 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux 00:02.0 VGA compatible controller: Intel Corporation Device 0166 (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21f6 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 42 Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 5000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 41b1 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915
I am seeing this same issue in Fedora 18. I am new to Fedora and Bugzilla so am not sure what the protocol is for reporting issues so please be understanding if I am a little ignorant to procedures. I am running on a Dell Latitude E6430 If undocked I have no issue If docked and no external monitor, no issue If docked and one external monitor, no issue If docked and two external monitors, The machine will not come up. I see a couple "failed to set mode on [CRTC:7]" and "detected unhandled fb_set_par code -22" It does not matter if I am using a VGA and a DVI or 2 DVI cables. I tried it with the laptop open and shut... If I plug in the second monitor while the system is running, It does screws up both displays and I cannot see do anything. I will have to do it again after saving this post for more information I booted to Ubunto 12.10 and was able to get it to work with 2 dvi cables, showing it is not a hardware limitation, at lease in that config. $ uname -a Linux localhost.localdomain 3.8.1-201.fc18.x86_64 #1 SMP Thu Feb 28 19:23:08 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
I also have this issue on a Dell Latitude E6330. Fully up to date as of yesterday.
Sorry, I wasn't done composing and I added myself to the cclist and it added the incomplete message. I'm running up-to-date Fedora 18, fresh install, 3.8.6-203. [root@mo0033802 ~]# uname -a Linux mo0033802.unix.magellanhealth.com 3.8.6-203.fc18.x86_64 #1 SMP Tue Apr 9 19:33:01 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root@mo0033802 ~]# lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) [root@mo0033802 ~]# dmidecode | grep Product Product Name: Latitude E6330 Product Name: 0P1XMK [root@mo0033802 ~]# cat /etc/fedora-release Fedora release 18 (Spherical Cow) [root@mo0033802 ~]# yum check-update Loaded plugins: langpacks, presto, refresh-packagekit [root@mo0033802 ~]# Relevant section from /var/log/messages: Apr 15 09:05:15 mo0033802 kernel: [ 3.975222] [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7] Apr 15 09:05:15 mo0033802 kernel: [ 3.975246] fbcon_init: detected unhandled fb_set_par error, error code -22 Apr 15 09:05:15 mo0033802 kernel: [ 3.975254] Console: switching to colour frame buffer device 170x48 Apr 15 09:05:15 mo0033802 kernel: [ 3.975321] [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7] Apr 15 09:05:15 mo0033802 kernel: [ 3.979883] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device Apr 15 09:05:15 mo0033802 kernel: [ 3.979885] i915 0000:00:02.0: registered panic notifier Apr 15 09:05:15 mo0033802 kernel: [ 3.979964] i915: No ACPI video bus found Apr 15 09:05:15 mo0033802 kernel: [ 4.105278] acpi device:4c: registered as cooling_device4 Apr 15 09:05:15 mo0033802 kernel: [ 4.138122] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) Apr 15 09:05:15 mo0033802 kernel: [ 4.138234] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10 Apr 15 09:05:15 mo0033802 kernel: [ 4.138490] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 Apr 15 09:05:15 mo0033802 kernel: [ 4.138764] [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7] Apr 15 09:05:15 mo0033802 kernel: [ 4.139857] [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7]
Adding a "me too" for this, with kernel 3.9.6-200.fc18.x86_64 $sudo dmidecode | grep Product Product Name: Latitude E5530 non-vPro Product Name: 05GRXT Can confirm that booting with laptop undocked and then docking works around the issue; booting with laptop docked with two external monitors (VGA and DVI), results in the error. Relevant logs section: Jun 27 11:22:40 localhost kernel: [ 4.568166] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). Jun 27 11:22:40 localhost kernel: [ 4.568167] [drm] Driver supports precise vblank timestamp query. Jun 27 11:22:40 localhost kernel: [ 4.568226] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Jun 27 11:22:40 localhost kernel: [ 4.693121] fbcon: inteldrmfb (fb0) is primary device Jun 27 11:22:40 localhost kernel: [ 5.074520] [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7], err = -22 Jun 27 11:22:40 localhost kernel: [ 5.074536] fbcon_init: detected unhandled fb_set_par error, error code -22 Jun 27 11:22:40 localhost kernel: [ 5.074540] Console: switching to colour frame buffer device 240x67 Jun 27 11:22:40 localhost kernel: [ 5.074573] [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7], err = -22 Jun 27 11:22:40 localhost kernel: [ 5.079235] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device Jun 27 11:22:40 localhost kernel: [ 5.079235] i915 0000:00:02.0: registered panic notifier Jun 27 11:22:40 localhost kernel: [ 5.079250] i915: No ACPI video bus found Jun 27 11:22:40 localhost kernel: [ 5.185482] acpi device:4c: registered as cooling_device4 Jun 27 11:22:40 localhost kernel: [ 5.218406] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) Jun 27 11:22:40 localhost kernel: [ 5.218465] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10 Jun 27 11:22:40 localhost kernel: [ 5.218612] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 Jun 27 11:22:40 localhost kernel: [ 5.218723] [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7], err = -22 Jun 27 11:22:40 localhost kernel: [ 5.218905] [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7], err = -22 Jun 27 11:22:40 localhost kernel: [ 5.658424] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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.
will this bug still be fixed? I would give some usefull reports if needed, since i get this message on Fedora 19, too. [drm: intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7], err = -22 This happens as described here: https://bugzilla.redhat.com/show_bug.cgi?id=753050#c25 > Jul 9 09:38:55 london kernel: [ 3.080270] acpi device:40: registered as cooling_device9 > Jul 9 09:38:55 london kernel: [ 3.080390] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) > Jul 9 09:38:55 london kernel: [ 3.080421] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:02/input/input7 > Jul 9 09:38:55 london kernel: [ 3.080480] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 > Jul 9 09:38:55 london kernel: [ 3.080706] [drm] initializing kernel modesetting (TURKS 0x1002:0x6840 0x1028:0x056E). > Jul 9 09:38:55 london kernel: [ 3.080748] [drm] register mmio base: 0xC2000000 > Jul 9 09:38:55 london kernel: [ 3.080750] [drm] register mmio size: 131072 > Jul 9 09:38:55 london kernel: [ 3.080752] vga_switcheroo: enabled > Jul 9 09:38:55 london kernel: [ 3.073292] [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7], err = -22 > Jul 9 09:38:55 london kernel: [ 3.073304] fbcon_init: detected unhandled fb_set_par error, error code -22 > Jul 9 09:38:55 london kernel: [ 3.073308] Console: switching to colour frame buffer device 240x67 > Jul 9 09:38:55 london kernel: [ 3.073344] [drm:intel_crtc_set_config] *ERROR* failed to set mode on [CRTC:7], err = -22 > Jul 9 09:38:55 london kernel: [ 3.078505] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device > Jul 9 09:38:55 london kernel: [ 3.078506] i915 0000:00:02.0: registered panic notifier > Jul 9 09:38:55 london kernel: [ 3.078731] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS > Jul 9 09:38:55 london kernel: [ 3.079464] acpi device:31: registered as cooling_device8 > Jul 9 09:38:55 london kernel: [ 3.079578] ACPI: Video Device [PEGP] (multi-head: yes rom: no post: no) > Jul 9 09:38:55 london kernel: [ 3.079615] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2f/LNXVIDEO:00/input/input6 > Jul 9 09:38:55 london kernel: [ 3.079680] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. Currently it seems that when people have 2 graphics card the firmware will say that there is a bug, but it isn't a bug. Btw. everything still works, it just couldn't print out anything on the second monitor on a laptop before the system is in stage3 and logged into the desktop.
Btw. Hardware is a Dell Vostro 3560 with 2 graphics card, one is Intel HD4000 the other is a Ati Radeon HD7970, but is currently disabled with rc.local and vgaswitchero. But it wouldn't change anything. But still the hardware supports useing HDMI and VGA in FullHD. Even my HD7970 would do the job but it would print the same error when i would enable it. Definitly a bug or maybe just a dumb error since everything works, it just prints out the set mode error and after i logged in everything works without any? problems.
Created attachment 791192 [details] dmesg output
Created attachment 791195 [details] tail of /var/log/messages Got this with a fresh installation of F19 followed by updates and installation of other software. When I powered down, the machine hang with the blue Fedora logo on the screen. CTRL-ALT-Fn showed messages like: "15806.695.....] [drm: drm_crtc_helper_set_config] ERROR failed to set mode on [RTC:10]" with different timestamps. I could not find the same timestamp in the files under /var/log, but the error messages are in /var/log/messages, and the dmesg output I generated.
I have the same problem here, a lenovo x230 with two external displays connected. Even if I turn one of with xrandr before I reboot, all I get is "fbcon_init: detected unhandled fb_set_par error, error code -22". Let me know if you want me to collect any data for you.
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.
This seems to work fine on Fedora 20.