Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package xserver-xorg-video-intel
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@list
debian/apport/source_xorg.py |6 ++
debian/changelog |3 ++-
2 files changed, 8 insertions(+), 1 deletion(-)
New commits:
commit 88f086bcfcf2798b39f4866a25af8de294db7339
Author: Bryce Harrington
Date: Mon Mar 9 16:35:43 2009 -0700
Add detection of fglrx module load
#
# bts-link upstream status pull for source package xserver-xorg-video-intel
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #511316
# * https://bugs.freedesktop.org/show_bug.cgi?id=19242
# *
Package: xtrans-dev
Version: 1.2.3-3
The following code (lines 2058-2066 of Xtranssock.c) is wrong:
else if (olderrno == ENOENT || olderrno == ECONNREFUSED) {
/* If opening as abstract socket failed, try again normally */
if (abstract) {
Your message dated Mon, 09 Mar 2009 18:17:03 +
with message-id
and subject line Bug#518909: fixed in compiz 0.7.6-8
has caused the Debian Bug report #518909,
regarding compiz: Fails to build from source: config.status: error:
po/Makefile.in.in was not created by intltoolize.
to be marked as
Your message dated Mon, 09 Mar 2009 18:17:04 +
with message-id
and subject line Bug#518910: fixed in compiz 0.7.6-8
has caused the Debian Bug report #518910,
regarding compiz-gtk: Uninstallable in sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Accepted:
compiz-core_0.7.6-8_amd64.deb
to pool/main/c/compiz/compiz-core_0.7.6-8_amd64.deb
compiz-dev_0.7.6-8_amd64.deb
to pool/main/c/compiz/compiz-dev_0.7.6-8_amd64.deb
compiz-gnome_0.7.6-8_amd64.deb
to pool/main/c/compiz/compiz-gnome_0.7.6-8_amd64.deb
compiz-gtk_0.7.6-8_amd64.deb
to po
compiz_0.7.6-8_amd64.changes uploaded successfully to localhost
along with the files:
compiz_0.7.6-8.dsc
compiz_0.7.6-8.diff.gz
compiz_0.7.6-8_all.deb
compiz-core_0.7.6-8_amd64.deb
compiz-dev_0.7.6-8_amd64.deb
compiz-gtk_0.7.6-8_amd64.deb
compiz-kde_0.7.6-8_amd64.deb
compiz-gnome_0.
Tag 'compiz-0.7.6-8' created by Julien Cristau at
2009-03-09 17:48 +
Tagging upload of compiz 0.7.6-8 to unstable.
Changes since compiz-0.7.6-7:
Julien Cristau (1):
Fix FTBFS and build against new metacity
---
debian/changelog |8
debian/rules |8 +---
2 fil
debian/changelog |8
debian/rules |8 +---
2 files changed, 13 insertions(+), 3 deletions(-)
New commits:
commit 5e876dc6f16d9c053191625c84b39233cb3c046e
Author: Julien Cristau
Date: Mon Mar 9 18:18:58 2009 +0100
Fix FTBFS and build against new metacity
*
Your message dated Mon, 09 Mar 2009 17:03:08 +0100
with message-id <1236614588.7243.2.ca...@radis.liafa.jussieu.fr>
and subject line fixed in libX11 1.2
has caused the Debian Bug report #511178,
regarding [libxcb] ekiga does not start. it waits for FUTEX_WAIT_PRIVATE
to be marked as done.
This me
Your message dated Mon, 09 Mar 2009 17:03:08 +0100
with message-id <1236614588.7243.2.ca...@radis.liafa.jussieu.fr>
and subject line fixed in libX11 1.2
has caused the Debian Bug report #511178,
regarding ekiga hangs on startup
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 09 Mar 2009 17:03:08 +0100
with message-id <1236614588.7243.2.ca...@radis.liafa.jussieu.fr>
and subject line fixed in libX11 1.2
has caused the Debian Bug report #511178,
regarding openoffice.org-gtk: Freezes consistently at opening
to be marked as done.
This means that yo
Accepted:
libx11-6-dbg_1.2-1_amd64.deb
to pool/main/libx/libx11/libx11-6-dbg_1.2-1_amd64.deb
libx11-6_1.2-1_amd64.deb
to pool/main/libx/libx11/libx11-6_1.2-1_amd64.deb
libx11-data_1.2-1_all.deb
to pool/main/libx/libx11/libx11-data_1.2-1_all.deb
libx11-dev_1.2-1_amd64.deb
to pool/main/libx/
libx11_1.2-1_amd64.changes uploaded successfully to localhost
along with the files:
libx11_1.2-1.dsc
libx11_1.2.orig.tar.gz
libx11_1.2-1.diff.gz
libx11-data_1.2-1_all.deb
libx11-6_1.2-1_amd64.deb
libx11-6-dbg_1.2-1_amd64.deb
libx11-dev_1.2-1_amd64.deb
libx11-xcb1_1.2-1_amd64.deb
l
Tag 'libx11-2_1.2-1' created by Julien Cristau at
2009-03-09 15:49 +
Tagging upload of libx11 2:1.2-1 to unstable.
Changes since libx11-2_1.1.99.2-1:
Adam Jackson (1):
Fix leak in _XimXGetReadData
Alan Coopersmith (1):
Add README with pointers to mailing list, bugzilla & git re
debian/changelog |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit d2d17ca22e64a623af880680566b375e9126b369
Author: Julien Cristau
Date: Mon Mar 9 16:36:38 2009 +0100
Prepare changelog for upload
diff --git a/debian/changelog b/debian/changelog
index a06a84
Package: xserver-xorg-video-intel
Version: 2:2.6.1-1
Severity: serious
The X server segfaults when exiting, before it restores the keyboard and
monitor to a usable state. Log attached.
-- Package-specific info:
Contents of /var/lib/x11/X.roster:
xserver-xorg
/var/lib/x11/X.md5sum does not exist.
Processing commands for cont...@bugs.debian.org:
> severity 518953 important
Bug#518953: xserver-xorg-video-intel: Signal 11 when x server exits
Severity set to `important' from `serious'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking s
On Mon, Mar 9, 2009 at 6:02 AM, Julien Cristau wrote:
> Sounds like RAW mode isn't being set on the console... Probably because
> you're not using the kbd driver, and disabling AllowEmptyInput. This
> isn't really a supported configuration.
I can confirm that reenabling AllowEmptyInput solves
On Mon, Mar 9, 2009 at 4:31 AM, Julien Cristau wrote:
> Your config disables AllowEmptyInput but leaves AutoAddDevices and
> AutoEnableDevices on, so you get both kbd and evdev devices for your
> keyboard. Either leave AllowEmptyInput enabled, or disable
> AutoAddDevices. If you still have this
Brice Goglin wrote:
> Now it would be nice to try with mesa 7.3 (currently in experimental).
I've been able to install mesa from experimental (packages: libdrm-intel1,
libdrm2, libgl1-mesa-dev, libgl1-mesa-dri, libgl1-mesa-glx, mesa-common-dev) in
a Lenny live cd environment. The bug still shows
debian/changelog |1
debian/patches/Turn-on-ModeDebug-by-default.patch | 25 ++
debian/patches/series |1
3 files changed, 27 insertions(+)
New commits:
commit b1b3130502cfa89ea581fa768cdde4ab2e30fa93
Aut
xorg-server_1.4.2-10.lenny1_amd64.changes uploaded successfully to localhost
along with the files:
xorg-server_1.4.2-10.lenny1.dsc
xorg-server_1.4.2-10.lenny1.diff.gz
xprint-common_1.4.2-10.lenny1_all.deb
xserver-xorg-core_1.4.2-10.lenny1_amd64.deb
xserver-xorg-dev_1.4.2-10.lenny1_amd64.d
Rebased ref, commits from common ancestor:
commit 872cd04ea5dbc3c33660abe459a4b14f780371f3
Author: Julien Cristau
Date: Sun Mar 8 22:31:52 2009 +0100
Add an fbdev screen as a fallback on sparc
Because of a bug in our PCI code that got exposed by recent kernels,
we will fail to
Tag 'xorg-server-2_1.4.2-10.lenny1' created by Julien Cristau
at 2009-03-09 10:14 +
Tagging upload of xorg-server 2:1.4.2-10.lenny1 to stable.
Changes since xorg-server-2_1.4.2-10:
Julien Cristau (1):
Add an fbdev screen as a fallback on sparc
---
debian/changelog
On Sun, 2009-03-08 at 23:13 -0400, Andrew Moise wrote:
> When I press Ctrl-C within my X session (for example, to abort a
> program within an xterm), the entire X server shuts down.
> Log and config are attached.
>
Sounds like RAW mode isn't being set on the console... Probably because
you're
This has nothing to do with "xorg", but your Desktop Environment (KDE or
Gnome) or your WindowManager...
There is something wrong with your Key-Bindings.
Thanks, Greetings and nice Day/Evening
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Deb
debian/changelog| 15 +
debian/local/dexconf| 50 -
debian/xserver-xorg.postinst.in | 395 ++--
debian/xserver-xorg.templates | 139 --
4 files changed, 45 insertions(+), 554 deletions(-)
New commits:
commit 6
I tried switching to the Nouveau driver to work around this issue, but it
resulted in a kernel hang within a few minutes of starting an X desktop.
I know that's a separate bug; I'm mentioning it here to clarify that it didn't
succeed as a work-around.
--
To UNSUBSCRIBE, email to debian-x-requ
On Sun, 2009-03-08 at 23:33 -0400, Andrew Moise wrote:
> My X keyboard doesn't work very well at all -- each keypress repeats
> 2-3 times, generally with the middle keypress shifted. Most things
> aren't usable. I don't believe I've done any special repeat-rate
> configuration or anything. I've
31 matches
Mail list logo