Description of problem: The firefox screen will occasionally get corrupted Version-Release number of selected component (if applicable): Doesn't really matter. Has happened on all Firfoxes since upgrade to Mageia 5 How reproducible: Occasional Steps to Reproduce: 1.Just browse around for some time and boom Display controller: Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Screenshot of corruption attached. The corruption of the buttons is fixed for some time when they are redrawn ie. by moving mouse over them. Reproducible: Steps to Reproduce:
Created attachment 7045 [details] Screenshot of corrupted display This is what it looks like.
Component: Release (media or process) => RPM PackagesSource RPM: (none) => firefox
I don't know what packagers would be at fault, maybe drivers. Adding knowledgeable packagers in CC in case they can help identifying the issue. Does it happen only in firefox? With or without the flash plugin? If with, does it happen without it too?
CC: sysadmin-bugs => anssi.hannula, thierry.vignaud, tmb
Only happens in Firefox. - Tried with Flash disabled - Doesn't seem to make a difference - Also tried with HW-acceleration off - Still happens
Please, have a look here: https://bugs.mageia.org/show_bug.cgi?id=16986 If it helps, this bug report can be closed.
CC: (none) => yullaw
Now tested. Did not make a difference.
Please, can you send outputs from?: $ cat /etc/issue $ urpmq --list-media active --list-url $ lspcidrake -v | grep VGA $ cat /etc/X11/xorg.conf
Here we go: % cat /etc/issue Mageia release 5 (Official) for x86_64 Kernel 4.1.8-desktop-1.mga5 on a Dual-processor x86_64 / \l % urpmq --list-media active --list-url Core Release http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/core/release Core Release Debug http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/debug/core/release Core Updates http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/core/updates Core Updates Debug http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/debug/core/updates Core Updates Testing Debug http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/debug/core/updates_testing Nonfree Release http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/nonfree/release Nonfree Release Debug http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/debug/nonfree/release Nonfree Updates http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/nonfree/updates Nonfree Updates Debug http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/debug/nonfree/updates Tainted Release http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/tainted/release Tainted Release Debug http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/debug/tainted/release Tainted Updates http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/tainted/updates Tainted Updates Debug http://ftp.acc.umu.se/mirror/mageia/distrib/5/x86_64/media/debug/tainted/updates Core 32bit Release http://ftp.acc.umu.se/mirror/mageia/distrib/5/i586/media/core/release Core 32bit Updates http://ftp.acc.umu.se/mirror/mageia/distrib/5/i586/media/core/updates Nonfree 32bit Release http://ftp.acc.umu.se/mirror/mageia/distrib/5/i586/media/nonfree/release Nonfree 32bit Updates http://ftp.acc.umu.se/mirror/mageia/distrib/5/i586/media/nonfree/updates Tainted 32bit Release http://ftp.acc.umu.se/mirror/mageia/distrib/5/i586/media/tainted/release Tainted 32bit Updates http://ftp.acc.umu.se/mirror/mageia/distrib/5/i586/media/tainted/updates lspcidrake -v | grep VGA Card:Intel 810 and later: Intel Corporation|Mobile 4 Series Chipset Integrated Graphics Controller [DISPLAY_VGA] (vendor:8086 device:2a42 subv:10cf subd:1451) (rev: 07) % cat /etc/X11/xorg.conf # File generated by XFdrake (rev 262502) # ********************************************************************** # Refer to the xorg.conf man page for details about the format of # this file. # ********************************************************************** Section "ServerFlags" AllowMouseOpenFail # allows the server to start up even if the mouse does not work #DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching) Option "DontZap" "False" # disable <Ctrl><Alt><BS> (server abort) EndSection Section "Module" Load "v4l" # Video for Linux EndSection Section "Monitor" Identifier "monitor1" VendorName "Plug'n Play" # TV fullscreen mode or DVD fullscreen output. # 768x576 @ 79 Hz, 50 kHz hsync ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 # 768x576 @ 100 Hz, 61.6 kHz hsync ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 EndSection Section "Device" Identifier "device1" VendorName "Intel Corporation" BoardName "Intel 810 and later" Driver "intel" Option "AccelMethod" "uxa" Option "DPMS" EndSection Section "Screen" Identifier "screen1" Device "device1" Monitor "monitor1" EndSection Section "ServerLayout" Identifier "layout1" Screen "screen1" EndSection
Your system seems to be broken in case you have incorrect set sources, see *Debug, which are not for normal users. See: https://wiki.mageia.org/en/Install_media_in_Mageia_2_for_beginners The system reinstallation should be neccessary. Save your data from /home partition first. Use medium Mageia 5 64bit DVD and after BIOS and DVD loading, choose Update â go to Custom disk partitioning â select root "/" and "/home" partitions â choose format disk "/" only! â do installation. Your /home will not be touched and you keep all datas. After well done fresh installation you have to add official repositories, update them and then install recomended software again. Let us know, please.
Well. I am not exactly the "normal" user. :-) The debug repositories are turned on because I needed to debug and fix autofs. There is nothing broken in that... Cannot see how enabling debug-information about packages would affect the bug. Can you give me a clue? And I will not re-install as there is far too much to reconfigure outside the home directory.. Please give me an indication on where to look in that case instead.
I too see this problem which is also described in 9410. Sorry to but in rather than raise a new bug report but I see the following in dmesg when the problem occurs: [ 769.997028] [drm] stuck on render ring [ 769.999070] [drm] GPU HANG: ecode 3:0:0x7efaffcf, in X [1107], reason: Ring hung, action: reset [ 769.999075] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 769.999078] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 769.999080] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 769.999082] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 769.999085] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 770.021930] drm/i915: Resetting chip after gpu hang [ 1235.997041] [drm] stuck on render ring [ 1235.998914] [drm] GPU HANG: ecode 3:0:0x3fb3330c, in X [1107], reason: Ring hung, action: reset [ 1235.999086] drm/i915: Resetting chip after gpu hang [ 1788.000049] [drm] stuck on render ring [ 1788.001943] [drm] GPU HANG: ecode 3:0:0x3cffffc1, in X [1107], reason: Ring hung, action: reset [ 1788.022363] drm/i915: Resetting chip after gpu hang [10739.997026] [drm] stuck on render ring [10739.998971] [drm] GPU HANG: ecode 3:0:0x0d7fffc1, in X [6101], reason: Ring hung, action: reset [10740.025764] drm/i915: Resetting chip after gpu hang [10770.000062] [drm] stuck on render ring [10770.002173] [drm] GPU HANG: ecode 3:0:0x16dfffc1, in X [6101], reason: Ring hung, action: reset [10770.023229] drm/i915: Resetting chip after gpu hang [11701.001779] [drm] GPU HANG: ecode 3:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue [11703.001793] [drm] GPU HANG: ecode 3:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue [11705.001802] [drm] GPU HANG: ecode 3:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue [11707.001800] [drm] GPU HANG: ecode 3:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue [11709.001810] [drm] GPU HANG: ecode 3:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue [11710.998771] [drm] GPU HANG: ecode 3:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue [11712.998767] [drm] GPU HANG: ecode 3:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue [11712.998825] [drm] no progress on render ring [11713.000766] [drm] GPU HANG: ecode 3:-1:0x00000000, reason: Ring hung, action: reset [11713.029819] drm/i915: Resetting chip after gpu hang [14934.000062] [drm] stuck on render ring [14934.002055] [drm] GPU HANG: ecode 3:0:0xfc981a23, in X [6101], reason: Ring hung, action: reset [14934.025084] drm/i915: Resetting chip after gpu hang [15031.000047] [drm] stuck on render ring [15031.001909] [drm] GPU HANG: ecode 3:0:0x16dfffc1, in X [6101], reason: Ring hung, action: reset [15031.033737] drm/i915: Resetting chip after gpu hang [15054.735437] sdf: detected capacity change from 512483328 to 0 [15058.371318] usb 1-5: USB disconnect, device number 7 [15071.000039] [drm] stuck on render ring [15071.002118] [drm] GPU HANG: ecode 3:0:0x0a0fffc1, in X [6101], reason: Ring hung, action: reset [15071.033218] drm/i915: Resetting chip after gpu hang [15170.000059] [drm] stuck on render ring [15170.002090] [drm] GPU HANG: ecode 3:0:0x0d7fffc1, in X [6101], reason: Ring hung, action: reset [15170.023076] drm/i915: Resetting chip after gpu hang [15224.997031] [drm] stuck on render ring [15224.999136] [drm] GPU HANG: ecode 3:0:0x0e3fffc1, in X [6101], reason: Ring hung, action: reset [15225.031297] drm/i915: Resetting chip after gpu hang [15276.997024] [drm] stuck on render ring [15276.999115] [drm] GPU HANG: ecode 3:0:0x7efeffc2, in X [6101], reason: Ring hung, action: reset [15277.027058] drm/i915: Resetting chip after gpu hang [15581.000054] [drm] stuck on render ring [15581.001966] [drm] GPU HANG: ecode 3:0:0x16ffbfc1, in X [6101], reason: Ring hung, action: reset [15581.027009] drm/i915: Resetting chip after gpu hang [15610.997027] [drm] stuck on render ring [15610.998950] [drm] GPU HANG: ecode 3:0:0x16ffbfc1, in X [6101], reason: Ring hung, action: reset [15611.024885] drm/i915: Resetting chip after gpu hang My system details. cat /etc/issue Mageia release 5 (Official) for i586 Kernel 4.1.15-desktop-2.mga5 on a Dual-processor i686 / \l urpmq --list-media active --list-url Core Release rsync://mirror.easthsia.com/mageia/distrib/5/i586/media/core/release Core Updates rsync://mirror.easthsia.com/mageia/distrib/5/i586/media/core/updates Nonfree Release rsync://mirror.easthsia.com/mageia/distrib/5/i586/media/nonfree/release Nonfree Updates rsync://mirror.easthsia.com/mageia/distrib/5/i586/media/nonfree/updates Tainted Release rsync://mirror.easthsia.com/mageia/distrib/5/i586/media/tainted/release Tainted Updates rsync://mirror.easthsia.com/mageia/distrib/5/i586/media/tainted/updates lspcidrake -v | grep VGA Card:Intel 810 and later: Intel Corporation|82915G/GV/910GL Integrated Graphics Controller [DISPLAY_VGA] (vendor:8086 device:2582 subv:103c subd:2a08) (rev: 04) cat /etc/X11/xorg.conf # File generated by XFdrake (rev 262502) # ********************************************************************** # Refer to the xorg.conf man page for details about the format of # this file. # ********************************************************************** Section "ServerFlags" Option "DontZap" "False" # disable <Ctrl><Alt><BS> (server abort) AllowMouseOpenFail # allows the server to start up even if the mouse does not work #DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching) EndSection Section "Module" Load "v4l" # Video for Linux EndSection Section "Monitor" Identifier "monitor1" VendorName "Plug'n Play" ModelName "HP f1905e" HorizSync 30-83 VertRefresh 50-76 # TV fullscreen mode or DVD fullscreen output. # 768x576 @ 79 Hz, 50 kHz hsync ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 # 768x576 @ 100 Hz, 61.6 kHz hsync ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 EndSection Section "Device" Identifier "device1" VendorName "Intel Corporation" BoardName "Intel 810 and later" Driver "intel" Option "DPMS" EndSection Section "Screen" Identifier "screen1" Device "device1" Monitor "monitor1" EndSection Section "ServerLayout" Identifier "layout1" Screen "screen1" EndSection
CC: (none) => phil
@ Dag Nygren Is this bug still valid for you? If so: which Display Manager and which Desktop Environment do you use? Is it also valid with a different DM and DE?
Keywords: (none) => NEEDINFOCC: (none) => marja11
No. Hasn't happened for a long time now. So long that I cannot remember when the problem disappeared. But you can close the report as not valid any more.
(In reply to Dag Nygren from comment #12) > No. Hasn't happened for a long time now. So long that I cannot remember when > the problem disappeared. But you can close the report as not valid any more. Thanks for the feedback, closing as fixed :-) @ Phil, If you still see the problem, then it must have a different cause, so it should then go into a separate bug report (If you're sure it's bug 9410, you could reopen that report and set it to the Mageia version you have. A new report, with fresh information, is preferred, though!)
Status: NEW => RESOLVEDResolution: (none) => FIXED