dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80050] New: [855GM] Incorrect drop shadow color under windows in Cinnamon persists with MESA 10.1.
Date: Sun, 15 Jun 2014 14:48:04 +0000	[thread overview]
Message-ID: <bug-80050-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 80050
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [855GM] Incorrect drop shadow color under windows in
                    Cinnamon persists with MESA 10.1.
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: rkmugen.linux@gmail.com
          Hardware: x86 (IA32)
            Status: NEW
           Version: 10.1
         Component: Drivers/DRI/i830
           Product: Mesa

I wasn't sure if I should've just edited my previous bug post #72819 since the
problem persists with a newer version of MESA.  But as the subject heading
reads, that's exactly what happens.

I was testing Linux Mint 17 Cinnamon edition with the same video hardware
(Intel 82852/855GM) and I noticed some things compared to the previous Linux
Mint 16 Cinnamon edition:

1)  In Cinnamon for Linux Mint 16, the background color for all drop-down menus
wasn't visible, making it very difficult to read the text for each menu item. 
In Cinnamon for Linux Mint 17, the bug appears to be fixed; the background
color is now visible.

2)  However, for Cinnamon under Linux Mint 16 and 17, regardless of what
alternate appearance theme I tried to apply, the windows always show the
incorrect dropshadow color (white) instead of black.

The terminal outputs for glxinfo (when I'm testing under Linux Mint 17) show
that I am indeed running MESA 10.1 and that I do have direct rendering enabled.

While I have absolutely NO idea what's causing this or what packages are
responsible for whatever else, the following list are of packages that I'm
currently using, that I think have something to do with this bug, and their
current version numbers:
*libdrm-intel1 v2.4.52-1
*xserver-xorg-video-intel v2:2.99.910-0ubuntu1
*libgl1-mesa-dri v10.1.0.4.ubuntu5
*libgl1-mesa-glx v10.1.0.4.ubuntu5
*libglapi-mesa v10.1.0.4.ubuntu5
*libglu1-mesa v9.0.0-2
*linux-kernel-generic v3.13.0-24
*linux-firmware v1.127

Please note that I'm experiencing this bug on Linux Mint 17 Cinnamon Edition
with the Intel 82852/855GM chipset.

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

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

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-06-15 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-15 14:48 bugzilla-daemon [this message]
2014-06-15 14:50 ` [Bug 80050] [855GM] Incorrect drop shadow color under windows in Cinnamon persists with MESA 10.1 bugzilla-daemon
2014-12-19 23:25 ` bugzilla-daemon
2015-04-10 16:15 ` bugzilla-daemon

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-80050-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox