FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 12-16-2009, 01:10 AM
"Cybe R. Wizard"
 
Default

On Tue, 15 Dec 2009 17:28:24 +0100 (CET)
"Amedee Van Gasse (ub)" <amedee-ubuntu@amedee.be> wrote:

> I would like to share this with Cybe R. Wizard and all others who
> think that the CoC does not apply to them. I'm sorry, but Mr.
> Shuttleworth says that you are mistaken.

Actually I have questioned the CoC as applying to /anyone/, not just
me, from the /wording of the COC/, itself.

When viewed in conjunction with the mailing list etiquette guidelines I
can see how it may be taken to mean anyone, not just Ubuntu-approved
Members of The Community, and I fully agree /and always have/ that
it /should/ apply.

However, these two documents, one of which is necessary to the
full understanding of the other, are /not/ linked from the sign-up page
for the mailing list /at all/. It is hard for me to understand how
anyone may be held responsible for aligning their conduct with two
separate documents /to which no reference exists/ on the page where one
signs up for that same mailing list.

Continues below:
>
> ---------------------------- Original Message
> ---------------------------- Subject: Re: [Bug 495391] [NEW] Not
> clear if CoC applies only to official Ubuntu Members or also
> to community in general From: "Mark Shuttleworth"
> <mark@canonical.com> Date: Tue, December 15, 2009 17:05
> To: amedee-launchpad@amedee.be
> --------------------------------------------------------------------------
>
> Launchpad Bug Tracker wrote:
> > 2) The CoC is inferred from the Mailing List Etiquette guidelines
> > and
> applies to anyone on the mailing lists as soon as they have made any
> contribution, even if it was only one answer to a question of a new
> user.
> >
>
> The Code of Conduct is the standard we hold all participants and
> proponents and advocates of Ubuntu to. We'd prefer that if you want to
> wear an Ubuntu t-shirt, you hold yourself to that standard for
> discourse and collaboration. So it certainly applies to all
> correspondence on Ubuntu mailing lists, not just to those who have
> signed it and those who are Ubuntu members.
>
> Mark
>
I see the response from Mark and wish that it were, indeed, true,
but the obvious fact is that the user list is totally and completely
unmoderated. If such were not the case there would /at the very least/
be some response to the call for removal of <some user>, pro or con.

Until such time as the 'facts' bear out the actual usage I remain
skeptical of any 'wishes' anyone, even Mr. Shuttleworth, may have about
the tone of the list.

In addition, if the CoC is, "inferred from mailing list... guidelines,"
it would be quite nice if those guidelines were at least linked from the
sign-up page, even if the page does not hold a signing /requirement/.
A link to the CoC would be nice, too, if we hope that users will use it
to guide their use.

As it is there is not the slightest indication on the sign-up page that
there even /exists/ a mailing list guideline page, much less a Code of
Conduct.

If we wish to hold users of the mailing list to these 'suggestions'
then it would behoove us to include the information /that these
guidelines even exist/ for those who wish to sign up.

Otherwise it is only a sad joke that anyone thinks that folks should
abide by them.

IOW, we need to say what we mean if we are to mean what we say.

Cybe R. Wizard
--
"If the words "life, liberty and the pursuit of happiness" don't
include the right to experiment with your own consciousness, then the
Declaration of Independence isn't worth the hemp it was written on."
- Terence McKenna

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 12-16-2009, 06:11 AM
Pablo Duboue
 
Default

fixed 6.1.22
thanks

We don't ship the test WebApps enabled by default (from what I can
gather, it seems we don't ship them at all) and
this new version fixes the remaining XSS vulnerabilities (I double
checked the fix is in).

This bug will be closed when the new version gets uploaded.


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-16-2009, 09:07 AM
"Amedee Van Gasse (ub)"
 
Default

On Wed, December 16, 2009 03:10, Cybe R. Wizard wrote:

> Actually I have questioned the CoC as applying to /anyone/, not just
> me, from the /wording of the COC/, itself.

You should add that to the bug report.

