Any help would be greatly appreciated. I did not have this issue in 12.3 with the same laptop (or SLED 11 SP3 for that matter). Also, all of the menus work fine if I have an application like Firefox running. Thanks!
For fun I went ahead and installed KDE just to make sure I wasn’t losing my mind and it wasn’t something easy with the hardware and KDE works flawlessly. No redraw issues at all.
Just thought I’d chime in with some more information.
Hi
Is the GPU an Intel device, can you post the details from;
hwinfo --gfxcard
What you are seeing has been seen in VM since the driver isn’t that good. GNOME also uses the GPU more than KDE does and is more likely to expose issues.
Not seeing errors in the /var/log/Xorg.0.log or ~/.xsession-errors?
Hi
Thanks, you could upload the full log and xsession-errors to SUSE Paste and set expire to never and post back the URL’s please. One of the openSUSE GNOME Maintainers is keeping an eye on the thread…
Another “layer” to this is that if I have a program in the “background” (I.E. Firefox running), then things work well as long as they are “layered” on top of that Firefox window. The strange stuff happens when there is no fullscreen window on the bottom of the “stack”.
69.346] (II) LoadModule: "modesetting"
69.346] (WW) Warning, couldn't open module modesetting
69.346] (II) UnloadModule: "modesetting"
69.346] (II) Unloading modesetting
69.347] (EE) Failed to load module "modesetting" (module does not exist, 0)
A (EE) error is usually bad news, and can be seriously bad news. Don’t recall seeing this error before. That module failed to load.
I use the intel driver (i915) on a lenovo ThinkPad at the same resolution 1366x768. Checked my Xorg.0.log, but its on Tumbleweed (12.3) KDE and it looks like this at the same point in log:
33.086] (II) LoadModule: "modesetting"
33.087] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
33.088] (II) Module modesetting: vendor="X.Org Foundation"
33.088] compiled for 1.13.2, module version = 0.8.0
33.088] Module class: X.Org Video Driver
33.088] ABI class: X.Org Video Driver, version 13.1
My intel driver is 13.1, yours is newer at 14.1; X.Org X Server 1.13.2, yours X.Org X Server 1.14.3; and my kernel-desktop-3.11.4-31.1, yours slightly older at “3.11.3-1-desktop”.
You might just check your install version with KDE to see if you have the error in Xorg.0.log or not.
Looks like the same modsetting module isn’t getting loaded in KDE, but I’m imagining that the graphical needs of KDE are more forgiving than GNOME and so maybe it isn’t showing up in KDE like it is in GNOME?
I could, of course, be insane, but that is what I am seeing here. I’ll try installing openSUSE 12.3 to see if I see the same thing with this laptop and report back … again!
No such errors in 12.3 GNOME installation with modesetting. Everything looks like it is working correctly. Also, no xsession-errors either on the machine.
“modesetting” is a graphics driver just like intel or radeon. In fact it is a generic driver like vesa, but with support for KMS.
You don’t need it as you are using the intel driver anyway, but X’s auto-configuration tries to load more than one driver and then chooses to use the best one of those that can be loaded successfully.
On your system it can’t be loaded, that’s why you get this error message. Maybe you don’t have xf86-video-modesetting installed?
I have no idea about your problem, though, but it sure sounds like a graphics driver issue.
Does the problem persist when you add “nomodeset” to the boot options, or boot to “recovery mode” (“Advanced Options” in the boot menu)?
Good check. I ggogled the error message, and a few other distro users had it and sometimes coupled with the other two driver alternatives vesa and fbdev, coincidentally nearly all Gnome 3 users and their Gnome display problems mysteriously sorted themselves. So most of those reports were pretty useless :. There were other desktops involved as well(IIRC), xfce and openbox. Hence the need to check KDE, as I didn’t see it amongst those other reports and it appeared problem free.
In all probability you don’t need that alternative driver, but it’s still unhelpful and misleading for users when X tries to load drivers that are not available and throws (EE) errors.
You could try Gnome with another desktop if available e.g. Mate, but I’m guessing?
I don’t care how, upstream or downstream that’s a problem for the devs to solve. Why is the driver not there if it’s required to be automatically configured? If not required, a warning should be sufficient or the program code should be fixed. It’s obviously not an issue for the previous release of openSUSE or X.
