Your message dated Thu, 27 Apr 2006 11:38:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363559: xserver-xorg-video-ati: Thanks!
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 Thu, 27 Apr 2006 12:28:52 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364979: libxvmc1: Missing link for shared library
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
...that Big Brother is *watching* you:
[EMAIL PROTECTED]:~$ svn update
Fetching external item into 'debian/xsfbs'
External at revision 1984.
At revision 1984.
:-)
Ender.
--
Buzz Lightyear: You killed my father!
Emperor Zurg: No, Buzz...I am your father.
Your message dated Thu, 27 Apr 2006 13:53:10 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364830: xserver-xorg: Fixed by X11R7
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 no
Package: xserver-xorg-core
Severity: grave
X-Debbugs-Cc: [EMAIL PROTECTED]
When updating xserver-xorg-core I get the following error.
Preconfiguring packages ...
(Reading database ... 128943 files and directories currently installed.)
Unpacking xserver-xorg-core (from .../xserver-xorg-core_1%
3a1
Package: xbase-clients
Version: 6.9.0.dfsg.1-6
Severity: normal
The man page for setxkbmap says "Only one layout is permitted." for
-layout. But /usr/lib/X11/xkb/README.config has examples like: -layout
"us,cz,de". One of them must be wrong.
-- System Information:
Debian Release: testing/unstable
Perhaps I should provide some additional information. I executed the
following apt-get command that led to the error:
[EMAIL PROTECTED] $ apt-get install libqt4-dev xserver-xorg
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
libdrm
Your message dated Thu, 27 Apr 2006 15:41:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing...
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 responsibility to reope
Nope. It doesn't work for me yet. I'll just bypass it in my .xinitrc.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The 'unable to load usable ISO8859 font' problem is not isolated to
xmessage; programs such as xfontsel can't find fonts either.
The funny part is that there are lots of iso8559 fonts available:
$ xlsfonts -fn '-*-*-*-*-*-*-*-*-*-*-*-*-iso8859-*' | wc -l
2918
$ xfontsel -pattern '-*-*-*-*-*-*-*-*
Hire,
i am here sitting in the internet caffe. Found your email and
decided to write. I might be coming to your place in! 14 days,
so I decided to email you. May be we can meet? aI am 25 y.o.
a
girl. I have a picture if you want. No need !to reply here as
this is not my email. Write me at [EMAIL
On Die, 2006-04-25 at 19:10 -0700, Josh Triplett wrote:
>
> Robert Hart wrote:
> > Since upgrading to 7.0 I've noticed a problem with the contents of any
> > GL viewport shifting roughly half the viewport width to the left. This
> > seems to occur when some other window partially overlaps and obs
Package: xcursor-themes
Version: 1.0.1-4
Severity: wishlist
There should be information in /usr/share/doc/xcursor-themes describing
how to use these.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /b
On Die, 2006-04-25 at 23:24 +0100, Regis Boudin wrote:
> Ok, si this bug is now starting to turn me crazy.
>
> All running tests point to a problem with Mesa :
> -crash with Mesa in software mode
You mean the X error from the original report? Did you find out which
extension generates it using
* Tore Anderson
> I will try downgrading my kernel now and see if it still happens.
Yep, it did, using 2.6.15-1-k7. I ran that kernel for a long time
with X11R6 on top and didn't have any problems at all, so it seems
very unlikely that the kernel is to blame.
--
Tore Anderson
--
To UN
Package: xkb-data
Version: 0.8-5
Severity: normal
Hello,
I do a dist-upgrade everyday, and before this one:
[REMOVE, NOT USED] libresmgr1
[REMOVE, NOT USED] resmgr
[INSTALL, DEPENDENCIES] xkb-data
[UPGRADE] info 4.8-8 -> 4.8.dfsg.1-1
[UPGRADE] liblcms1 1.13-1 -> 1.15-1
[UPGRADE] liblcms1-dev 1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
After some investigation, I found that some of my xorg packages where
improperly upgraded (don't ask me why). After some tweaking with
apt-get, I could finally upgraded everything, and now it works fine.
Sorry for the improper bug report.
Hi,
OK, sorry for filing a duplicate bug.
The solution: downgrade libxklavier10 to 2.2-1.
See bugs: 364838 and 364830
I think this bug should be reassigned to libxklavier10 (or X) and could
be merged with the above bugs. I'll leave that up to the maintainer (I
haven't got much experience wit
Package: xdm
Version: 1:1.0.1-6
Followup-For: Bug #113542
The path according to /etc/X11/Xservers is /usr/bin/X. According to the debconf
information, the name of the daemon is
/usr/bin/X11/xdm. None of these locations exist. Without changing these, xdm
can't be started with "/etc/init.d/xdm
s
FYI: The status of the xdm source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 1:1.0.1-6
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more informatio
I had the same problem, it got solved by replacing the font paths in
/etc/X11/xorg.conf; it now reads:
Section "Files"
#FontPath "unix/:7100"# local font server
# if the local font server has problems, we can fall back on these
FontPath"/us
Package: xserver-xorg-video-ati
Version: 1:6.5.8.0-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please package upstream's change log with the driver. This may apply to other
drivers as well.
- -- System Information:
Debian Release: testing/unstable
APT prefers unstable
Author: dnusinow
Date: 2006-04-27 22:06:25 -0400 (Thu, 27 Apr 2006)
New Revision: 1985
Added:
trunk/app/xbase-clients-7.0.0/debian/local/
trunk/app/xbase-clients-7.0.0/debian/local/xserverrc
Removed:
trunk/xserver/xorg-server-1.0.2/debian/local/xserverrc
Modified:
trunk/app/xbase-clien
Author: dnusinow
Date: 2006-04-27 22:13:31 -0400 (Thu, 27 Apr 2006)
New Revision: 1986
Added:
vendor/X11R7/
Removed:
vendor/7.0/
Log:
Rename the current vendor branch to something more appropriate as we move
beyond 7.0
Copied: vendor/X11R7 (from rev 1985, vendor/7.0)
--
To UNSUBSCRIBE,
Author: dnusinow
Date: 2006-04-28 00:09:20 -0400 (Fri, 28 Apr 2006)
New Revision: 1987
Modified:
trunk/debian/xorg/debian/xserver-xorg.postinst.in
Log:
Copy missing line to allow backing up file to work
Modified: trunk/debian/xorg/debian/xserver-xorg.postinst.in
===
Author: dnusinow
Date: 2006-04-28 00:18:07 -0400 (Fri, 28 Apr 2006)
New Revision: 1988
Modified:
trunk/debian/xorg/debian/xserver-xorg.NEWS
Log:
Document corner case. Thanks Steve Langasek.
Modified: trunk/debian/xorg/debian/xserver-xorg.NEWS
===
Author: dnusinow
Date: 2006-04-28 00:30:18 -0400 (Fri, 28 Apr 2006)
New Revision: 1989
Modified:
trunk/debian/xorg/debian/changelog
Log:
Prepare changelog for release
Modified: trunk/debian/xorg/debian/changelog
===
--- trunk/debi
Author: dnusinow
Date: 2006-04-28 00:31:36 -0400 (Fri, 28 Apr 2006)
New Revision: 1990
Added:
tags/debian/xorg/xorg-7.0.15/
Log:
Tag upload of xorg-7.0.15 to unstable
Copied: tags/debian/xorg/xorg-7.0.15 (from rev 1989, trunk/debian/xorg)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
On Thu, Apr 27, 2006 at 09:21:53PM +0200, Daniel Immel wrote:
> Hi, do you know the time when xgl might be availible in debian/sid?
I don't know just yet. Xgl turns out to be fairly problematic for several
reasons:
1) It has yet to actually be released. Every single package that's out
ther
Your message dated Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362894: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363667: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364210: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362894: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364641: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364007: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364642: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363571: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364113: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364475: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364692: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#358692: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364689: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363436: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364056: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362728: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362495: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#357714: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#341003: fixed in xorg 1:7.0.15
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 Thu, 27 Apr 2006 21:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363051: fixed in xorg 1:7.0.15
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 Fri, 28 Apr 2006 07:02:07 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364253: Please close that bug (sorry)
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 n
50 matches
Mail list logo