> However, these two documents, one of which is necessary to the
> full understanding of the other, are /not/ linked from the sign-up page
> for the mailing list /at all/. It is hard for me to understand how
> anyone may be held responsible for aligning their conduct with two
> separate documents /to which no reference exists/ on the page where one
> signs up for that same mailing list.

You should add that to the bug report.

> In addition, if the CoC is, "inferred from mailing list... guidelines,"
> it would be quite nice if those guidelines were at least linked from the
> sign-up page, even if the page does not hold a signing /requirement/.
> A link to the CoC would be nice, too, if we hope that users will use it
> to guide their use.

You should add that to the bug report.

> As it is there is not the slightest indication on the sign-up page that
> there even /exists/ a mailing list guideline page, much less a Code of
> Conduct.

You should add that to the bug report.




The proper procedure for getting things fixed that are wrong or
incomplete, is to create a bug report on Launchpad and add all relevant
information.
Keep the bug report up-to-date until the problem is fixed, either by you
accepting the current state of things, or by a change of the
documentation.

If the bug report comes to a certain resolution and you do not agree, and
you have good arguments to disagree, then it is your moral duty to add
your objections to the bug report.

If you do not respond to a certain resolution, it is considered as your
agreement with the solution.


I have made one big mistake: I created the bug report for you. You should
have done it yourself. Why didn't you? At least you could have subscribed
to the bug report. By not subscribing, you show a lack of interest.

I don't want to be rude, but all this talk on the mailing lists isn't
productive. If you don't do what you are supposed to do to fix a problem,
then you have no reason to complain.

For the record, Cybe, your arguments are purely semantical, and in that
context I think that you are right. However semantics isn't everything,
and when people drag out their dictionary like you do, it usually means
that they ran out of other good arguments. If you continue this on the
lists without a constructive contribution to the bug report, I will see
that as a sign of bad faith.

Kind regards,

Amedee Van Gasse
(not feeling comfortable discussing non-technical stuff in a foreign
language)


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 12-16-2009, 01:01 PM
Mark Shuttleworth
 
Default

Cybe R. Wizard wrote:


If we wish to hold users of the mailing list to these 'suggestions'
then it would behoove us to include the information /that these
guidelines even exist/ for those who wish to sign up.


It's a great suggestion that we should point to the Code of Conduct on
all the email list signup pages. James, could you put that into action,
please?



Nevertheless, it's also perfectly reasonable that there be a code of
conduct that applies to a list. Everyone on ubuntu-users should now be
absolutely clear that this is the case, and that users who can't
exercise the appropriate judgment are not welcome on this list and
others at lists.ubuntu.com.



I would ask everyone on these lists to help new folks find their feet,
and help set the tone for the conversations that unfold here.



Mark



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 12-16-2009, 01:54 PM
"Cybe R. Wizard"
 
Default

On Wed, 16 Dec 2009 11:07:25 +0100 (CET)
"Amedee Van Gasse (ub)" <amedee-ubuntu@amedee.be> wrote:

> You should add that to the bug report.
>
I was just headed over to launchpad to sign up when the response from
Mr. Shuttleworth came in. It seems that the problem is being solved
as we type. That shows that one person /can/ make a difference
whether signed up on launchpad or not, I suppose.
>
> The proper procedure for getting things fixed that are wrong or
> incomplete, is to create a bug report on Launchpad and add all
> relevant information.
> Keep the bug report up-to-date until the problem is fixed, either by
> you accepting the current state of things, or by a change of the
> documentation.
>
> If the bug report comes to a certain resolution and you do not agree,
> and you have good arguments to disagree, then it is your moral duty
> to add your objections to the bug report.

Perhaps. I'll have to examine that position further.
>
> If you do not respond to a certain resolution, it is considered as
> your agreement with the solution.
>
That's an incorrect consideration as I might be dead or incapacitated.
Heck, I might just be very busy with real Life. I may have given up on
convincing anybody. Lack of response cannot prove a positive position.
>
> I have made one big mistake: I created the bug report for you. You
> should have done it yourself. Why didn't you? At least you could have
> subscribed to the bug report. By not subscribing, you show a lack of
> interest.

