Package: xserver-xorg-video-siliconmotion
Version: 1:1.3.1.5-3
Severity: important
Tags: patch
Hi,
the driver hangs on a Debian/amd64 system with the Silicon Motion
SM720 Lynx3DM (ID 126f:0720) card. I've asked help on the Xorg
mailing list and I got attached patch which fixes the problem:
Ho
Package: xserver-xorg-video-nv
Version: 1:1.2.0-3
Severity: normal
Hi
The nv driver renders thin green vertical stripes approx 6mm apart against a
grey
background with my nvidia 6800 GS (256 MB) card.
Attempting to switch to a vt, results in a black screen. Switching back to vt7
normally re
On Fri, Nov 24, 2006 at 10:47:51PM +0900, Osamu Aoki wrote:
> On Tue, Nov 21, 2006 at 06:26:00PM +0100, Lo?c Minier wrote:
...
> http://people.debian.org/~osamu/public as gedit-logs.tar.gz
Correct URL:
http://people.debian.org/~osamu/pub as gedit-logs.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL
On Tue, Nov 21, 2006 at 06:26:00PM +0100, Lo?c Minier wrote:
...
> Which patches did you apply? Could you please try the attached patches
> which I've extracted from the Fedora SRPM? One looks the same as the
> freedesktop one, the other one seems to flag events appropriately.
Goto-san and I
On Fri, Nov 24, 2006, Osamu Aoki wrote:
> Goto-san and I tried your patch and it did not fix freeze. I upload GDB
> full logs to:
> http://people.debian.org/~osamu/public as gedit-logs.tar.gz
(s/public/pub)
> I used LANG=en_US.UTF-8 LD_LIBRARY_PATH=/usr/lib/debug to ensure English
> message and
On Fri, Nov 24, 2006 at 03:12:20PM +0100, Loïc Minier wrote:
> On Fri, Nov 24, 2006, Osamu Aoki wrote:
> > Goto-san and I tried your patch and it did not fix freeze. I upload GDB
> > full logs to:
> > http://people.debian.org/~osamu/public as gedit-logs.tar.gz
>
> (s/public/pub)
>
> > I used LA
Hi,
I am trying to solve Bug #374640.
You claimed that gcin can use gedit using XIM as imput method instead of
IMMODULE gcin directly. So far I can not reproduce it.
On Sun, Nov 19, 2006 at 12:32:53PM +, caleb wrote:
> Osamu Aoki wrote:
...
>
> > I tested GTK IMMODULE. It looks like worki
Hi,
I thought I got freeze under SCIM(XIM) but now I an not sure.
(My comment on SCIM might have been just explaining what
[EMAIL PROTECTED] reported.)
At least SCIM using XIM as its input mechanism does not freeze gedit now
(using standard libx11-6). I am quite intrigued.
BTS URL: http://bugs
Hi all,
To be honest, I do not know well why my bug report is reassigned and
retitled as freeze when XIM is used to input Japanese text ...
The bug I reported is about the Shift key behavior of SCIM in gedit, and I
did not notice the freezing problem reported by others at all :-)
Maybe is there
Package: xserver-xorg-video-i810
Version: 2:1.7.2-1
Severity: normal
Repeating actions explained on the first comment I can't reproduce this
failure, altough I think I had experienced this before upgrading to xorg
7.0 and/or kernel 2.6.18.
-- System Information:
Debian Release: 4.0
APT prefers
Package: xserver-xorg-video-i810
Version: 2:1.7.2-1
Severity: normal
Repeating actions explained on the first comment I can't reproduce this
failure, altough I think I had experienced this before upgrading to xorg
7.0 and/or kernel 2.6.18.
-- System Information:
Debian Release: 4.0
APT prefers
Reviewing the upstream report, it seems this bug is solved on the git
repository.
--
Raúl Sánchez Siles
->Proud Debian user<-
Linux registered user #416098
pgpM1Vc4wGnCg.pgp
Description: PGP signature
Package: xserver-xorg-video-i810
Version: 2:1.7.2-1
Severity: normal
Repeating actions explained on the first comment I can't reproduce this
failure, altough I think I had experienced this before upgrading to xorg
7.0 and/or kernel 2.6.18.
-- System Information:
Debian Release: 4.0
APT prefers
Processing commands for [EMAIL PROTECTED]:
> close 400272
Bug#400272: xserver-xorg-video-i810: I don't experience this problem.
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Raúl Sánchez Siles <[EMAIL
PROTECTED]>
> --
Stop
Package: xserver-xorg-video-i810
Version: 2:1.7.2-1
Severity: normal
Could you provide a way to reproduce this?. Also if you are using
frambuffer at console, the xorg.conf file and the kernel you are using.
This is not happenning to me with an i855GM card. Please report your bug
with reportb
Author: dnusinow
Date: 2006-11-24 16:47:10 -0500 (Fri, 24 Nov 2006)
New Revision: 4045
Modified:
trunk/xserver/xorg-server/debian/changelog
Log:
Prepare changelog for upload
Modified: trunk/xserver/xorg-server/debian/changelog
==
Author: dnusinow
Date: 2006-11-24 16:52:42 -0500 (Fri, 24 Nov 2006)
New Revision: 4046
Added:
tags/xserver/xorg-server/xorg-server-2:1.1.1-11/
Log:
Tagging upload of xorg-server-2:1.1.1-11 to unstable.
Copied: tags/xserver/xorg-server/xorg-server-2:1.1.1-11 (from rev 4045,
trunk/xserver/xorg-
Processing commands for [EMAIL PROTECTED]:
> tags 377386 patch
Bug#377386: xserver-xorg-video-s3: s3 driver does not work after upgrade to 7.0
There were no tags set.
Bug#399735: s3_drv.so: undefined symbol: S3AccelInitPIO
Tags added: patch
> retitle 377386 s3 driver does not work after upgrade t
Sorry for my previous dirty hack for Makefile.am. My previous message
should be ignored. Now I present new correct version of patch. It also
possibly closes bug #377386 which was merged with this bug.
Infomation for maintainer. This patch replaces(!!!) my previous patch
01_enable_new_mmio.diff. I
Your message dated Fri, 24 Nov 2006 23:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356300: fixed in xorg-server 2:1.1.1-11
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
Your message dated Fri, 24 Nov 2006 23:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337703: fixed in xorg-server 2:1.1.1-11
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
Your message dated Fri, 24 Nov 2006 23:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#395564: fixed in xorg-server 2:1.1.1-11
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
Your message dated Fri, 24 Nov 2006 23:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#358015: fixed in xorg-server 2:1.1.1-11
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
Your message dated Fri, 24 Nov 2006 23:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393991: fixed in xorg-server 2:1.1.1-11
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
Your message dated Fri, 24 Nov 2006 23:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356300: fixed in xorg-server 2:1.1.1-11
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
Your message dated Fri, 24 Nov 2006 23:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#392453: fixed in xorg-server 2:1.1.1-11
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
Your message dated Fri, 24 Nov 2006 23:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#291100: fixed in xorg-server 2:1.1.1-11
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
Your message dated Fri, 24 Nov 2006 23:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#308899: fixed in xorg-server 2:1.1.1-11
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
Your message dated Fri, 24 Nov 2006 23:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364556: fixed in xorg-server 2:1.1.1-11
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
Package: xserver-xorg-video-savage
Version: 1:2.1.2-1
Followup-For: Bug #393266
lspci -v reports:
01:00.0 VGA compatible controller: S3 Inc. SuperSavage IX/C SDR (rev 05)
(prog-if 00 [VGA])
Subsystem: IBM ThinkPad T23 (2647-4MG)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWI
Author: jamey
Date: 2006-11-24 20:14:26 -0500 (Fri, 24 Nov 2006)
New Revision: 4047
Added:
branches/experimental/lib/libx11/
Log:
Create an experimental branch for libx11 1.1 with Xlib/XCB.
Copied: branches/experimental/lib/libx11 (from rev 4046, trunk/lib/libx11)
--
To UNSUBSCRIBE, email
Author: julien
Date: 2006-11-25 00:06:54 -0500 (Sat, 25 Nov 2006)
New Revision: 4048
Removed:
trunk/lib/libx11/debian/libx11-6.postrm.in
Modified:
trunk/lib/libx11/debian/changelog
trunk/lib/libx11/debian/libx11-6.postinst.in
Log:
* Replace call to register_x_lib_dir_with_ld_so in postins
On Sat, Nov 25, 2006 at 02:30:03AM +0800, Hongzheng Wang wrote:
> Hi all,
>
> To be honest, I do not know well why my bug report is reassigned and
> retitled as freeze when XIM is used to input Japanese text ...
>
> The bug I reported is about the Shift key behavior of SCIM in gedit, and I
> did
33 matches
Mail list logo
