El miércoles, 11 de enero de 2006 04:48, X Strike Force SVN Repository Admin
escribió:
Author: dnusinow
Date: 2006-01-10 22:48:31 -0500 (Tue, 10 Jan 2006)
New Revision: 1058
Modified:
branches/modular/lib/mesa-6.4.1/debian/changelog
branches/modular/lib/mesa-6.4.1/debian/control
Your message dated Wed, 11 Jan 2006 11:19:03 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#333765: #333765 xterm -e no longer works with relative
paths
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 11 Jan 2006 11:19:03 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#333765: #333765 xterm -e no longer works with relative
paths
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 11 Jan 2006 11:19:03 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#333765: #333765 xterm -e no longer works with relative
paths
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 11 Jan 2006 11:19:03 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#333765: #333765 xterm -e no longer works with relative
paths
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 11 Jan 2006 11:19:03 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#333765: #333765 xterm -e no longer works with relative
paths
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 11 Jan 2006 11:19:03 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#333765: #333765 xterm -e no longer works with relative
paths
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 11 Jan 2006 11:19:03 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#333765: #333765 xterm -e no longer works with relative
paths
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 11 Jan 2006 11:19:03 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#333765: #333765 xterm -e no longer works with relative
paths
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 11 Jan 2006 11:19:03 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#333765: #333765 xterm -e no longer works with relative
paths
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Can you please add the workaround described below to the DRM problems
with kernels 2.6.14+15 to next release of Xorg. Obviously the kernel
module patch will not be included until kernel 2.6.16.
For direct rendering with MGA graphics cards use the following option in
the Device section of
Version: 208-1
David Nusinow forgot to run dpkg-buildpackage with -v option, in order
to
close bugs from previous version. All these bugs were closed by xterm
204-0pre1 in experimental, and 208-1 in unstable.
Best regards,
Ender.
--
Another C-3PO: E chu ta!
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 11 Jan 2006 11:49:34 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing bugs fixed in xterm 208-1.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Author: ender
Date: 2006-01-11 05:19:43 -0500 (Wed, 11 Jan 2006)
New Revision: 1061
Modified:
trunk/debian/changelog
trunk/debian/po/tr.po
Log:
Updated Turkish translation. Thanks, Recai Okta?\195?\133~_ (closes: #347494).
Modified: trunk/debian/changelog
Author: ender
Date: 2006-01-11 05:21:53 -0500 (Wed, 11 Jan 2006)
New Revision: 1062
Modified:
trunk/debian/changelog
Log:
Add Osman Y?\195?\188ksel to thanks.
Modified: trunk/debian/changelog
===
--- trunk/debian/changelog
tag 347494 + pending
thanks for the fish
El miércoles, 11 de enero de 2006 04:02, Recai Oktaş escribió:
Package: xorg-x11
Severity: wishlist
Tags: l10n patch
Please find attached the Turkish po-debconf translation. Thanks to Osman
Yüksel.
Thank you very much, Recai. Your
Processing commands for [EMAIL PROTECTED]:
tag 347494 + pending
Bug#347494: [INTL:tr] Turkish po-debconf update
Tags were: l10n patch
Tags added: pending
thanks for the fish
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Author: ender
Date: 2006-01-11 05:46:20 -0500 (Wed, 11 Jan 2006)
New Revision: 1063
Modified:
trunk/debian/changelog
trunk/debian/po/ja.po
Log:
Updated Japanese translation. Thanks, Kenshi Muto (closes: #347498).
Modified: trunk/debian/changelog
El domingo, 18 de diciembre de 2005 05:56, Ross Boylan escribió:
[..]
The failure acts a bit differently than the original high CPU in this
bug's title; now it seems to just die without leaving any informative
diagnostics.
[...]
Hello, Ross. Could you please test latest unstable
Your message dated Wed, 11 Jan 2006 11:34:43 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#342782: xterm -e ./cmd tries to find a wrong program cmd
and crashes
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
The problem turned out to be a mixture of two
causes:
1) A bug in my .bash_profile, and
2) a vulnerability in X (a design flaw).
In my .bash_profile, I had lines in the form of
set line_oriented_history=on
These lines should have been in my .inputrc, instead.
When placed in .bash_profile, they
Package: xlibs-data
Version: 6.9.0.dfsg.1-3
Severity: minor
File: /usr/X11R6/lib/X11/locale/compose.dir
Compose is not working in Qt-based applications (and in GTK applications
if input module set to xim) if LC_CTYPE=cs_CZ.UTF-8
I've noticed that /usr/X11R6/lib/X11/locale/compose.dir contains
tag 347498 + pending
thanks for the fish
El miércoles, 11 de enero de 2006 05:48, kmuto escribió:
Package: xorg-x11
Severity: wishlist
Version: svn
Tags: l10n patch
Hi,
I updated Japanese debconf translation.
Please apply this.
Thank you very much, Kenshi. Your translation is
Processing commands for [EMAIL PROTECTED]:
tag 347498 + pending
Bug#347498: xorg-x11: [INTL:ja] updated Japanese debconf translation
Tags were: l10n patch
Tags added: pending
thanks for the fish
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Author: ender
Date: 2006-01-11 07:26:45 -0500 (Wed, 11 Jan 2006)
New Revision: 1064
Modified:
trunk/debian/changelog
trunk/debian/patches/general/011a_recognize_glibc_2.3.2_locale_names.diff
Log:
Fixed Compose key for LC_CTYPE=cs_CZ.UTF-8 (closes: #347531).
Modified:
tag 347531 + pending
thanks for the fish
El miércoles, 11 de enero de 2006 12:16, Marek Schmidt escribió:
Compose is not working in Qt-based applications (and in GTK applications
if input module set to xim) if LC_CTYPE=cs_CZ.UTF-8
I've noticed that /usr/X11R6/lib/X11/locale/compose.dir
Processing commands for [EMAIL PROTECTED]:
tag 347531 + pending
Bug#347531: /usr/X11R6/lib/X11/locale/compose.dir: compose not working if
LC_CTYPE=cs_CZ.UTF-8
There were no tags set.
Tags added: pending
thanks for the fish
Stopping processing here.
Please contact me if you need assistance.
Package: xutils
Version: 6.9.0.dfsg.1-3
Severity: normal
The 'resize' binary is missing in the xutils package in the version
above. It seems to be missing since version 6.9.0. For now, I
reverted to xutils version xutils_6.8.2.dfsg.1-11_i386.deb which
still includes the 'resize' binary.
--
On Wed, Jan 11, 2006 at 01:27:46PM +0100, David Martínez Moreno wrote:
tag 347531 + pending
thanks for the fish
El miércoles, 11 de enero de 2006 12:16, Marek Schmidt escribió:
Compose is not working in Qt-based applications (and in GTK applications
if input module set to xim) if
On Fri, 2006-01-06 at 20:31 +0100, Dominique Dumont wrote:
Michel Dänzer [EMAIL PROTECTED] writes:
On Thu, 2006-01-05 at 21:51 +0100, Lionel Elie Mamane wrote:
MergedFB false doesn't send signal to secondary, [...]
I think that's expected, as MergedFB unifies all
Package: xserver-xorg
Version: 6.9.0.dfsg.1-3
Severity: normal
I somehow cannot enable DRI. I always get the message
(EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
in the Xorg.0.log.
I tried many configuration options already and all the hints from the
FAQs and newsgroups I could
On Tue, Jan 10, 2006 at 11:06:21PM -0500, Felix-Antoine Bourbonnais wrote:
Package: xlibs
Version: 6.9.0.dfsg.1-2
Severity: normal
Since I have upgraded my xlibs package to 6.9.0.dfsg, my French Canadian
(ca_enhanced) keyboard doesn't work anymore in XOrg. I have an error about
the
This has also happened to me without any binary driver. Once with
6.9.0.dfsg.1-2 and once 6.9.0 but I don't remember which version
(probably 1-1). X makes computer very slow, top shows it's xorg.
Switching to text console and back cured it for me on both occassions. I
was running KDE both
Ok It's better but it's still not perfect. Normally, to write è, I type
` + e. But with this configuration the è is done directly with one key.
There is other things like the for which I usually use SHIFT+2 but now
it's done by SHIT+. .
Thanks,
Denis Barbier wrote:
On Tue, Jan 10, 2006 at
After upgrading to Xorg 6.9 in unstable, the problem remains. However,
I found out that X does start if I simply leave the S-VHS connection
to the TV unplugged (and connect it after starting X).
--
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22
signature.asc
Description: Digital
On Wed, 2006-01-11 at 16:58 +0100, Stefan Borggraefe wrote:
Package: xserver-xorg
Version: 6.9.0.dfsg.1-3
Severity: normal
I somehow cannot enable DRI. I always get the message
(EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
in the Xorg.0.log.
Any corresponding kernel
Hi,
I have noted that X believes that the second monitor is alive; the
desktop is sized as if both monitors were working. I can move the mouse
cursor to the secondary monitor (blinking No signal) and I can also
move windows to the secondary monitor. It's tricky to move them back
into view,
I noted this new warning message:
The XKEYBOARD keymap compiler (xkbcomp) reports:
Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
Denis Barbier wrote:
On Tue, Jan 10, 2006 at 11:06:21PM -0500, Felix-Antoine Bourbonnais wrote:
On Wed, Jan 11, 2006 at 11:44:50AM -0500, Felix-Antoine Bourbonnais wrote:
Ok It's better but it's still not perfect. Normally, to write è, I type
` + e. But with this configuration the è is done directly with one key.
There is other things like the for which I usually use SHIFT+2 but now
On Wed, Jan 11, 2006 at 04:12:19PM +0200, Martin-Éric Racine wrote:
Package: xlibs
Version: 6.9.0.dfsg.1-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After upgrading GNOME to the 2.12 packages in Unstable,
I keep on getting the following message at every login:
Author: barbier
Date: 2006-01-11 16:10:20 -0500 (Wed, 11 Jan 2006)
New Revision: 1065
Added:
trunk/debian/local/Compose
Log:
This file will be installed at /etc/X11/Compose so that users
can customize their compose sequences.
Added: trunk/debian/local/Compose
Author: barbier
Date: 2006-01-11 16:19:15 -0500 (Wed, 11 Jan 2006)
New Revision: 1066
Added:
trunk/debian/patches/general/086_enable_ca_variants.diff
Modified:
trunk/debian/changelog
trunk/debian/patches/series
Log:
* Add general/086_enable_ca_variants.diff so that variants of the ca
On Tue, Jan 10, 2006 at 05:50:37PM -0500, David Nusinow wrote:
On Tue, Jan 10, 2006 at 11:15:55PM +0100, Denis Barbier wrote:
On Wed, Jan 11, 2006 at 12:02:27AM +0200, Anton Zinoviev wrote:
On Mon, Jan 09, 2006 at 11:55:57AM +0100, Denis Barbier wrote:
IMO this solution is much
Hi Denis,
ke, 2006-01-11 kello 21:26 +0100, Denis Barbier kirjoitti:
On Wed, Jan 11, 2006 at 04:12:19PM +0200, Martin-Éric Racine wrote:
Package: xlibs
Version: 6.9.0.dfsg.1-3
Severity: important
After upgrading GNOME to the 2.12 packages in Unstable,
I keep on getting the
Author: barbier
Date: 2006-01-11 17:08:33 -0500 (Wed, 11 Jan 2006)
New Revision: 1067
Added:
trunk/debian/patches/general/013_xkb_drop_rules_xorg_duplicates.diff
Modified:
trunk/debian/changelog
trunk/debian/patches/general/091_xkb_implement_compose:caps.diff
Package: xserver-xorg
Version: 6.9.0.dfsg.1-3
Followup-For: Bug #345480
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Adam Borowski [EMAIL PROTECTED] wrote on 31 Dec 2005:
I use a console size bigger than 80x25, and when I switch vt to a Text
console, the kernel's idea (ie,
Author: barbier
Date: 2006-01-11 17:32:07 -0500 (Wed, 11 Jan 2006)
New Revision: 1068
Added:
trunk/debian/patches/general/087_xkb_ralt_switch_multikey.diff
Modified:
trunk/debian/changelog
trunk/debian/patches/series
Log:
Add general/087_xkb_ralt_switch_multikey.diff to enable again the
Package: xserver-xorg
Version: 6.9.0.dfsg.1-3
Severity: important
First X crash in *years*...
I was browsing the web, selecting some text, and bang, kicked out.
From the end of my Xorg.0.log.old:
[...]
(--) Touchpad auto-dev sets device to /dev/input/event3
(**) Option Device /dev/input/event3
On Wed, Jan 11, 2006 at 11:35:39PM +0200, Martin-Éric Racine wrote:
Anyhow, even after purging the packages and force-removing /etc/X11/xkb,
then re-installing the packages, adding secondary keymaps via GNOME's
keyboard preferences again made the error message appear.
Does it work for some
We believe that the bug you reported is fixed in the latest version
of xterm, ...
Looks good to me. Thanks.
I find that I am still curious about the path. I wrote:
BTW, I noticed that the path to xterm has changed from
/usr/bin/X11/xterm
to
/usr/bin/xterm
. This is not a problem
On Thu, Jan 12, 2006 at 12:24:14AM +0200, Martin-Éric Racine wrote:
ke, 2006-01-11 kello 23:17 +0100, Denis Barbier kirjoitti:
On Wed, Jan 11, 2006 at 11:35:39PM +0200, Martin-Éric Racine wrote:
Anyhow, even after purging the packages and force-removing /etc/X11/xkb,
then re-installing
ke, 2006-01-11 kello 23:33 +0100, Denis Barbier kirjoitti:
On Thu, Jan 12, 2006 at 12:24:14AM +0200, Martin-Éric Racine wrote:
ke, 2006-01-11 kello 23:17 +0100, Denis Barbier kirjoitti:
On Wed, Jan 11, 2006 at 11:35:39PM +0200, Martin-Éric Racine wrote:
Anyhow, even after purging the
ke, 2006-01-11 kello 23:17 +0100, Denis Barbier kirjoitti:
On Wed, Jan 11, 2006 at 11:35:39PM +0200, Martin-Éric Racine wrote:
Anyhow, even after purging the packages and force-removing /etc/X11/xkb,
then re-installing the packages, adding secondary keymaps via GNOME's
keyboard preferences
On Wed, Jan 11, 2006 at 04:12:19PM +0200, Martin-Éric Racine wrote:
[...]
(**) Option XkbRules xorg
(**) Generic Keyboard: XkbRules: xorg
(**) Option XkbModel pc105
(**) Generic Keyboard: XkbModel: pc105
(**) Option XkbLayout fi
(**) Generic Keyboard: XkbLayout: fi
Back to your original
Hei!
Thanks Kaare Hviid! Adding the suggested option AGPMode under the
Device section really made the crashes go away. glxgears works now as
expected. Sorry for false bug report, it turned out to be my ignorance
instead. No surprise here, i guess. :-)
Juhan
--
To UNSUBSCRIBE, email to [EMAIL
reopen 346461
thanks
Debian Bug Tracking System [EMAIL PROTECTED] writes:
This is an automatic notification regarding your Bug report
346461: AllowMouseOpenFail doesn't work with evdev-mouse,
which was filed against the xserver-xorg package.
It has been closed by one of the developers,
to, 2006-01-12 kello 00:02 +0100, Denis Barbier kirjoitti:
On Wed, Jan 11, 2006 at 04:12:19PM +0200, Martin-Éric Racine wrote:
[...]
(**) Option XkbRules xorg
(**) Generic Keyboard: XkbRules: xorg
(**) Option XkbModel pc105
(**) Generic Keyboard: XkbModel: pc105
(**) Option XkbLayout
On Thu, Jan 12, 2006 at 01:14:35AM +0200, Martin-Éric Racine wrote:
Back to your original report, there is no error in your logs, so X
configuration looks fine. Can you run
setxkbmap -layout fi,ru -variant ,phonetic -option -option
grp:shifts_toggle
in a terminal?
$ setxkbmap -v
Processing commands for [EMAIL PROTECTED]:
reopen 346461
Bug#346461: AllowMouseOpenFail doesn't work with evdev-mouse
Bug reopened, originator not changed.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
to, 2006-01-12 kello 00:38 +0100, Denis Barbier kirjoitti:
On Thu, Jan 12, 2006 at 01:14:35AM +0200, Martin-Éric Racine wrote:
Back to your original report, there is no error in your logs, so X
configuration looks fine. Can you run
setxkbmap -layout fi,ru -variant ,phonetic -option
Package: xserver-xorg
Version: 6.9.0.dfsg.1-3
Severity: important
If Xorg is running, it claims /proc/acpi/events. This causes acpid
to not start:
lapse:~# /usr/sbin/acpid -c /etc/acpi/events -s /var/run/acpid.socket
acpid: can't open /proc/acpi/event: Device or resource busy
Either require
After some hours of research here are my findings:
This issue is tracked at x.org:
https://bugs.freedesktop.org/show_bug.cgi?id=4847
And the cited patch by Benjamin Herrenschmidt fixes the issue for me:
http://lists.freedesktop.org/archives/xorg/2005-December/011678.html
:-)
--
To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, I've been bored and having nothing better to do of late am looking for
ways to help. :-)
Any suggions etc...
- --
Zoe Parsons | skype:mpsonscix
[EMAIL PROTECTED] | http://livejournal.com/~zoep
[EMAIL PROTECTED] | ICQ:97984995
Hey,
Been rejected for employment because you didn't have a qualification?
We have diplomas in all fields, from a accredited university, ready
for delivery within 1 - 2 weeks.
Call me at the number below to discuss our options.
Best Regards,
Clara McCarthy
1-360-272-9646
--
To UNSUBSCRIBE,
Am Mittwoch, 11. Januar 2006 18:33 schrieb Michel Dänzer:
On Wed, 2006-01-11 at 16:58 +0100, Stefan Borggraefe wrote:
$ lsmod | grep -E (drm|agp|radeon)
radeon 97120 1
drm64724 2 radeon
via_agp 9344 1
agpgart31496 2
76 matches
Mail list logo