I think that, before deciding it was an actual bug (I'm still not
convinced; bugs exist only in /software/, IIANM) some discussion was
warranted, don't you? How can we know a problem really exists without
discussion?
>
> I don't want to be rude, but all this talk on the mailing lists isn't
> productive. If you don't do what you are supposed to do to fix a
> problem, then you have no reason to complain.

You aren't being rude, you have your own position. OTOH, the
discussion must have been productive as it has led directly to a
solution. Then there's the fact that one /always/ has a reason to
complain!
>
> For the record, Cybe, your arguments are purely semantical,

And that semantics is the basis upon which lawyers make fantastic
amounts of money. It /can't/ be dismissed easily.

> and in
> that context I think that you are right. However semantics isn't
> everything, and when people drag out their dictionary like you do, it
> usually means that they ran out of other good arguments.

Defining the terms with which we communicate is never a bad idea.
Without those definitions we can never hope to arrive at clear
understandings of what others mean. Without that clear understanding
everyone is a stranger to everyone else and, therefore, suspiciously
dangerous. That's not good in an international list.

>If you
> continue this on the lists without a constructive contribution to the
> bug report, I will see that as a sign of bad faith.

I hope such is not the case. I am only continuing it in /good/ faith
that it will work out for the best in the end (as it seems to be doing,
my membership on launchpad notwithstanding).
>
> Kind regards,
>
> Amedee Van Gasse
> (not feeling comfortable discussing non-technical stuff in a foreign
> language)

Just because it doesn't concern the coding or working of the code in
Ubuntu doesn't mean that it isn't technical.
(and here I must drag out the dictionary to illustrate my point)
 
Old 12-16-2009, 08:04 PM
Tommy Trussell
 
Default

On Wed, Dec 16, 2009 at 8:54 AM, Cybe R. Wizard
<cyber_wizard@mindspring.com> wrote:
> I think that, before deciding it was an actual bug (I'm still not
> convinced; bugs exist only in /software/, IIANM) some discussion was
> warranted, don't you?

The concept of a "bug" as a defect or flaw predates the "computer
era."* I believe Ubuntu is not alone in its practice of managing
non-software issues using the bug tracking system.

* http://en.wikipedia.org/wiki/Software_bug#Etymology

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 12-16-2009, 08:53 PM
James Troup
 
Default

Mark Shuttleworth <mark@canonical.com> writes:

> Cybe R. Wizard wrote:
>> If we wish to hold users of the mailing list to these 'suggestions'
>> then it would behoove us to include the information /that these
>> guidelines even exist/ for those who wish to sign up.
>>
> It's a great suggestion that we should point to the Code of Conduct on
> all the email list signup pages. James, could you put that into action,
> please?

Done, viz.:

| root@chlorine:/etc/# bzr di
| === modified file 'mailman/en/listinfo.html'
| --- mailman/en/listinfo.html 2009-12-14 17:07:07 +0000
| +++ mailman/en/listinfo.html 2009-12-16 21:43:12 +0000
| @@ -62,7 +62,7 @@
| <td colspan="2">
| <P>
| Subscribe to <MM-List-Name> by filling out the following
| - form.
| + form. Please respect the <a href="http://www.ubuntu.com/community/conduct">Ubuntu Code of Conduct</a> when posting to this list.
| <ul>
| <MM-List-Subscription-Msg>
| <TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2"
|
| === modified file 'mailman/en/subscribeack.txt'
| --- mailman/en/subscribeack.txt 2007-03-09 13:37:26 +0000
| +++ mailman/en/subscribeack.txt 2009-12-16 21:45:21 +0000
| @@ -4,6 +4,12 @@
|
| %(emailaddr)s
|
| +Please respect the Ubuntu Code of Conduct when posting to this list.
| +
| +You can find the Ubuntu Code of Conduct at:
| +
| + <http://www.ubuntu.com/community/conduct>
| +
| General information about the mailing list is at:
|
| %(listinfo_url)s

