public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [~and64] Headsup for google-chrome users
Date: Fri, 22 May 2015 06:28:16 -0700	[thread overview]
Message-ID: <mjnath$pgk$1@ger.gmane.org> (raw)
In-Reply-To: <871ti8kjeo.fsf@gmail.com>

On 05/22/2015 03:15 AM, Quanyang Liu wrote:
> On Thu, May 21 2015 at 20:55:52 +0800, walt wrote:
>> I just wasted some time figuring out this mess:
>>
>> ......
>>
>> So, re-install ati-drivers, reboot, etc, all of which will make you late
>> for work, like I am now :p
> 
> Hi all, but I just found another problem.
> 
> I now use xmonad, and always shift chrome to 7th workspace. And for the
> new version chrome, it has no focus after being shifted. I can type in
> the start page (if I set it to some website,
> i.e. https://www.google.com ), but can't type in the address bar (if
> there is no start page). And the title bar is always gray until I click
> the browser.
 
I'd suggest posting this question in a new thread because you are describing
a different problem from the one I had.  More people will see your question
that way.





  reply	other threads:[~2015-05-22 13:28 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 12:55 [gentoo-user] [~and64] Headsup for google-chrome users walt
2015-05-21 13:03 ` Alan McKinnon
2015-05-21 14:05 ` Mike Gilbert
2015-05-26  1:27   ` [gentoo-user] " Nikos Chantziaras
2015-05-21 14:57 ` [gentoo-user] " Dale
2015-05-21 15:29   ` Alec Ten Harmsel
2015-05-21 18:29   ` Neil Bothwick
2015-05-21 19:44 ` wabenbau
2015-05-21 20:45   ` Mike Gilbert
2015-05-21 23:49     ` Dale
2015-05-22  7:36       ` Mick
2015-05-22  7:53         ` Dale
2015-05-22  8:38           ` Neil Bothwick
2015-05-22  9:01             ` Dale
2015-05-22  9:19             ` Alan McKinnon
2015-05-22 12:54               ` gottlieb
2015-05-22 14:29               ` Daniel Frey
2015-05-22 17:21                 ` Dale
2015-05-22 20:57                   ` [gentoo-user] [~and64] Headsup for googled the previous one to vmlinu-chrome users Neil Bothwick
2015-05-22 22:04                     ` Dale
2015-05-22 22:13                       ` Neil Bothwick
2015-05-22 22:29                         ` Mick
2015-05-22 22:58                           ` Neil Bothwick
2015-05-23  0:55                             ` Tom H
2015-05-23  8:17                               ` Neil Bothwick
2015-05-23  0:52                           ` Tom H
2015-05-23  4:21                           ` Walter Dnes
2015-05-23  3:19                         ` Dale
2015-05-22 21:09                   ` [gentoo-user] [~and64] Headsup for google-chrome users Daniel Frey
2015-05-22 22:11                     ` Dale
2015-05-22 10:44             ` Mick
2015-05-22 11:09               ` Alan McKinnon
2015-05-22 12:43                 ` Mick
2015-05-22 12:47       ` [gentoo-user] " walt
2015-05-22 13:32         ` Mick
2015-05-22 21:13           ` walt
2015-05-22 21:38             ` Tom H
2015-05-22 22:19               ` walt
2015-05-22 23:00                 ` Neil Bothwick
2015-05-23  0:30                 ` Tom H
2015-05-22 22:25               ` Mick
2015-05-22 10:15 ` Quanyang Liu
2015-05-22 13:28   ` walt [this message]
2015-05-22 14:32 ` [gentoo-user] " Behrouz Khosravi

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='mjnath$pgk$1@ger.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=gentoo-user@lists.gentoo.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