Package: xserver-xorg-input-synaptics
Version: 1.8.3-1+b1
Severity: normal
I rebooted today with the touchpad working fine and it came back up with
it messed up (bad accelleration, no tap click). For some reason, X
stopped using the synaptics driver for it and fell back to libinput
instead. Reboot
Cyril Brulebois wrote:
> Michelle Konzack (03/09/2010):
> > I use the ~/.xsession file and it works with XDM, WDM, GDM and KDM.
>
> Joey, does that suit your needs?
.xsession is not used when gnome is the session manager.
--
see shy jo
signature.asc
Description: Digital signature
Package: x11-common
Version: 1:7.5+6
Severity: wishlist
I'm using gdm and gnome, but I would like to be able to run a shell
script as part of session startup, in order to
a) Set environment variables etc.
b) Start a lot of programs that I don't want to have to manually
configure gnome to start
Package: xserver-xorg-video-intel
Version: 2:2.9.1-4
Severity: normal
With this version and also experimental 2:2.11.0-1, on not one, but
*two* Dell Mini 9 laptops, I have started seeing multiple types of
screen corruption.
* Twice, a blue screen of death, that appeared without warning while
I
Cyril Brulebois wrote:
> I fear the following message didn't reach you. Could you please tell
> us what the situation currently is?
I have not seen these weird problems in some time.
When using current unstable xorg and 2.6.32, I do get the problem where
sometimes the screen just goes black. IIRC
reassign 556261 acpid
tag 556261 patch
thanks
I've isolated this bug to acpid 1.0.10-3. After downgrading to 1.0.10-2,
I no longer see the problem. Pressing the video switch key now causes the
screen to flicker exactly once, not an infinite number of times. Thank
goodness!
I will try to bisect th
This is actually triggered by accidentially pressing the display switch
button.
Also, if I do that w/o X running, I get a repeated sequence of ^...@^@^@
output to the console, that does not stop. So this may be a hardware
problem.
--
see shy jo
signature.asc
Description: Digital signature
Theppitak Karoonboonyanan wrote:
> The latter choice would be too complicated if the font package ships more
> than one alias file. So, I take the former.
>
> debhelper patch looks cleaner, and I hope the added options are OK for
> xfonts-utils.
This patch is fine by me for debhelper; of course
Theppitak Karoonboonyanan wrote:
> + push @alias_postinst, "\tsed -i
> \',/etc/X11/fonts/$f/$package.alias,d\' $alias_exclude";
> + push @alias_postrm, "\tsed -i
> \',/etc/X11/fonts/$f/$package.alias,d\' $alias_exclude";
I h
Package: xserver-xorg-video-intel
Version: 2:2.7.1-1
Severity: important
I tried upgrading again from the testing version after seeing
hangs with the unstable version this spring and using the testing
version of X to avoid them. But within days I was experiencing
similar symptoms to those reported
Julien Cristau wrote:
> Does it happen reproducibly on a particular web page?
No.
> Versions of xserver-xorg-core, xserver-xorg-video-intel and kernel?
2:1.6.1.901-2. 2:2.7.1-1, 2.6.29-5
--
see shy jo
signature.asc
Description: Digital signature
I've also been getting freezes of X where the cursor still
works. It **always** happens to me when iceweasel is loading
a new web page. I had one last night, one this afternoon,
and before that it had been I think 20 days since the last one.
I was able to ssh in, but stopping gdm did not stop X,
a
Package: xvfb
Version: 2:1.6.1-1
Severity: normal
The man page for xvfb-run contains at least one typo of the command name
as "xfvb-run"
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel
Josselin Mouette wrote:
> Since X did not report correct keysyms until recently, the default keys
> for some shortcuts used to be overridden in GNOME. The problem should be
> fixed by this upload:
>
> control-center (1:2.24.0.1-3) unstable; urgency=low
> .
>* capplets-data.gconf-defaults: rem
Package: xorg
Version: 1:7.4+1
Severity: normal
Apologies for the innaccurate choice of packages, but I'm pretty sure
this problem was caused by my upgrade from xorg 7.3 to 7.4 in general,
though it might turn out to be a gnome bug somehow.
After this upgrade, I noticed two weird things about the
If upstream is really going to disable tapping by default, and Debian is
not going to see fit to override them, then at the very least
this needs to be well documented in the NEWS file.
It's very disconcerting to have tapping just stop working after
an upgrade, as happened to me today (to 1.1.0-1)
Package: xserver-xorg-input-synaptics
Version: 0.14.7~git20070706-2.1
Severity: normal
Trying to follow README.Debian to make the necessary changes to the
xorg.conf of a freshly installed system is a harder than it should
be. (Of course, it shouldn't be necessary at all, but that's bug
#486524.)
I've been using xdm and qemu for ages w/o problems, but today I began
seeing this bug when using qemu.
[EMAIL PROTECTED]:~>qemu -boot a -fda boot_70.img -fdb root.img
XDM authorization key matches an existing client!Could not initialize SDL -
exiting
ii libx11-6 2:1.1.4-2 X11 client-
# Automatically generated email from bts, devscripts version 2.10.28
reassign 483618 xserver-xorg
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I've been using version 2:2.2.99.902-1 since April 1st, with no crashes.
--
see shy jo
signature.asc
Description: Digital signature
Package: xserver-xorg-video-intel
Version: 2:2.2.1-1
I've been seeing this crash for a month or so too. Unlike the original
reporter, I don't think I just see it when mplayer switches to full
screen mode. I've seen mplayer crash X the same way when just starting
up in a window.
I probably see the
Julien Cristau wrote:
> I don't see this anymore with 1:1.1.6-4. Do you still see this bug?
I don't see the bevel problem anymore.
--
see shy jo
signature.asc
Description: Digital signature
Thomas Dickey wrote:
> If I add these lines to the "XTerm" resources that you supplied:
>
> *VT100.utf8Fonts.boldFont: 9x15
> *XTerm*VT100.utf8Fonts.boldFont:9x15
> That should be enough - however in testing this, I see a code change needed
> to make this path work properly:
>
> dif
Thomas Dickey wrote:
> I'm puzzled, since the boldMode/alwaysBoldMode resources do produce the
> result that I tabulated in the manpage.
>
> However, since you're not seeing it work, it's likely that I'm not using
> the same resource-settings and/or locale.
>
> "appres XTerm" and "appres UXTerm"
Updated patch for version 232 is attached.
(Not sure why but the xtermCloseFont line, which is identical to that in
the preceeding code block, now causes a BadFont error. So I commented it
out.
--
see shy jo
diff -ur old/xterm-232/fontutils.c xterm-232/fontutils.c
--- old/xterm-232/fontutils.c 2
Julien Cristau wrote:
> On Sat, Feb 9, 2008 at 19:48:01 -0500, Joey Hess wrote:
>
> > I'm getting tired of having to build my own xterm for over a year..
> >
> The fix wasn't reverted, it was modified in 225 with the addition of the
> "alwaysBoldMode"
I'm getting tired of having to build my own xterm for over a year..
--
see shy jo
signature.asc
Description: Digital signature
Package: xterm
Version: 231-2boldmode1
Severity: normal
Tags: patch
Unlike most XSF maintained packages, this one is missing Vcs fields.
From 65828168ef5c88a337895338aee2ed602a5a785e Mon Sep 17 00:00:00 2001
From: Joey Hess <[EMAIL PROTECTED]>
Date: Sat, 9 Feb 2008 19:39:39 -0500
Subject:
Package: xterm
Version: 231-2
Severity: normal
xterm has grown a cursor hiding feature. It has much to learn from
unclutter IMHO, including:
* unclutter exists. Why bloat the RSS of every individual X program with
their own cursor hiding code?
* Turning the cursor into a black dot is not a very
Thomas Dickey:
> http://vt100.net/docs/vt220-rm/chapter4.html#S4.6.14
(It's helpful to cc the bug sumbitter if you want them to see your
comments.)
Well, I've learned something about vt100 terminals. Namely, that I want
a terminal emulator that emulates something else, since that behavior is
insa
I was asked to follow up on this. On my laptop, I'm using version
2:2.1.1-4 and xbacklight works ok.
--
see shy jo
signature.asc
Description: Digital signature
Package: xterm
Version: 229-1
Severity: normal
In an 80 column xterm, run this command:
perl -e 'print "LABEL=kodama-root
/\t\text3\tnoatime,user_xattr,errors=remount-ro 00\t1\n"'
The output is displayed like this:
LABEL=kodama-root / ext3noatime,user_xattr,errors=remount-ro 001
Brice Goglin wrote:
> A different backlight regression has been reported in 2.1.1
> https://bugs.freedesktop.org/show_bug.cgi?id=11527
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438969
I'm seeing similar behavior to those with 2.1.0, but only if I use the
bios-controlled backlight
Package: xdm
Version: 1:1.1.5-2
Severity: minor
The xdm greeter window is quite a bit larger now than it used to be.
This might relate to a display glitch. Along the bottom of the window,
there is a bevel. About 3/4 of the way across, the bevel is gone, and I
think it just displays flat grey inste
I don't understand why xserver-xorg
Depends: xserver-xorg-input-all | xserver-xorg-input
Recommends: xserver-xorg-video-all
The Depends seems to handle all the cases. If you install xserver-xorg
plus a specific xserver-xorg-input-*, the -all package is skipped.
Otherwise it's installed by defaul
reopen 347790
thanks
Guess I need to reopen this, the bts still has it marked as fixed
despite the fix having been reverted.
--
see shy jo
signature.asc
Description: Digital signature
Brice Goglin wrote:
> Hi Joey,
>
> Could you try the latest xserver-xorg-video-intel package (2:2.0.0-5
> currently in experimental) and report back whether it fixes this crash
> in xgalaga?
It's hard for me to say, since as noted I've only e
Brice Goglin wrote:
> I can't reproduce this crash with latest xserver-xorg-video-intel
> currently in experimental (2:2.0.0-4). I think I tried in the right
> conditions as explained earlier (16bits depth and so). Could you confirm?
I'm not seeing it with an X server built from sources keithp gav
Joey Hess wrote:
> I've found a fairly reliable way to reproduce this, I think. If I start
> a movie in mplayer, pause it, suspend, resume, suspend, and resume
> again, it seems to crash on that second resume (it crash on resume 50%
> of the time or so).
Confirmed, and it'
I've found a fairly reliable way to reproduce this, I think. If I start
a movie in mplayer, pause it, suspend, resume, suspend, and resume
again, it seems to crash on that second resume (it crash on resume 50%
of the time or so).
--
see shy jo
signature.asc
Description: Digital signature
Steinar H. Gunderson:
> I've talked to the X maintainers, and been told that the patch for
> #381952 (laptop multimedia key detection) will go into experimental
> quite soon, and possibly from there to unstable if the results are good.
That was last August, is this bug being worked on?
--
see sh
Drew Parsons wrote:
> Joey wrote:
> > This is the second regular X app I've seen crash the X server, this time
> > it's xgalaga, which crashed it once when it was starting up in
> > fullscreen mode, which switches to a smaller video mode.
>
>
> Confirmed, crashes hard every time for me. Crashes
Brice Goglin wrote:
> Joey Hess wrote:
> > I do have a useful bit of info though. The crash only happens with my
> > old xorg.conf. I let a new one be generated, and blobwars runs ok.
> >
> > The relevant change seems to be running at 24 bpp. If I switch it back
> >
Raúl Sánchez Siles wrote:
> That backtrace doesn't seem very meaningful, maybe using a core dump
> backtrace would be better.
How could a core dump backtrace be different or better?
It seems pretty clear that it's jumping the the xf86SigHandler and
losing all prior stack info before that.
I do
Julien Cristau wrote:
> > > Backtrace:
> > > 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c20e4]
> > > 1: /lib/i686/cmov/libc.so.6 [0xb7d23828]
> > > 2: [0x49004900]
> > >
> > could you install the xserver-xorg-core package and try to either get a
> ^
> I meant
Package: xserver-xorg-video-intel
Version: 2:2.0.0-1
Severity: important
I can crash X by just running blobwars (1.06-2-1). This was not the case
with the old version of the X server.
This is what shows up in the log after I start blobwars. Then xdm restarts.
Backtrace:
0: /usr/bin/X(xf86SigHand
#418256 is similar to #420400, in workaround if not cause/symptoms. To
work around that bug, I came up with a hibernate patch that provides a
SwitchToTextModeOnResume option. The patch is in bug #420401.
--
see shy jo
signature.asc
Description: Digital signature
Package: xdm
Version: 1:1.1.4-3
Severity: normal
If I ctrl-alt-backspace in X, xdm is restarted, and must be running at a
different pid than what the init script expects, since /etc/init.d/xdm
stop fails to stop it.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT pol
Julien Cristau wrote:
> close 419143 1:1.1.4-1
> forcemerge 335388 419143
> thanks
> Already fixed :)
No, I'm not talking about the lsb comments, which are there.
I'm asking for it to use log_daemon_msg, log_end_msg, etc from
/lib/lsb/init-functions.
--
see shy jo
signature.asc
Description:
found 347790 225-1
thanks
Due to the boldmode patch being aparently reverted in version 225-1,
this bug has resurfaced. Using 225-1, I cannot disable bold mode again.
My configuration remains as documented in this bug report.
--
see shy jo
signature.asc
Description: Digital signature
Julien Cristau wrote:
> On Fri, Apr 13, 2007 at 18:49:59 -0400, Joey Hess wrote:
>
> > Package: xterm
> > Version: 1:222-1
>
> There is no such version of xterm, etch has 222-1etch2 (without the
> epoch), lenny and sid have 225-1.
>
> > Severity: normal
&g
Package: xterm
Version: 1:222-1
Severity: normal
If I have x-terminal-emulator set to gnome-terminal, the
x-terminal-emulator man page works. If I then use update-alternatives
--config to set it to xterm, the link is broken:
[EMAIL PROTECTED]:/usr/share/man/man1>man x-terminal-emulator
man: warni
Package: xterm
Version: 1:222-1
Severity: normal
/etc/init.d/xterm doesn't use lsb init functions, and so it's one of the
few scripts left in my startup sequence whose output can't be understood
by usplash, etc.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy:
Brice Goglin wrote:
> About 6 years ago, you reported a bug to the Debian BTS regarding xdm
> generating garbage files if interrupted while generating auth token. Did
> you reproduce this problem recently? With Xorg/Etch? If not, I will
> close this bug in the next weeks.
This would be difficult t
Brice Goglin wrote:
> About 9 years ago, you reported a bug to the Debian BTS regarding
> localhost appearing in chooser when route is -net 127.0.0.0. You didn't
> reply to Branden's ping 7 years ago. But you change the submitter's
> address later.
> So, did you reproduce this problem recently? Wit
Julien Cristau wrote:
> Would the following patch fix this for you?
Looks like it would.
--
see shy jo
signature.asc
Description: Digital signature
Package: xdm
Version: 1:1.0.5-1
Severity: normal
Tags: d-i
I'd like to include xdm in the xfce task, but I can't since it fails as
follows:
Warning: Fake start-stop-daemon called, doing nothing.
cat: /var/run/xdm.pid: No such file or directory
dpkg: error processing xdm (--configure);
subproces
Brice Goglin wrote:
> About 3 years ago, you reported a bug to the Debian BTS regarding
> missing default answers for X configuration questions. Did you reproduce
> this problem recently? If not, I will close this bug in the next weeks.
The only ones that I can find that still seems to be missing
[EMAIL PROTECTED] wrote:
> But when I booted into the new system, X wouldn't com up, and complained
> that it could not load modules 'kbd' or 'mouse' because "module does not
> exist"
>
> starting aptitude and installiny packages
>xserver-xorg-input-kbd
> and
>xserver-xorg-input-mouse
>
Christoph Berg wrote:
> Adding ${misc:Depends} adds the (previously missing) dependency on
> xfonts-utils, but does not make it versioned.
Why does it need to be versioned? There has not been any version of
xfonts-utils that did not support --x11r7-layout.
--
see shy jo
signature.asc
Descripti
Frans Pop wrote:
> Currently the debian-x list is getting heavily spammed with commit mails,
> both from SVN and from git. IMO this is not necessary.
The git ones are especially annoying, since they don't contain any diff
to read. Why get commit mails if there's no diff..
--
see shy jo
signat
Well, I upgraded 222-1 today, and this bug is back for me.
I tried applying the xterm-boldmode-2.patch, and with some updates to
work with changed variables in the new version, it works! I've attached
an updated version of the patch.
Please consider applying this..
--
see shy jo
diff -ur old/xt
Julien Cristau wrote:
> I tried to reproduce this by upgrading xterm from sarge to etch and
> didn't get any dangling symlink. I tried an upgrade with xterm as the
> only x-terminal-emulator package installed, as well as with xterm and
> rxvt, and I also tried setting the link to uxterm manually b
Package: x11-common
Version: 1:7.1.0-5
Severity: normal
The following report is for Ubuntu, not Debian, but the first bug
encountered seems to affect us too: x11-common is missing a conflict on
an opera-static package which at some version installed files in
/usr/X11R6/bin. (Possibly on opera too?
David Nusinow
> Will tasksel still be able to ensure that
> xresprobe and discover are installed prior to the
> scripts being run in this case?
Yes, tasksel can arrange for all necessary hardware detection tools to
be installed by the time the postinst runs. Or you can just depend on
them, your ch
Steve Langasek wrote:
> tags 368582 patch
> tags 384057 patch
> tags 384282 patch
> tags 386185 patch
> tags 369895 patch
> thanks
I think that this NMU will also fix #359328, won't it?
--
see shy jo
signature.asc
Description: Digital signature
David Nusinow wrote:
>I didn't realize that this was a pressing issue.
> Since it worked for sarge, I figured that the kludge
> could remain until we can get a proper solution in
> place.
There have been large changes to the installer since sarge that broke the
old solution.
>My plan for
For years and years, X has had a unique special case: It needs to have
discover1 and some other software (currently also xresprobe[1]) installed
before it is preconfigured. If the software is not installed then X's
config script will silently not use it during hardware detection, and
will do a wors
Drew Parsons wrote:
> Unfortunately it's happened against, this time with the upload of
> xorg-server (xserver-xorg-core) 1:1.1.1-3, accidentally uploaded to
> unstable instead of experimental. An easy enough mistake, it's only
> one little field in a changelog file.
'2:' is not any worse than '1
This bug is annoying, and still open.
/etc/cron.weekly/man-db:
mandb: warning: /usr/share/man/man1/x-terminal-emulator.1.gz is a dangling
symlink
That file points to a /etc/alternatives file that is not there; one with
"1x" in the name is there.
--
see shy jo
signature.asc
Description: Digi
One way to fix this would be to promote apt-listchanges to standard
priority so it's available everywhere and add a NEWS.Debian entry for
the issue.
--
see shy jo
signature.asc
Description: Digital signature
David Nusinow wrote:
> Right, I don't like it but I don't have a clean fix for it yet. The reason
> being that x11-common didn't exist in sarge so I can't simply check for an
> upgrade. Ideally I would look for xserver-common being on the system and
> put the note up in that case, but that package
David Nusinow wrote:
> Ok, this is an extremely troubling bug. The previous x11-common's postinst
> gets called when the new x11-common's postinst fails with the /usr/bin/X11
> switch.
No the problem is not that the new postinst is failing (nor does dpkg do
any error-unwind involving the old posti
Package: x11-common
Version: 1:7.0.20
Severity: wishlist
I have an idea.. why not check early if an X server is installed, then
in the postinst check again and if there's no X server installed
anymore, display an error message about it. It's disconcerting to get
this debconf note displayed during
[EMAIL PROTECTED] wrote:
> Package: x11-common
> Version: 1:7.0.20
> Severity: grave
> X-Debbugs-CC: "Henk Boom" <[EMAIL PROTECTED]>
>
>
> x11-common postinst error: trouble with /usr/include/X11
>
>
> We get this problem on two different systems -- an etch AMD-64 (installed
> as Debian-AMD64,
Package: x11-common
Version: 1:7.0.20
Severity: normal
I have a small apt repository at work containing some third-party
packages that use /usr/X11R6/bin. How am I supposed to provide a clean
upgrade path for my users? If x11-common is upgraded first, it will
flame out and die. But there's no way
Package: x11-common
Version: 1:7.0.20
Severity: normal
_smoking_guns=$(grep -l "$1" $_possible_culprits)
It's possible for this grep to not turn up anything, and if it does, the
postinst will crash here, exiting with 1 and no indication of the problem.
If || true is added to the end, it b
Package: x11-common
Version: 1:7.0.20
Severity: normal
The system I am trying to upgrade has third-party packages that
installed stuff in /usr/X11R6/bin. Since that caused the upgrade to
fail, I have moved everything out of /usr/X11R6/bin and am trying to
pick up the peices.
adsdebian:/usr/lib# l
Dominique Dumont wrote:
> I've upgraded from Xork 6.9 to Xorg 7.0. While updating, aptitude
> insisted on removing xprint. Then xprint-common was removed by
> aptitude as it was no longer used.
>
> Unfortunately, I couldn't get Xorg to start with startx. Long story
> short, I found this error mess
Steve Langasek wrote:
> Hmm, this was supposed to have been fixed in xserver-xorg 1:7.0.11 by
> removing the symlink in question. :/ So there are two bugs here --
> xserver-xorg needs to drop the symlink, and x11-common needs to bump its
> versioned conflict with xserver-xorg...
Just to add to th
Package: x11-common
Version: 1:7.0.11
Severity: serious
Setting up x11-common (7.0.11) ...
rmdir: /usr/X11R6/bin: Directory not empty
x11-common postinst error: Could not remove /usr/X11R6/bin. Is not yet empty
dpkg: error processing x11-common (--configure):
subprocess post-installation script r
Daniel Stone wrote:
> On Fri, Apr 14, 2006 at 10:32:36AM +0200, Joey Hess wrote:
> > This commit seems likely to break upgrades from stable. Nothing will
> > guarantee that x11-common will be upgraded before everything else that
> > uses /usr/X11R6/bin in stable.
>
>
This commit seems likely to break upgrades from stable. Nothing will
guarantee that x11-common will be upgraded before everything else that
uses /usr/X11R6/bin in stable.
X Strike Force SVN Repository Admin wrote:
> Author: dnusinow
> Date: 2006-04-13 20:18:48 -0400 (Thu, 13 Apr 2006)
> New Revisi
I've reopened this bug because xdm 1:1.0.1-5 remains broken exactly as
before; xdm-config refers to a nonexistant Xsetup_0, and if I fix that
xdm still fails on login with this in the log:
error opening security policy file /usr/lib/xserver/SecurityPolicy
(Note: I purged xdm and reinstalled it, t
Somehow, upgrading to modular x.org and to version 210-2 of xterm
fixed this problem for me. I'm leaving the bug open since it has
(unrelated?) patches in it.
--
see shy jo
I've done a minor mass-bug filing (85 bugs) on packages that still use
/usr/X11R6/lib/X11/fonts. I hope that I captured everything that needs to be
done to transition:
* Modify rules or Makefile to install the fonts to the new directory.
* Build-depend on debhelper version 5.0.29, which supports
Package: xfonts-utils
Version: 1:1.0.0-3
Severity: normal
With the fonts dirs moving, a system that is upgraded from an old
version of X will have /usr/X11R6/lib/X11/fonts directories left hanging
around with fonts.dir, fonts.cache-1, fonts.alias, and encodings.dir
left in them. Since these old di
Erm, am I currect that X now only looks for fonts in
/usr/share/fonts/X11/? What is everything that hardcodes
/usr/X11R6/lib/X11/fonts/ (dh_installxfonts, font packages, etc)
supposed to do? Any kind of a transition plan here?
--
see shy jo
Package: xserver-xorg
Version: 1:7.0.10
Severity: normal
On startup, X gives the message given in the subject. This doesn't seem
to keep it from working, but dunno if it's seeing the copy of the file
in /etc.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT pol
Package: debian-policy
Version: 3.6.2.2
Severity: normal
Section 11.8.5. is no longer current regarding the font paths used by
the new modular version of X. Packages providing fonts need to drop them
into /usr/share/fonts/X11/ now, I guess. It would probably help if the X
maintainers sent in a pat
Package: xserver-xorg
Version: 1:7.0.10
Severity: important
I have a custom xorg.conf. On upgrade, X stopped working since all the
paths in it were pointing to stuff in /usr/X11R6/ that doesn't exist
anymore. X should detect this and fix/warn on upgrade.
-- System Information:
Debian Release: tes
Package: xserver-xorg
Version: 1:7.0.10
Severity: normal
lrwxrwxrwx root/root 0 2006-04-11 04:16:27 ./usr/X11R6/bin/X ->
../../bin/X
This is a broken link since /usr/X does not exist..
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'un
Package: x11-common
Version: 1:7.0.10
Severity: normal
Now that /usr/X11R6/bin and /usr/bin/X11 do not point to the same place,
if a system has /usr/bin/X11 in its PATH, it will miss anything left in
/usr/X11R6/bin. This should at least be documented in NEWS.Debian
although it's easy to be bit by
Michel Dänzer wrote:
> On Mon, 2006-04-10 at 12:52 -0400, Joey Hess wrote:
> > This bug has reared its ugly head again for me today, when I rebooted
> > and came up in xserver-xorg 6.9.0.dfsg.1-6. Sigh, I thought it was dead.
> > Installing the -dbg package to work around it a
This bug has reared its ugly head again for me today, when I rebooted
and came up in xserver-xorg 6.9.0.dfsg.1-6. Sigh, I thought it was dead.
Installing the -dbg package to work around it again.
--
see shy jo
signature.asc
Description: Digital signature
It also seems to be ignoring color settings like these:
*XTerm*VT100*color0: black
*XTerm*VT100*color1: red3
*XTerm*VT100*color2: green4
*XTerm*VT100*color3: yellow4
*XTerm*VT100*color4: blue4
*XTerm*VT100*color5: magenta3
*XTerm*VT100*color6: cyan4
*XTerm*VT100*color7: gray55
*XTerm*VT100*color8:
Package: xterm
Version: 208-3.1
Severity: normal
(Hmm, I see I already filed a bug on this once, so I'll just follow up
with this second, more detailed bug report since I typed it up..)
My system was configured via update-alternatives --edit so that xterm
was the alternative used for x-terminal-e
Package: xorg-x11
Severity: normal
Version: 6.9.0.dfsg.1-4
Tags: security
CVE-2006-0197 describes a potential security problem as follows:
The XClientMessageEvent struct used in certain components of X.Org 6.8.2
and earlier, possibly including (1) the X server and (2) Xlib, uses a
"long" sp
David Martínez Moreno wrote:
> What happened about the nasty Transmeta bug with X?
> Did you see any changes with new 6.9 packages and/or gcc-4.0?
I haven't been seeing it with x.org 6.9 packages built with recent
gcc's, but I assume this just means the code has stopped tickling the
underlying bu
Free Ekanayaka wrote:
> I'm wondering if it would make sense to add
>
> xresprobe
> discver
> laptop-detect
>
> to the list of packages which get installed before the X server. As
> far a I know, if available, they are used by the postinst scripts of
> xserver-xorg.
laptop-detect is already
1 - 100 of 217 matches
Mail list logo