This is English only at the moment, if anyone wants to contribute
suitable text for the other languages mailman has templates for please
follow-up to rt@ubuntu.com. Thanks.

--
James

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 12-17-2009, 03:37 PM
Ralf Mardorf
 
Default

_Hi developers_

there's trouble with setting up X for 64 Studio 3.0-beta3. I don't know
if the others are fine with X now. I could (half-)solve the trouble I
had, but I don't know a solution to solve this in general.


I guess this is the complete thread:

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-November/003940.html>
/chan /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-November/003941.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-November/003942.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-November/003943.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-November/003945.html>
/Jonathan Leonard /


* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003951.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003952.html>
/tim hall /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003953.html>
/Jonathan Leonard /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003954.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003955.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003956.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003957.html>
/Gustin Johnson /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003958.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003959.html>
/tim hall /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003960.html>
/Jonathan Leonard /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003961.html>
/Gustin Johnson /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003962.html>
/tim hall /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003963.html>
/Ralf Mardorf /

* [64studio-users] X Configuration - Episode 1 "xrandr semms to be
useless for my problem"
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003964.html>
/Ralf Mardorf /

* [64studio-users] X Configuration - Episode 2 "For Suse it's fine,
for 64 Studio not yet"
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003965.html>
/Ralf Mardorf/


Developers, please directly reply to me or to the users list. I'm not
receiving mail from the developers list and I also very seldom write to
this list./

/
_Hi users_

I was able to solve it for this set up and for GNOME, it's not a
solution in general.


I puzzled out a xorg.conf and copied it to /etc/X11, see attachment.
Sources for the puzzle were those two xorg.configurations:

http://lists.64studio.com/pipermail/64studio-users/attachments/20091217/338c7e9e/attachment.txt
http://lists.64studio.com/pipermail/64studio-users/attachments/20091217/338c7e9e/attachment-0001.txt

After a restart the xorg.conf kept unchanged:

spinymouse-sudo@64studio:~/Desktop$ diff xorg.conf_puzzle /etc/X11/xorg.conf

No diff.

But the session started with a resolution of 1024x768@60Hz, using the
GNOME utility it's possible to select different resolutions (I guess all
possible resolutions) and frequencies (not all frequencies, but 60, 75,
85 and 90Hz). It's possible to set up the wanted 1152x862@90Hz (results
in 82.0KHz : 90.0Hz).


I checked it with a second restart. Unexpected the session automatically
started with the wanted 1152x864@90Hz (even if it resulted in *81.9KHz*
and 90.0Hz) , all resolutions still seems to be available, but now
only 75, 86 and 90 Hz are available, btw. GDM is using a higher
resolution @ 60Hz .


Running

spinymouse-sudo@64studio:~/Desktop$ diff xorg.conf_puzzle /etc/X11/xorg.conf

there's still no diff.

I guess it would be possible to optimize it, but for now I'll keep it
this way, even if I guess it only will be fine for GNOME at the moment,
anyway, it's the DE I prefer now.


The problem still is, that I needed Suse to get information about the
settings and the xorg.conf for my old monitor, getting this xorg.conf
for my old monitor for 64 Studio 3.0-beta3 once also was a PITA (but it
was fine for GDM and every WM/ DE).


There should be something similar to Suse's "sax2 -r" for 64 Studio too,
or if possible something similar to Windows, were all settings are
available, without using any command . Btw. for Windows I used ATI's
Catalyst, while for Linux I can't use the proprietary driver and Catalyst.


My personal résumé is, that this is still an issue that needs attention
by the developers.


Cheers,
Ralf
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
Option "XkbVariant" "ro"
Option "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "Device"
Identifier "Configured Video Device"
Boardname "VESA driver (generic)"
Busid "PCI:1:5:0"
Driver "radeon"
Screen 0
Option "MergedFB" "off"
EndSection

Section "Monitor"
DisplaySize 305 230
HorizSync 29-98
Identifier "Configured Monitor"
Modelname "Plug 'n' Play"
Vendorname "Plug 'n' Play"
VertRefresh 50-120
modeline "1152x864" 128.42 1152 1232 1360 1568 864 865 868 910
Gamma 1.0
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
Defaultdepth 24
SubSection "Display"
Depth 24
Modes "1152x864"
Virtual 3840 1200
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
screen 0 "Default Screen" 0 0
EndSection
Section "Module"
Load "glx"
Load "GLcore"
Load "v4l"
EndSection
Section "ServerFlags"
EndSection

_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel
 
Old 12-17-2009, 03:37 PM
Ralf Mardorf
 
Default

_Hi developers_

there's trouble with setting up X for 64 Studio 3.0-beta3. I don't know
if the others are fine with X now. I could (half-)solve the trouble I
had, but I don't know a solution to solve this in general.


I guess this is the complete thread:

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-November/003940.html>
/chan /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-November/003941.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-November/003942.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-November/003943.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-November/003945.html>
/Jonathan Leonard /


* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003951.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003952.html>
/tim hall /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003953.html>
/Jonathan Leonard /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003954.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003955.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003956.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003957.html>
/Gustin Johnson /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003958.html>
/Ralf Mardorf /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003959.html>
/tim hall /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003960.html>
/Jonathan Leonard /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003961.html>
/Gustin Johnson /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003962.html>
/tim hall /

* [64studio-users] mobo nvidia6100 max 640x480
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003963.html>
/Ralf Mardorf /

* [64studio-users] X Configuration - Episode 1 "xrandr semms to be
useless for my problem"
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003964.html>
/Ralf Mardorf /

* [64studio-users] X Configuration - Episode 2 "For Suse it's fine,
for 64 Studio not yet"
<http://lists.64studio.com/pipermail/64studio-users/2009-December/003965.html>
/Ralf Mardorf/


Developers, please directly reply to me or to the users list. I'm not
receiving mail from the developers list and I also very seldom write to
this list./

/
_Hi users_

I was able to solve it for this set up and for GNOME, it's not a
solution in general.


I puzzled out a xorg.conf and copied it to /etc/X11, see attachment.
Sources for the puzzle were those two xorg.configurations:

http://lists.64studio.com/pipermail/64studio-users/attachments/20091217/338c7e9e/attachment.txt
http://lists.64studio.com/pipermail/64studio-users/attachments/20091217/338c7e9e/attachment-0001.txt

After a restart the xorg.conf kept unchanged:

spinymouse-sudo@64studio:~/Desktop$ diff xorg.conf_puzzle /etc/X11/xorg.conf

No diff.

But the session started with a resolution of 1024x768@60Hz, using the
GNOME utility it's possible to select different resolutions (I guess all
possible resolutions) and frequencies (not all frequencies, but 60, 75,
85 and 90Hz). It's possible to set up the wanted 1152x862@90Hz (results
in 82.0KHz : 90.0Hz).


I checked it with a second restart. Unexpected the session automatically
started with the wanted 1152x864@90Hz (even if it resulted in *81.9KHz*
and 90.0Hz) , all resolutions still seems to be available, but now
only 75, 86 and 90 Hz are available, btw. GDM is using a higher
resolution @ 60Hz .


Running

spinymouse-sudo@64studio:~/Desktop$ diff xorg.conf_puzzle /etc/X11/xorg.conf

there's still no diff.

I guess it would be possible to optimize it, but for now I'll keep it
this way, even if I guess it only will be fine for GNOME at the moment,
anyway, it's the DE I prefer now.


The problem still is, that I needed Suse to get information about the
settings and the xorg.conf for my old monitor, getting this xorg.conf
for my old monitor for 64 Studio 3.0-beta3 once also was a PITA (but it
was fine for GDM and every WM/ DE).


There should be something similar to Suse's "sax2 -r" for 64 Studio too,
or if possible something similar to Windows, were all settings are
available, without using any command . Btw. for Windows I used ATI's
Catalyst, while for Linux I can't use the proprietary driver and Catalyst.


My personal résumé is, that this is still an issue that needs attention
by the developers.


Cheers,
Ralf
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
Option "XkbVariant" "ro"
Option "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "Device"
Identifier "Configured Video Device"
Boardname "VESA driver (generic)"
Busid "PCI:1:5:0"
Driver "radeon"
Screen 0
Option "MergedFB" "off"
EndSection

Section "Monitor"
DisplaySize 305 230
HorizSync 29-98
Identifier "Configured Monitor"
Modelname "Plug 'n' Play"
Vendorname "Plug 'n' Play"
VertRefresh 50-120
modeline "1152x864" 128.42 1152 1232 1360 1568 864 865 868 910
Gamma 1.0
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
Defaultdepth 24
SubSection "Display"
Depth 24
Modes "1152x864"
Virtual 3840 1200
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
screen 0 "Default Screen" 0 0
EndSection
Section "Module"
Load "glx"
Load "GLcore"
Load "v4l"
EndSection
Section "ServerFlags"
EndSection

_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users
 
Old 12-18-2009, 11:49 PM
David McGuffey
 
Default

On Mon, 2009-12-14 at 21:31 -0500, Mathew S. McCarrell wrote:
> On Mon, Dec 14, 2009 at 7:31 PM, David McGuffey
> <davidmcguffey@verizon.net> wrote:
> Here is what my logs show for the last three updates that ran
> successfully:
>
> Nov 14 10:02:13 Updated: 1:libvorbis-1.1.2-3.el5_4.4.x86_64
> Nov 14 10:02:13 Installed: libmpeg2-0.5.1-2.el5.rf.x86_64
> Nov 14 10:02:14 Installed:
> libmpeg2-utils-0.5.1-2.el5.rf.x86_64
> Nov 14 10:02:17 Updated: httpd-2.2.3-31.el5.centos.2.x86_64
> Nov 14 10:02:17 Updated: dbus-python-0.70-9.el5_4.x86_64
> Nov 14 10:02:18 Updated: 1:libvorbis-1.1.2-3.el5_4.4.i386
> Nov 14 10:02:19 Updated:
> 1:libvorbis-devel-1.1.2-3.el5_4.4.i386
> Nov 14 10:02:19 Updated:
> 1:libvorbis-devel-1.1.2-3.el5_4.4.x86_64
> Nov 14 10:02:19 Erased: mpeg2dec
> Nov 17 21:26:08 Installed: aide-0.13.1-4.el5.x86_64
> Nov 24 22:04:43 Updated: 1:cups-libs-1.3.7-11.el5_4.4.x86_64
> Nov 24 22:04:44 Updated: 1:cups-libs-1.3.7-11.el5_4.4.i386
> Nov 24 22:04:52 Updated: 1:cups-1.3.7-11.el5_4.4.x86_64
> Nov 27 08:59:17 Installed: twolame-0.3.12-1.el5.rf.x86_64
> Nov 27 08:59:18 Updated:
> gstreamer-plugins-ugly-0.10.11-1.el5.rf.x86_64
> Nov 27 08:59:18 Updated:
> gstreamer-ffmpeg-0.10.6-1.el5.rf.x86_64
> Nov 28 08:35:38 Updated: metacity-2.16.0-12.el5_4.1.x86_64
> Nov 28 08:35:38 Updated: xterm-215-8.el5_4.1.x86_64
> Nov 28 08:35:39 Updated: kexec-tools-1.102pre-77.el5.3.x86_64
> Nov 28 08:35:41 Updated:
> system-config-lvm-1.1.5-1.0.el5_4.1.noarch
> Nov 28 08:35:47 Updated: metacity-2.16.0-12.el5_4.1.i386
>
>
> So...maybe I'm just an IA guy with a worrying problem. I'm
> used to my
> Windoze boxes updating nearly every time I boot them. I'm
> also used to
> Fedora 10 and 11 which seem to have updates every two or three
> days.
>
> DaveM

Yes, I'm worrying too much. Must be my Information Assurance
background. 13 updates showed up today.

