"D. R. Evans" writes:
> lee wrote on 11/20/2014 04:36 PM:
>> "D. R. Evans" writes:
>>
>>> I just installed wheezy on a new system, and no matter what I have tried, I
>>> am
>>> unable to get the attached monitor to display at 1920x1200. All my other
>>> systems display at that resolution when
"D. R. Evans" writes:
> Mark Neyhart wrote on 11/20/2014 05:49 PM:
>
>>> The update (auto-update.sh) executed without error with the message:
>>> "ASPEED Graphics Family Linux XORG 7.7 driver update finished"
>>>
>> This should result in the file ast_drv.so in
>> /usr/lib/xorg/modules/drivers
>
On Fri 21 Nov 2014 at 08:04:57 -0700, D. R. Evans wrote:
> Andrei POPESCU wrote on 11/20/2014 10:51 PM:
> > On Jo, 20 nov 14, 16:00:23, D. R. Evans wrote:
> >>
> >> The update (auto-update.sh) executed without error with the message:
> >> "ASPEED Graphics Family Linux XORG 7.7 driver update fini
lee wrote on 11/20/2014 04:36 PM:
> "D. R. Evans" writes:
>
>> I just installed wheezy on a new system, and no matter what I have tried, I
>> am
>> unable to get the attached monitor to display at 1920x1200. All my other
>> systems display at that resolution when attached to the same monitor.
>>
Andrei POPESCU wrote on 11/20/2014 10:51 PM:
> On Jo, 20 nov 14, 16:00:23, D. R. Evans wrote:
>>
>> The update (auto-update.sh) executed without error with the message:
>> "ASPEED Graphics Family Linux XORG 7.7 driver update finished"
>
> I'll stop with a stab in the dark: I see from your Xorg.0
Mark Neyhart wrote on 11/20/2014 05:49 PM:
>> The update (auto-update.sh) executed without error with the message:
>> "ASPEED Graphics Family Linux XORG 7.7 driver update finished"
>>
> This should result in the file ast_drv.so in
> /usr/lib/xorg/modules/drivers
>
> Is it there?
Yes; as I ment
On Jo, 20 nov 14, 16:00:23, D. R. Evans wrote:
>
> The update (auto-update.sh) executed without error with the message:
> "ASPEED Graphics Family Linux XORG 7.7 driver update finished"
I'll stop with a stab in the dark: I see from your Xorg.0.log that
you're running the -amd64 kernel. Could it
On 11/20/2014 02:00 PM, D. R. Evans wrote:
> Andrei POPESCU wrote on 11/20/2014 02:03 PM:
>
>> your adapter. It might be prudent to give more details about where you
>> obtained it from (e.g. the download page).
>
> I downloaded it from:
>
> http://www.asus.com/us/Commercial_Servers_Workstat
"D. R. Evans" writes:
> I just installed wheezy on a new system, and no matter what I have tried, I am
> unable to get the attached monitor to display at 1920x1200. All my other
> systems display at that resolution when attached to the same monitor.
>
> I won't bore you with all the things I've t
Andrei POPESCU wrote on 11/20/2014 02:03 PM:
> your adapter. It might be prudent to give more details about where you
> obtained it from (e.g. the download page).
I downloaded it from:
http://www.asus.com/us/Commercial_Servers_Workstations/P9DE4L/HelpDesk_Download/
Select Linux, then VGA. T
On 11/20/2014 11:05 AM, D. R. Evans wrote:
I just installed wheezy on a new system, and no matter what I have tried, I am
unable to get the attached monitor to display at 1920x1200. All my other
systems display at that resolution when attached to the same monitor.
I won't bore you with all the t
On Jo, 20 nov 14, 13:30:09, D. R. Evans wrote:
>
> I updated the ASPEED driver to make sure that it was the current version.
>
> Just in case it would help, I enabled the wheezy deb-multimedia repository and
> did a dist-upgrade (it made no difference).
...
> The only thing I know about the ast
Andrei POPESCU wrote on 11/20/2014 12:19 PM:
> On Jo, 20 nov 14, 12:05:11, D. R. Evans wrote:
>> I just installed wheezy on a new system, and no matter what I have tried, I
>> am
>> unable to get the attached monitor to display at 1920x1200. All my other
>> systems display at that resolution when
On Jo, 20 nov 14, 12:05:11, D. R. Evans wrote:
> I just installed wheezy on a new system, and no matter what I have tried, I am
> unable to get the attached monitor to display at 1920x1200. All my other
> systems display at that resolution when attached to the same monitor.
>
> I won't bore you wi
I just installed wheezy on a new system, and no matter what I have tried, I am
unable to get the attached monitor to display at 1920x1200. All my other
systems display at that resolution when attached to the same monitor.
I won't bore you with all the things I've tried without success. (At least,
On 21/03/14 16:22, W. Martin Borgert wrote:
> Hi,
>
> I set my system language to es_AR.UTF-8, but Orca seems to ignore this.
> When logged in, I can configure Orca to use Spanish, but what about GDM,
> i.e. before log in? The buttons etc. are in English, but Orca pronounces
> it all in English.
>
Hi,
I set my system language to es_AR.UTF-8, but Orca seems to ignore this.
When logged in, I can configure Orca to use Spanish, but what about GDM,
i.e. before log in? The buttons etc. are in English, but Orca pronounces
it all in English.
Thanks in advance!
--
To UNSUBSCRIBE, email to debian
The plain-old window managers are sufficiently different from Windows
and Apple that I feel comfortable stating that the developers are not
interested in keeping up with the current desktop trends. That gives
me
high confidence that there won't be many major changes in the way
those
window man
On Tuesday 18 December 2012 15:23:16 Rob Owens wrote:
> It's not clear how long the Gnome folks will continue to support the
> Gnome Classic session (which upstream Gnome refers to as Gnome Legacy).
> Some people may decide that their own ideals no longer align with the
> ideals of the Gnome develo
On Tue, Dec 18, 2012 at 04:21:47AM +, Russell L. Harris wrote:
> Can you recommend a good Wheezy HOWTO for users forcibly being
> migrated from the Gnome environment of Etch, Lenny, or Squeeze?
>
> I dread having to learn all the details of how to configure and use
> Wheezy once it becomes sta
On Mon, 17 Dec 2012, Bob Proulx wrote:
Russell L. Harris wrote:
Can you recommend a good Wheezy HOWTO for users forcibly being
migrated from the Gnome environment of Etch, Lenny, or Squeeze?
-- snip --
You could try MATE or another of the GNOME 2 fork projects that will
be around keeping
Russell L. Harris wrote:
> Can you recommend a good Wheezy HOWTO for users forcibly being
> migrated from the Gnome environment of Etch, Lenny, or Squeeze?
If you use GNOME 2 now and you upgrade to Wheezy then you will be
upgraded to GNOME 3 which as you know is quite different.
> I dread having
Can you recommend a good Wheezy HOWTO for users forcibly being
migrated from the Gnome environment of Etch, Lenny, or Squeeze?
I dread having to learn all the details of how to configure and use
Wheezy once it becomes stable.
RH
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On Thu, 19 Jan 2012 20:44:56 -0600, Kjetil brinchmann Halvorsen wrote:
> Hola!
Hola :-)
> In an earlier mail I told about problems with Xfce4/xfwm4 caused by
> updating.
>
> Now, I try to find out how to test alternatives, like enlightenment. I
> installed enlightenment (e17)
> through synaptic
Hola!
In an earlier mail I told about problems with Xfce4/xfwm4 caused by updating.
Now, I try to find out how to test alternatives, like enlightenment. I
installed enlightenment (e17)
through synaptic, but that was not enough to run it!
So how can I set up the system to have a possibulity to sw
On Wed, 03 Aug 2011 19:28:46 +0200, Jerome BENOIT wrote:
>>> Have anyone submit a bug report for it ?
>>
>> To enhance the gnome-keyring doc/readme? Nope (most probably because of
>> the aforementioned lazyness) :-)
>
> I see !
>
>
> In fact, a bug report was submit in April:
>
> http://bugs.d
Hello:
On 03/08/11 19:04, Camaleón wrote:
On Wed, 03 Aug 2011 18:33:39 +0200, Jerome BENOIT wrote:
On 03/08/11 14:07, Camaleón wrote:
(...)
Anyway, I sincerely doubt the only way to widely disable
"gnome-keyring- ssh" starts by forcing the user to compile the
application with ssh keyring-a
On Wed, 03 Aug 2011 18:33:39 +0200, Jerome BENOIT wrote:
> On 03/08/11 14:07, Camaleón wrote:
(...)
>> Anyway, I sincerely doubt the only way to widely disable
>> "gnome-keyring- ssh" starts by forcing the user to compile the
>> application with ssh keyring-app disable, that is a non-sense.
>> A
Hello:
On 03/08/11 14:07, Camaleón wrote:
On Tue, 02 Aug 2011 21:23:27 +0200, Jerome BENOIT wrote:
On 02/08/11 19:46, Camaleón wrote:
(...)
This does not actually remove gnome-keyring, but it does allow
lower level system software to handle SSH keys, for instance.
Yes, but is it a per us
On Tue, 02 Aug 2011 21:23:27 +0200, Jerome BENOIT wrote:
> On 02/08/11 19:46, Camaleón wrote:
(...)
>> This does not actually remove gnome-keyring, but it does allow
>> lower level system software to handle SSH keys, for instance.
>
> Yes, but is it a per useir set up, not a syst
On 20110802_090648, Jerome BENOIT wrote:
> Hello List:
>
> On 02/08/11 00:10, Paul E Condon wrote:
> >On 20110801_230130, Jerome BENOIT wrote:
> >>
> >>
> >>
> >>Indeed, because I would suspect that a lot of packages depend on
> >>gnome-keyring
> >>as I could read on Google. But as only a `minima
Hello:
On 02/08/11 19:46, Camaleón wrote:
On Tue, 02 Aug 2011 19:22:06 +0200, Jerome BENOIT wrote:
Hello:
On 02/08/11 17:42, Camaleón wrote:
On Tue, 02 Aug 2011 09:06:48 +0200, Jerome BENOIT wrote:
On 02/08/11 00:10, Paul E Condon wrote:
(...)
This does not actually remove gnome-keyrin
On Tue, 02 Aug 2011 19:22:06 +0200, Jerome BENOIT wrote:
> Hello:
>
> On 02/08/11 17:42, Camaleón wrote:
>> On Tue, 02 Aug 2011 09:06:48 +0200, Jerome BENOIT wrote:
>>
>>> On 02/08/11 00:10, Paul E Condon wrote:
>>
>> (...)
>>
This does not actually remove gnome-keyring, but it does allow lo
Hello:
On 02/08/11 17:42, Camaleón wrote:
On Tue, 02 Aug 2011 09:06:48 +0200, Jerome BENOIT wrote:
On 02/08/11 00:10, Paul E Condon wrote:
(...)
This does not actually remove gnome-keyring, but it does allow lower
level system software to handle SSH keys, for instance.
Yes, but is it a p
On Tue, 02 Aug 2011 09:06:48 +0200, Jerome BENOIT wrote:
> On 02/08/11 00:10, Paul E Condon wrote:
(...)
>> This does not actually remove gnome-keyring, but it does allow lower
>> level system software to handle SSH keys, for instance.
>
> Yes, but is it a per user set up, not a system wide set
Hello List:
On 02/08/11 00:10, Paul E Condon wrote:
On 20110801_230130, Jerome BENOIT wrote:
Indeed, because I would suspect that a lot of packages depend on gnome-keyring
as I could read on Google. But as only a `minimal' Gnome is actually
installed on my box, it appeared that no package de
On 20110801_230130, Jerome BENOIT wrote:
>
>
>
> Indeed, because I would suspect that a lot of packages depend on gnome-keyring
> as I could read on Google. But as only a `minimal' Gnome is actually
> installed on my box, it appeared that no package depends on it.
> OT: Gnome sounds heavy to me,
On 01/08/11 22:16, Camaleón wrote:
On Mon, 01 Aug 2011 13:16:43 -0600, Bob Proulx wrote:
Camaleón wrote:
Bob Proulx wrote:
I disagree. If the package isn't useful then removing it is very
likely the easiest solution. Why frustrate yourself trying to work
around the problem when removing t
On Mon, 01 Aug 2011 13:16:43 -0600, Bob Proulx wrote:
> Camaleón wrote:
>> Bob Proulx wrote:
>> > I disagree. If the package isn't useful then removing it is very
>> > likely the easiest solution. Why frustrate yourself trying to work
>> > around the problem when removing the problem is a good s
Camaleón wrote:
> Bob Proulx wrote:
> > I disagree. If the package isn't useful then removing it is very likely
> > the easiest solution. Why frustrate yourself trying to work around the
> > problem when removing the problem is a good solution too.
>
> IMO, removing should be the last resort, th
On Mon, 01 Aug 2011 20:33:45 +0200, Jerome BENOIT wrote:
> On 01/08/11 20:19, Camaleón wrote:
>> On Mon, 01 Aug 2011 20:02:56 +0200, Jerome BENOIT wrote:
>>
>>
>>> On 01/08/11 19:53, Camaleón wrote:
>>
>> (...)
>>
Should you have removed/renamed
>>>
>>> If I remember well, this causes trouble
On Mon, 01 Aug 2011 12:30:10 -0600, Bob Proulx wrote:
> Camaleón wrote:
>> Jerome BENOIT wrote:
>> > Finally I applied a brute force solution: I purged gnome-keyring.
>>
>> Wow, how drastic!
>
> I disagree. If the package isn't useful then removing it is very likely
> the easiest solution. Why
On 01/08/11 20:19, Camaleón wrote:
On Mon, 01 Aug 2011 20:02:56 +0200, Jerome BENOIT wrote:
On 01/08/11 19:53, Camaleón wrote:
(...)
Should you have removed/renamed
If I remember well, this causes trouble.
I meant removing the `/etc/xdg/autostart/gnome-keyring-ssh.desktop'
It shou
Camaleón wrote:
> Jerome BENOIT wrote:
> > Finally I applied a brute force solution: I purged gnome-keyring.
>
> Wow, how drastic!
I disagree. If the package isn't useful then removing it is very
likely the easiest solution. Why frustrate yourself trying to work
around the problem when removing
On Mon, 01 Aug 2011 20:02:56 +0200, Jerome BENOIT wrote:
>
> On 01/08/11 19:53, Camaleón wrote:
(...)
>> Should you have removed/renamed
>
> If I remember well, this causes trouble.
It shouldn't, at all. Is what README file says (removing the involving
elements from the menu so they don't ru
Hello List:
On 01/08/11 19:53, Camaleón wrote:
On Mon, 01 Aug 2011 19:39:27 +0200, Jerome BENOIT wrote:
On 01/08/11 13:51, Camaleón wrote:
On Mon, 01 Aug 2011 13:43:10 +0200, Jerome BENOIT wrote:
I have just migrated from Squeeze to Wheezy. It appeared that
gnome-keyring agent interferes wi
On Mon, 01 Aug 2011 19:39:27 +0200, Jerome BENOIT wrote:
> On 01/08/11 13:51, Camaleón wrote:
>> On Mon, 01 Aug 2011 13:43:10 +0200, Jerome BENOIT wrote:
>>
>>> I have just migrated from Squeeze to Wheezy. It appeared that
>>> gnome-keyring agent interferes with my ssh-agent set-up: I want to
>>>
Hello List:
Thanks for the link.
On 01/08/11 13:51, Camaleón wrote:
On Mon, 01 Aug 2011 13:43:10 +0200, Jerome BENOIT wrote:
I have just migrated from Squeeze to Wheezy. It appeared that
gnome-keyring agent interferes with my ssh-agent set-up: I want to
disable gnome-keyring agent for ssh.
A
On Mon, 01 Aug 2011 13:43:10 +0200, Jerome BENOIT wrote:
> I have just migrated from Squeeze to Wheezy. It appeared that
> gnome-keyring agent interferes with my ssh-agent set-up: I want to
> disable gnome-keyring agent for ssh.
>
> At the end of the README.Debian for gnome-keyring, it is suggest
Hello List:
I have just migrated from Squeeze to Wheezy.
It appeared that gnome-keyring agent interferes with my ssh-agent set-up:
I want to disable gnome-keyring agent for ssh.
At the end of the README.Debian for gnome-keyring, it is suggested
to ``simply edit /etc/xdg/autostart/gnome-keyring-s
50 matches
Mail list logo
