GNOME 3.10 - Desktop artifacts (1 screen)

jasonwryan · 2013-10-11 19:37:24

Merging with the exisiting thread

s0lid7 · 2013-10-12 20:47:54

I can't even get to login screen with gdm. I installed slim and login screen appears but does not accept password. Then i installed lxdm but it couldn't boot either. I had to install lxde also and from it i'm writing now. I was reading somewhere that it is a known issue and there is already a 3.10-1 version that solves it. I also got a strange message about language when i logged in to lxde.

Solutions "pacman -S gnome" and "alt+f2 r" does not resolve the problem for me

Last edited by s0lid7 (2013-10-12 20:48:34)

David Batson · 2013-10-13 11:18:52

Possibly this helps?

https://bugzilla.gnome.org/show_bug.cgi?id=657071

Try putting the following in /etc/environment

CLUTTER_PAINT=disable-clipped-redraws:disable-culling

s0lid7 · 2013-10-13 12:04:41

Before i see your post i tried disabling all ISO languages from locale and i now have only en_US.UTF-8 enabled. That has as a result that i'm now able to see gdm's login screen. So, gdm seems to be working now. But it still can't login in gnome but only in lxde. When i try to login in gnome i either get a message saying "oops something went wrong etc..." or "all extensions has been disabled please logout etc..."

I also tried your suggestion but i'm still in lxde... I'll take a further look at the link you provided.

--edit--

By putting that CLUTTER_PAINT=disable-clipped-redraws:disable-culling gnome-shell --replace i can login but i only see conky (with bad font config) and black wallpaper instead of default and after 2-3 seconds i get the message "something went wrong. all extensions have been disabled as a precaution". I also tried to disable all extensions and even remove them manually from ./local/share/gnome-shell/extensions/ but with no result

--edit 2--

By reading this https://bugzilla.gnome.org/show_bug.cgi?id=709313 i opened as root nvidia-settings and manually choose native resolution of screen (it was auto) and then saved it in xorg configuration file. Before that gnome-control-center couldn't even recognise my screen... Now everything seems to be fine except bad italic(!) fonts in conky. I'll test it further and try to re-enable some extensions and set proper fonts in conky.

Last edited by s0lid7 (2013-10-13 13:26:17)

ItachiSan · 2013-10-13 17:21:10

Seems they're working on it.

https://git.gnome.org/browse/gnome-shel … 574942d971

Will see if it's fixed in next builds.

s0lid7 · 2013-10-13 20:09:51

For now everything seems to work fine except the weird problem with italic fonts in conky which also causes bad font rendering in mplayer and gnome player too (it uses different fonts from line to line!!). Since i'm not sure that this is related i'll say that for me problem is solved after settings screen resolution manually in nvidia-settings and save configuration in xorg. I'll keep an eye here i case something new appears.

gertjanzwartjes · 2013-10-21 09:25:26

I also had this problem with my primary screen showing no background, flickering and drawing artefacts of windows. I have a Lenovo T420, with two monitors connected through DVI and DisplayPort.

I tried all workarounds in this thread to no avail. Restarting didn't help at all. So I switched to nouveau instead to see if that helped. It did. However, I tried to re-arrange my monitors in the Displays settings app, but that crashed the whole X session. I was sick of re-arranging my displays anyway, so I decided to simply switch the monitor cables, so the default display arrangement would be as I want them. So all fine, except the laggy performance of the nouveau driver.

That made me try to switch to nVidia drivers once more, I had just a little hope left that maybe by switching monitor cables the 'problem' screen would be on my secondary display (without menu bar) and who knows maybe the restart workaround would work in that case. I re-installed the nvidia driver and against all odds the problem was still fixed!

It's a strange workaround, but hey, it works for me as well as a colleague/friend who has the same setup, so I just thought to post it here maybe it'll help someone else too.

crashandburn4 · 2013-10-23 16:43:49

had this and luckily a pacman -S gnome worked for me (didn't think it would as there were no flags the first time) none of the other solutions worked for me though.

siamer · 2013-10-23 17:38:34

I got same problem but my gnome I installed by single packages from repo (mean gnome-shell, gnome-session, libsoup etc.) not by "gnome" metapackage. After installing "gnome" metapackage problem is solved for me... maybe you should try this ? other solution for me was autologin at boot with gdm than I didn't see that artifacts when using "startx" was seeing them again...

Good luck
siamer

jdc2172 · 2013-10-23 18:42:54

My gnome 3.10 shell still requires a restart on login. Are the gnome devs still fixing this?

ps. I hate how every gnome release breaks my setup, even though I'm using just the default gnome installation - is this even tested before release?

tandycorp · 2013-10-24 00:05:00

I changed theme and it worked. All artifacts suddently stopped. But I don't like standart theme so I'm reinstalling gnome like others suggested.

siamer · 2013-10-25 18:14:59

if you are using intel card another solution is make a file /etc/X11/xorg.conf.d/20-intel.conf

and pas that

Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "AccelMethod"  "uxa"
EndSection

intel is using 2 differnt drivers

more info on wiki

Regards,
siamer

bulletmark · 2013-10-25 22:49:55

tandycorp wrote:

But I don't like standart theme so I'm reinstalling gnome like others suggested.

I don't see how reinstalling gnome will fix this? I am new to arch and just clean installed it to my intel graphics HD 4000 PC but I get this problem. I also clean installed arch as a guest in Virtualbox and I see the same problem, running on a Ubuntu 13.10 VB host, and also on a Mac OS X Mavericks VB host. So it just seems a universal bug currently in GNOME 3/shell? Restarting the shell does seem to clear the bug though.

mtfk · 2013-10-26 22:46:41

I had the same problem, after pacman -Syu gnome starts behave really weird, and in my case:

pacman -S gnome-shell-extensions

solved the problem.

Last edited by mtfk (2013-10-26 22:47:01)

bulletmark · 2013-10-26 23:10:14

Yes mtfk, installing gnome-shell-extensions does solve the problem.

However, as the other threads and bugs about this issue now say, a possibly easier and better solution is just to create the directory:

/usr/share/gnome-shell/modes

This will stop the bug until they fix it upstream. Some of us do not not want to install gnome-shell-extensions because they all get added to the installed list on extensions.gnome.org.

Arch Linux

#26 2013-10-11 19:37:24

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#27 2013-10-12 20:47:54

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#28 2013-10-13 11:18:52

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#29 2013-10-13 12:04:41

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#30 2013-10-13 17:21:10

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#31 2013-10-13 20:09:51

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#32 2013-10-21 09:25:26

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#33 2013-10-23 16:43:49

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#34 2013-10-23 17:38:34

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#35 2013-10-23 18:42:54

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#36 2013-10-24 00:05:00

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#37 2013-10-25 18:14:59

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#38 2013-10-25 22:49:55

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#39 2013-10-26 22:46:41

Re: GNOME 3.10 - Desktop artifacts (1 screen)

#40 2013-10-26 23:10:14

Re: GNOME 3.10 - Desktop artifacts (1 screen)

Board footer