All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 90932] New: gm105 font glitches with kernel 4.1rc
Date: Thu, 11 Jun 2015 07:02:26 +0000	[thread overview]
Message-ID: <bug-90932-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1097 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=90932

            Bug ID: 90932
           Summary: gm105 font glitches with kernel 4.1rc
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: marcus.moeller-OI3hZJvNYWs@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 116429
  --> https://bugs.freedesktop.org/attachment.cgi?id=116429&action=edit
font glitches with gm105

I have tried Kernel 4.1 with gm105 (NVidia K620 graphics card) and noticed some
font glitches. Some characters are not displayed at all. Sometimes those chars
appear while hovering them with the mouse, sometimes not. I have attached a
screenshot of Firefox. Please note that the word Firefox is sometimes displayed
as 'Fire  x'

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2449 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2015-06-11  7:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  7:02 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-90932-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-06-11 10:33   ` [Bug 90932] gm105 font glitches with kernel 4.1rc bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-13 16:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-18 12:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-22 11:22   ` [Bug 90932] gm107 " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-22 11:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-23 11:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-23 11:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-23 13:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-23 13:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-23 13:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-23 14:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-23 14:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-24  6:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-24 15:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-26 13:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-29  3:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-29  3:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-29  8:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-29 19:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-30  8:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-01 11:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-01 12:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-01 12:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-15  7:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-22 15:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-15 16:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-02 14:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-90932-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.