Dec 18 19:40:56 Updated: glibc-common-2.5-42.el5_4.2.x86_64
Dec 18 19:41:13 Updated: glibc-2.5-42.el5_4.2.x86_64
Dec 18 19:41:14 Updated: kernel-headers-2.6.18-164.9.1.el5.x86_64
Dec 18 19:41:29 Installed: kernel-2.6.18-164.9.1.el5.x86_64
Dec 18 19:41:50 Updated: kmod-kvm-83-105.el5_4.13.x86_64
Dec 18 19:41:51 Updated: kvm-83-105.el5_4.13.x86_64
Dec 18 19:41:51 Updated: kvm-qemu-img-83-105.el5_4.13.x86_64
Dec 18 19:41:51 Updated: libtool-1.5.22-7.el5_4.x86_64
Dec 18 19:41:56 Installed: kernel-devel-2.6.18-164.9.1.el5.x86_64
Dec 18 19:41:57 Updated: glibc-2.5-42.el5_4.2.i686
Dec 18 19:41:59 Updated: xulrunner-1.9.0.16-2.el5_4.x86_64
Dec 18 19:41:59 Updated: 30:bind-libs-9.3.6-4.P1.el5_4.1.x86_64
Dec 18 19:42:01 Updated: openssh-4.3p2-36.el5_4.3.x86_64
Dec 18 19:42:01 Updated: expat-1.95.8-8.3.el5_4.2.x86_64
Dec 18 19:42:02 Updated: samba-common-3.0.33-3.15.el5_4.1.x86_64
Dec 18 19:42:02 Updated: kpartx-0.4.7-30.el5_4.4.x86_64
Dec 18 19:42:02 Updated: libtool-ltdl-1.5.22-7.el5_4.x86_64
Dec 18 19:42:04 Updated: xulrunner-1.9.0.16-2.el5_4.i386
Dec 18 19:42:04 Updated: expat-1.95.8-8.3.el5_4.2.i386
Dec 18 19:42:05 Updated: device-mapper-multipath-0.4.7-30.el5_4.4.x86_64
Dec 18 19:42:06 Updated: samba-client-3.0.33-3.15.el5_4.1.x86_64
Dec 18 19:42:08 Updated: samba-3.0.33-3.15.el5_4.1.x86_64
Dec 18 19:42:08 Updated: openssh-clients-4.3p2-36.el5_4.3.x86_64
Dec 18 19:42:08 Updated: openssh-askpass-4.3p2-36.el5_4.3.x86_64
Dec 18 19:42:09 Updated: openssh-server-4.3p2-36.el5_4.3.x86_64
Dec 18 19:42:09 Updated: 30:bind-utils-9.3.6-4.P1.el5_4.1.x86_64
Dec 18 19:42:14 Updated: xulrunner-devel-1.9.0.16-2.el5_4.x86_64
Dec 18 19:42:14 Updated: acpid-1.0.4-9.el5_4.1.x86_64
Dec 18 19:42:14 Updated: screen-4.0.3-1.el5_4.1.x86_64
Dec 18 19:42:14 Updated: nscd-2.5-42.el5_4.2.x86_64
Dec 18 19:42:18 Updated: xulrunner-devel-1.9.0.16-2.el5_4.i386
Dec 18 19:42:19 Updated: glibc-headers-2.5-42.el5_4.2.x86_64
Dec 18 19:42:22 Updated: firefox-3.0.16-1.el5.centos.i386
Dec 18 19:42:23 Updated: glibc-devel-2.5-42.el5_4.2.i386
Dec 18 19:42:23 Updated: expat-devel-1.95.8-8.3.el5_4.2.x86_64
Dec 18 19:42:23 Updated: expat-devel-1.95.8-8.3.el5_4.2.i386
Dec 18 19:42:24 Updated: firefox-3.0.16-1.el5.centos.x86_64
Dec 18 19:42:25 Updated: glibc-devel-2.5-42.el5_4.2.x86_64

DaveM



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 11:56 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org