Bug#174260: [jidanni@dman.ddts.net: Bug#174260: xbase-clients: no xmessage --help, --version]
>BTW, how in the world is one to tell the version of xmessage in a >formal way on debian then? One sees some note of it in the man page >trailers, but that is not a formal way. Other than just looking at the version tag, apparently? $ xmessage usage: xmessage [-options] [message ...] where options include: -file filename file to read message from, "-" for stdin -buttons string comma-separated list of label:exitcode -default button button to activate if Return is pressed -print print the button label when selected -center pop up at center of screen -nearmouse pop up near the mouse cursor -timeout secs exit with status 0 after "secs" seconds XConsortium: xmessage.c,v 1.6 95/01/04 16:29:54 gildea Exp $ Seems pretty explicit to me. :) -- Marc Wilson | Once a woman has given you her heart you can never [EMAIL PROTECTED] | get rid of the rest of her. -- Vanbrugh
Bug#165416: xfree86: no warning of meta/alt/windows key behavior change
On Fri, Oct 18, 2002 at 02:58:48PM -0700, David Parker wrote: > After reading the changelogs I figured out that I had to add the > following to my XF86Config-4 file: > > Option "XkbOptions""altwin:meta_win" > > There was no warning of this change, and for a long time I was > unable to fix the problem. I'm sure Branden will be considerably more caustic, but the best possible answer would be... whyinhell hadn't you read the changelog in the first place, where this is explicitly described? This *is* unstable, after all. You really gotta love the way people think nowadays... oh, no, I don't see any reason why I should look at a changelog and find out what changed in package "X"... I'll decide the KERNEL, which hasn't changed, must suddenly be at fault. Sheesh. > I think that if this setting isn't added automatically to the user's > config file, it should at least be documented in README.Debian and > displayed in a dialog before the package is installed. For every person that expects that ALT is ALT and Windows is META, there's another person who expects that ALT is META and is going to lame about how you've broken their copy of emacs. Don't gratuitously add options to configuration files. -- Marc Wilson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#166497: x-window-system: should depend on x-display-manager instead of xdm
On Sat, Oct 26, 2002 at 11:32:11AM -0700, Agthorr wrote: > Package: x-window-system > Version: 4.1.0-16 > Severity: normal > > The x-window-system should depend on x-display-manager (provided by > xdm, gdm, kdm, and wdm) instead of on xdm. How is this anything more than a wishlist bug? What's going to win if NOTHING is installed, which is when people are going to be installing x-window-system in the first place. Xdm is the XFree-provided display manager. Install another if you want another. All the display managers can co-exist. -- Marc Wilson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#166413: mga driver doesn't set gamma on second screen
On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote: > 2) It is possible that this is a hardware limitation. Multiple-output > video cards often don't support all features on secondary "heads". I always had the problem with my G450 and later with my G550 that X wouldn't set the gamma the same on both heads, although it claimed that it was according to the log. The monitors were the same make and model, and the difference was distinct and annoying. OTOH, xgamma was always quite willing to set the gamma on the heads separately, and I was also able to specify specific gamma settings for each monitor in XF86Config-4 and have them take effect. > [I'd appreciate feedback from Matrox users on the debian-x list so I > know whether I'm right about 2) or not.] Hope that helps. -- Marc Wilson [EMAIL PROTECTED] msg04417/pgp0.pgp Description: PGP signature
Bug#166413: mga driver doesn't set gamma on second screen
On Sun, Oct 27, 2002 at 11:14:37PM -0500, [EMAIL PROTECTED] wrote: > On Sun, Oct 27, 2002 at 07:07:15PM -0800, Marc Wilson wrote: > > I always had the problem with my G450 and later with my G550 that X > > wouldn't set the gamma the same on both heads, although it claimed that it > > was according to the log. The monitors were the same make and model, and > > the difference was distinct and annoying. > > > > OTOH, xgamma was always quite willing to set the gamma on the heads > > separately, and I was also able to specify specific gamma settings for each > > monitor in XF86Config-4 and have them take effect. > > In that case I'm confused. Has there been a regression since XFree86 > 4.1 or not? I should clarify... When I was still using the G450/G550, X would claim that it was setting the gamma on the two monitors identically. Anyone who looked at them, though, would be able to tell that they were wildly different. I used xgamma (at first) in $HOME/.xsession, and later manipulating XF86Config-4 directly, to reduce the gamma on the second monitor, like so: Section "Monitor" Identifier "Viewsonic PF790" HorizSync 30-97 VertRefresh 50-180 Option "DPMS" "Yes" Gamma 0.8 0.8 1.15 EndSection This was the only way I could make the two of them balance. I always chalked it up to just hardware differences in the respective video outputs (ie they had different ideas of what gamma 1.0 meant) and got on with things. I haven't run either of my Matrox cards on XF 4.2.x... it's a nVidia world in my box now (I wouldn't have, but they were free). Sorry for any confusion I may have introduced. I think I was trying to point out that even though they weren't being set the same (and X claimed they were), there was still individual control on both heads. -- Marc Wilson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#174260: [jidanni@dman.ddts.net: Bug#174260: xbase-clients: no xmessage --help, --version]
>BTW, how in the world is one to tell the version of xmessage in a >formal way on debian then? One sees some note of it in the man page >trailers, but that is not a formal way. Other than just looking at the version tag, apparently? $ xmessage usage: xmessage [-options] [message ...] where options include: -file filename file to read message from, "-" for stdin -buttons string comma-separated list of label:exitcode -default button button to activate if Return is pressed -print print the button label when selected -center pop up at center of screen -nearmouse pop up near the mouse cursor -timeout secs exit with status 0 after "secs" seconds XConsortium: xmessage.c,v 1.6 95/01/04 16:29:54 gildea Exp $ Seems pretty explicit to me. :) -- Marc Wilson | Once a woman has given you her heart you can never [EMAIL PROTECTED] | get rid of the rest of her. -- Vanbrugh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xprt-xprintorg taking over xprt: now or later?
On Tue, Dec 07, 2004 at 11:09:31AM +1100, Drew Parsons wrote: > I guess we can do it now. xprt (xfree86) does not work and Fabio was > already prepared to remove it now before sarge. Of course, neither does xprt-xprintorg, but that's a minor quibble. :) Does *anything* besides Mozilla care about whether or not it exists? From a user's perspective, I can't imagine that it's at all important to replace the one with the other for Sarge. Checking reverse depends... no, nothing other than Mozilla and friends deps on it, and they don't even dep on it, they only recommend it. So who cares, really? Packages that want it, will already bring it in. > Also, I have a prerelease upstream version of Xprint (1.0alpha1), based > on X.org 6.8.2. Roland upstream recommends we put it into sarge, it has > considerable improvements over the current Xprint. Oh, you mean that this one actually works correctly? -- Marc Wilson | Kissing your hand may make you feel very good, [EMAIL PROTECTED] | but a diamond and sapphire bracelet lasts for ever. | -- Anita Loos, "Gentlemen Prefer Blondes"
Re: xprt-xprintorg taking over xprt: now or later?
On Tue, Dec 07, 2004 at 11:03:25AM +0300, Nikita V. Youshchenko wrote: > Tried ever to print non iso8859-1 characters from mozilla? > It isn't impossible without xprt, but it is really hacky ... I will *freely* admit to my North American English bias. I will *also* freely admit to my bias towards having a working ability to create usable printed copies of the majority of web pages found today, which Mozilla can usually do on its own and Xprint (either version) most certainly CAN NOT without hackery that Joe User is not capable of and should not be expected to be capable of. My gods, the thing thinks it needs to know the output resolution of the printer! Otherwise you end up with endless stupidities like the problems that were showing up while the Mozilla maintainer was temporarily insane and requiring Xprint. Search the d-u archives for endless descriptions of Xprint producing huge print, or print that won't fill the page, among other things. Postscript exists for a *reason*... we don't need yet another device-dependent and incompatible way to lay out a page. -- Marc Wilson | A song in time is worth a dime. [EMAIL PROTECTED] |
Re: xprt-xprintorg taking over xprt: now or later?
On Tue, Dec 28, 2004 at 07:04:26PM +0100, David Schweiger wrote: And on top of that, it doesn't work! How can you beat that? I again refer the reader to all the fun 'n games that ensued when the Mozilla maintainer went insane recently. You can find it all by searching the d-u archives. Oh, and by the way... my LaserWriter 630 Pro, an over ten year old Level 2 printer that wasn't high-level when it was *new*, handles Mozilla just fine. And I don't use CUPS, either. -- Marc Wilson | Someone is unenthusiastic about your work. [EMAIL PROTECTED] |
Re: xprt-xprintorg taking over xprt: now or later?
On Tue, Dec 28, 2004 at 06:51:02PM +0100, David Schweiger wrote: > Daniel Stone wrote: > >Ideally, we could get rid of both, but such is life. > > Why ? Xprint is one of the greatest innovations for Unix+Linux printing > in the last five years and becomes more and more widespread. And name one application where it has support other than Mozilla, please. -- Marc Wilson | To kick or not to kick... -- Somewhere on IRC, [EMAIL PROTECTED] | inspired by Shakespeare
Re: that damn debian xlibs/openbox bug!
On Fri, Dec 31, 2004 at 04:06:44AM -0500, Branden Robinson wrote: > On Sun, Dec 12, 2004 at 12:05:29PM +0100, Louis-David Mitterrand wrote: > > Hi, > > > > Starting with version 4.3.0.dfsg.1-5 of debian xlibs, openbox overlay > > panels are broken: switching desktops of alt-tab'ing keeps the transient > > panel focused and in the forground until ENTER is pressed. > > Sounds like the same problem that afflicts sawfish. It may be that openbox > is buggy. Openbox 3 did break at dfsg-5... it was the Debian keymapping buglet. > > Is someone aware of the situation? Is there a workaround for that bug? > > Should I re-open it in the BTS? > > See if you don't feel a bug report against openbox is warranted after > reviewing the above. It's not present in -10. Whichever Debian package did the reorganization of keymaps and related behavior fixed it. I would suggest that the user has a local problem. From my XF86Config-4: Section "InputDevice" Identifier "LiteON SK-6000 Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" Option "XkbOptions""altwin:meta_win" EndSection From my ~/.Xmodmap: ! remove the function of Caps Lock ! and turn it into Multi remove lock = Caps_Lock keycode 66 = Multi_key ! vim: ft=xmodmap nu tw=0 ts=8 I include the above just to show that my configuration is relatively normal. Oh: rei $ /opt/openbox3/bin/openbox --version Openbox 3.2 Copyright (c) 2004 Mikael Magnusson Copyright (c) 2003 Ben Jansens Patches: openbox-3.1-xinerama_no_split+edge-final openbox-3.x-toggle_fullscreen_action openbox-3.x-desktop-menu-icons openbox-3.2-resize-timer openbox-3.2-xgrabpointer openbox-3.2-per-app-settings openbox-3.2-no_snap_beneath openbox-3.2-window-title-numbering This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the file COPYING for details. None of those patches are related to keyboard handling. -- Marc Wilson | BOFH excuse #359: YOU HAVE AN I/O ERROR -> [EMAIL PROTECTED] | Incompetent Operator error signature.asc Description: Digital signature
Re: Xsession and login shells
On Sun, Jul 25, 2004 at 09:23:08PM -0600, Bob Proulx wrote: > Xsession does not spawn a login shell. Why should it? There's no shell running. If the user is starting X from a console prompt, then their environment is already initialized, and if they're using a display manager, then it's the display manager's problem if it wants to source environment variables (which is what this is really about), not that the display manager has any business doing it either. And yes, I've read the bug you point to. I don't agree with it. If the user wants a particular set of environment variables, then their ~/.xsession should source $ENV (or the csh equivalent, which I dis-remember). -- Marc Wilson | When you're in command, command. -- Admiral Nimitz [EMAIL PROTECTED] | signature.asc Description: Digital signature
Bug#268890: infinite recursion when x-terminal-emulator -> uxterm
On Sun, Aug 29, 2004 at 06:14:23PM +0100, Chris Boyle wrote: > Package: xterm > Version: 4.3.0.dfsg.1-6 > Severity: important > > Line 5 of /usr/X11R6/bin/uxterm is: > program=xterm > > If the x-terminal-emulator alternative is pointed at uxterm, then > launching just "xterm" runs uxterm again (since /usr/bin/xterm -> > /etc/alternatives/x-terminal-emulator), recursing infinitely. Better > would be: > program=/usr/X11R6/bin/xterm If your system is in that state, then you put it into it yourself: rei $ ls -l /usr/bin/xterm ls: /usr/bin/xterm: No such file or directory rei $ ls -l /usr/bin/X11/xterm -rwxr-sr-x 1 root utmp 259448 2004-07-07 08:07 /usr/bin/X11/xterm* rei $ ls -l /etc/alternatives/x-terminal-emulator lrwxr-xr-x 1 root root 21 2004-07-10 21:40 /etc/alternatives/x-terminal-emulator -> /usr/X11R6/bin/uxterm* rei $ sudo update-alternatives --display x-terminal-emulator x-terminal-emulator - status is auto. link currently points to /usr/X11R6/bin/uxterm /usr/bin/Eterm - priority 10 slave x-terminal-emulator.1.gz: /usr/share/man/man1/Eterm.1.gz /usr/X11R6/bin/uxterm - priority 30 slave x-terminal-emulator.1.gz: /usr/X11R6/man/man1/uxterm.1x.gz /usr/X11R6/bin/xterm - priority 20 slave x-terminal-emulator.1.gz: /usr/X11R6/man/man1/xterm.1x.gz /usr/bin/aterm-xterm - priority 20 slave x-terminal-emulator.1.gz: /usr/share/man/man1/aterm.1.gz Current `best' version is /usr/X11R6/bin/uxterm. rei $ grep xterm /usr/bin/X11/uxterm # $XFree86: xc/programs/xterm/uxterm,v 1.8 2004/03/04 02:21:56 dickey Exp $ # wrapper script to setup xterm with UTF-8 locale program=xterm # Check environment variables that xterm does, in the same order: #test -f ./xterm && program=./xterm exec $program -class UXTerm -title 'uxterm' -u8 "$@" So... where'd the /usr/bin/xterm binary come from? -- Marc Wilson | Oh don't the days seem lank and long When all goes [EMAIL PROTECTED] | right and none goes wrong, And isn't your life | extremely flat With nothing whatever to grumble at!
Bug#234788: Major data loss because of .xsession-errors
On Mon, Mar 01, 2004 at 10:27:32AM -0500, Branden Robinson wrote: > On Sun, Feb 29, 2004 at 05:23:46PM -0500, Joey Hess wrote: > > Tomasz Wegrzanowski wrote: > > > When I tried it as root, X worked, but the /dev/null became 0600. > > > So it seems it wants to chmod 0600 .xsession-errors. > > > > That would probably be a security hole (at least a DOS: make ld.so 600 > > and the system stops working), but I cannot reproduce it with > > xserver-xfree86 4.2.1-10. > > It is the Xsession script in /etc/X11 that does this chmod. > [question to the general public:] Do you think this chmod should just go > away? Considering the tendency of X applications to spew gods only know what to stdout/stderr, and thus into .xsession-errors, this is probably still a good idea. I can't point to a case where there'd actually be security-sensitive information included therein, but if there were... Paranoia over all, I suppose. -- Marc Wilson | "You who hate the Jews so, why did you adopt their [EMAIL PROTECTED] | religion?" -- Friedrich Nietzsche, addressing | anti-semitic Christians
Bug#239651: xdm: don't invoke non existent Xreset
On Wed, Mar 24, 2004 at 03:43:10AM +0800, Dan Jacobson wrote:
> Package: xdm
> Version: 4.3.0-7
> Severity: normal
>
> $ dlocate -L xdm|LC_ALL=C xargs zgrep Xreset
> /etc/X11/xdm/xdm-config:DisplayManager*reset:
> /usr/X11R6/lib/X11/xdm/Xreset
> that file doesn't exist anymore !! so don't try to invoke it
Really. Describe, please, the failure in your system by xdm attempting to
invoke this, especially considering the priority you assigned the bug.
> /usr/X11R6/man/man1/xdm.1x.gz:or \fIXreset\fP.
> mentioned several times in man page, but not mentioned that it is gone now
> /usr/share/man/man5/xdm.options.5.gz:.I /etc/X11/xdm/Xreset
> same
See above.
> /usr/share/doc/xdm/changelog.Debian.gz: * Drop the
> /etc/X11/xdm/{Xreset,Xsetup} conffiles.
> yes, but also please do the above cleanups
No. The fact that Debian chooses not to ship said files has absolutely
ZERO to do with the fact that xdm supports the use of them. You seem to
have missed THAT little bit of information.
I suppose next you'll recommend that Branden break from upstream and remove
support from the code completely. Then those of us that actually use it
can file bugs requesting that he put it back.
Dan, you file worse bugs than *I* do. Howinhell is this "normal" priority?
Wishlist at best, stupid at worst.
--
Marc Wilson | Humpty Dumpty was pushed.
[EMAIL PROTECTED] |
Bug#240880: xdm: doesn't clean utmp entries
On Sun, Mar 28, 2004 at 11:19:14AM +0800, Dan Jacobson wrote: > Package: xdm > Version: 4.3.0-7 > Severity: minor > > Looks like who output isn't cleared: > # invoke-rc.d xdm stop > # who > root tty1 Mar 28 11:11 > jidanni :0 Mar 28 06:33 > # pstree jidanni > No processes found. > -- debconf information: > * shared/default-x-display-manager: xdm > xdm/stop_running_server_with_children: false > xdm/daemon_name: /usr/bin/X11/xdm Yes, oh clueless one... and of course you want to remove the possibility of cleaning that up, witness bug #239651. Do you ever keep track of your own bug reports? Here you go: #!/bin/sh # # /etc/X11/xdm/Xreset # # This script is run as root after the X session ends. # remove the utmp entry for the session if grep -qs ^use-sessreg /etc/X11/xdm/xdm.options && command -v sessreg > /dev/null 2>&1; then sessreg -d -l $DISPLAY -u /var/run/utmp -x /etc/X11/xdm/Xservers $USER fi exit 0 # vim:set ai et sts=2 sw=2 tw=0: I'm not saying I agree with Branden's decision to unilaterally stop shipping /etc/X11/xdm/Xreset in order to clean up the xconsole stuff, but it's not like it's hard to do this yourself. -- Marc Wilson | Nintendo Declares GCN Most Popular Console [EMAIL PROTECTED] | Ever Who are they kidding? | knghtbrd: Stock holders?
Bug#240788: xserver-xfree86: font config should include font server at port 7110 (default for xfs-xtt)
On Mon, Mar 29, 2004 at 10:35:46AM +0200, Zoltan Ivanfi wrote: > > Package: xserver-xfree86 > Version: 4.3.0-7 > Severity: wishlist > > The default Files section should not only include > > FontPath"unix/:7100"# local font server > > but also > > FontPath"unix/:7110"# local xfs-xtt font > server IHMO, no it shouldn't. XFree is perfectly capable of rendering TrueType fonts, either in the X server itself, or via xfs. It certainly doesn't need to provide support for an outmoded, out-of-date, unnecessary TrueType server that isn't even part of XFree. -- Marc Wilson | Beauty is truth, truth beauty, that is all Ye know [EMAIL PROTECTED] | on earth, and all ye need to know. -- John Keats
Bug#239651: Xreset missing ?
On Mon, Mar 29, 2004 at 10:50:57AM +0200, Guillaume Brocker wrote: > Is it right that Xreset is missing ? It's not required, if that's what you mean. Write one, xdm will use it. > I read that this script was responsible to clean-up session data like > utmp/wtmp entries. That's one of it's uses. See #240880. -- Marc Wilson | Stone's Law: One man's "simple" is another man's [EMAIL PROTECTED] | "huh?"
Bug#241566: [xclock]: colored hands cannot be changed
On Fri, Apr 02, 2004 at 02:40:47AM -0500, Branden Robinson wrote: > On Thu, Apr 01, 2004 at 07:30:50PM -0800, Keith Packard wrote: > > When I added render support to xclock, I did update the man page to note > > that the command line arguments are ignored in render mode (which is the > > default). > > Hmm. This is either not a bug, or xclock should just fail and snarl a > usage message at the user if he tries to do this. IMHO it's not a bug. The bug is that 4.3.0-7 doesn't have the updated man page for xclock, but it's using the updated binary. :) -- Marc Wilson | Hangover, n.: The burden of proof. [EMAIL PROTECTED] | signature.asc Description: Digital signature
Re: x configuration process
On Thu, Apr 29, 2004 at 08:30:17PM -0700, Nick Urban wrote: > Why does X not attempt to configure itself automatically before asking > the user questions? Depends on whether discover and friends are installed or not. > The debconf configurator asks lots of questions that many users don't > understand or care about. If the user does care, they can always just > run `XFree86 -configure' and do some manual editing. Oh, and doing it that way subjects clueless users to LESS intimidating questions. Not. Branden's configuration method is pretty moron-friendly. > Does X it normally autoconfigure when working correctly, or is this a > bigger problem. If it is, can we just steal knoppix autoconfigure system? Please, no... can we have something that works, instead? -- Marc Wilson | Money is the root of all wealth. [EMAIL PROTECTED] |
Re: X Bitmap
On Tue, Jun 15, 2004 at 04:06:23AM +1000, Daniel Stone wrote: > On Mon, Jun 14, 2004 at 07:21:57PM +0200, Kevin Boergens wrote: > > http://netghost.narod.ru/gff/graphics/summary/xbm.htm > > > > I need support for the X BitMap format. On the page mentioned about I > > found a few pieces of code from X to support loading and reading xbm > > (Very old indeed). I was not able to find out what Debian packages I > > have to install to get the needed headers to support xbm. > > Given no-one uses it, I don't think there are actually any packages in > Debian supporting it. Try stealing some of the code from that site. X itself supports it... all the stuff in /usr/X11R6/include/X11/bitmaps/* (for example) is owned by xlibs-data. Unstable's perl uses it, emacs uses it, xfig uses it, ghostscript uses it, etc. The functions that support it are in libX11. You should only have to install xlibs-dev. All the supporting functions have man pages. -- Marc Wilson | Custer committed Siouxicide. [EMAIL PROTECTED] | signature.asc Description: Digital signature
Bug#198447: G450 Dual-Head: Second Monitor I2C Detection Happening Incorrectly
On Sun, Jun 22, 2003 at 06:02:22PM -0500, Jason Bucata wrote: > I have two different monitors that I'm trying to use in a dual-head > configuration, if only just to experiment with it. The I2C monitor info > detection isn't working on the second head. In the logs, I see it > detecting the first monitor twice, so that it assumes that I have two > identical monitors. Just as a data point, Debian's X has behaved like this for a long time. Both my dual-head 400 and my dual-head 450 exhibited this behavior. So does my G550 (not currently installed anywhere or I'd verify if it still did). Thinking back, I believe that the reason I did not file a bug on it was that I'd brought it up on Matrox's own forum (I was having other dual-head issues that were hardware-related), and the moderator there told me that it was a hardware limitation of the card in some way. Perhaps I should have anyway. Anyone who's ever participated in Matrox's forum knows that usually details are usually somewhat... lacking. > The explicit frequency settings in the configuration file appear to be > ignored. I got around this by explicitly disabling I2C on both heads. I knew perfectly well what the specifications of my monitors were... I didn't need X to figure it out for me. ^_^ -- Marc Wilson | Please, won't somebody tell me what diddie-wa-diddie [EMAIL PROTECTED] | means? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#198447: G450 Dual-Head: Second Monitor I2C Detection Happening Incorrectly
On Thu, Jun 26, 2003 at 01:01:36AM -0500, Jason Bucata wrote: > On Tue, Jun 24, 2003 at 09:51:13PM -0700, Marc Wilson wrote: > > I got around this by explicitly disabling I2C on both heads. I knew > > perfectly well what the specifications of my monitors were... I didn't > > need X to figure it out for me. ^_^ > > How do I go about trying that? I pored over the docs I could find on > xfree86.org but they didn't say anything about how to do that. The relevant sections from my archived (and hopefully correct) configuration file for the G550: Section "Device" Identifier "MatroxG550 Primary" VendorName "Matrox" Driver "mga" Screen 0 BusID "PCI:1:0:0" Option "NoDDC" Option "AGPMode" "2" EndSection Section "Device" Identifier "MatroxG550 Secondary" VendorName "Matrox" Driver "mga" Screen 1 BusID "PCI:1:0:0" Option "NoDDC" Option "AGPMode" "2" EndSection I think the "NoDDC" option is what you want. Here is some discussion from the Matrox forum via Google's cache regarding the detection problem (Ben is/was the only one of their moderators that had a brain): http://216.239.39.100/search?q=cache:W02FxzA7OjEJ:forum.matrox.com/mgaforum/Forum2/HTML/001921.html+matrox+%22noDDC%22&hl=en&ie=UTF-8&client=googlet The "NoDDC" option is discussed here: http://www.xfree86.org/4.0/RELNOTES2.html -- Marc Wilson | The disks are getting full; purge a file today. [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#199838: Re : Bug#199838: xfree86: 4.2.1-9 src fails to build
On Thu, Jul 03, 2003 at 01:55:37PM +0200, Jean-Luc wrote: > Thanks, but it does not works here. Just as a data point, I built 4.2.1-9 from source here last night, with no problem. Even used pentium-builder and did an athlon-xp build, just to see if I could. ^_^ Wanted to build it since the complete set of packages for i386 didn't appear in the archive on the same night, unfortunately. LC_COLLATE does the job here. > On 03-07-2003 13:37, Daniel Stone wrote: > >export LC_COLLATE=C, before you build. > > > >-- > >Daniel Stone > ><[EMAIL PROTECTED]> > >http://www.kde.org - http://www.debian.org - http://www.xwin.org > > -- Marc Wilson | Who loves me will also love my dog. -- John Donne [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Xfree 4.3 Experimental. netscape needs glue-package xlib6g?
On Tue, Aug 19, 2003 at 12:30:58AM +0200, Wilfried Goesgens wrote: > I think it's in the xlibs-package, should the package 'provide' xlib6g? xlib6g is deprecated, no one should be depending on it. If you MUST have Netscape 4.77, perhaps you can use equivs to fake it out. -- Marc Wilson | "One lawyer can steal more than a hundred men [EMAIL PROTECTED] | with guns." -- The Godfather -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#198447: G450 Dual-Head: Second Monitor I2C Detection Happening Incorrectly
On Sun, Jun 22, 2003 at 06:02:22PM -0500, Jason Bucata wrote: > I have two different monitors that I'm trying to use in a dual-head > configuration, if only just to experiment with it. The I2C monitor info > detection isn't working on the second head. In the logs, I see it > detecting the first monitor twice, so that it assumes that I have two > identical monitors. Just as a data point, Debian's X has behaved like this for a long time. Both my dual-head 400 and my dual-head 450 exhibited this behavior. So does my G550 (not currently installed anywhere or I'd verify if it still did). Thinking back, I believe that the reason I did not file a bug on it was that I'd brought it up on Matrox's own forum (I was having other dual-head issues that were hardware-related), and the moderator there told me that it was a hardware limitation of the card in some way. Perhaps I should have anyway. Anyone who's ever participated in Matrox's forum knows that usually details are usually somewhat... lacking. > The explicit frequency settings in the configuration file appear to be > ignored. I got around this by explicitly disabling I2C on both heads. I knew perfectly well what the specifications of my monitors were... I didn't need X to figure it out for me. ^_^ -- Marc Wilson | Please, won't somebody tell me what diddie-wa-diddie [EMAIL PROTECTED] | means?
Bug#198447: G450 Dual-Head: Second Monitor I2C Detection Happening Incorrectly
On Thu, Jun 26, 2003 at 01:01:36AM -0500, Jason Bucata wrote: > On Tue, Jun 24, 2003 at 09:51:13PM -0700, Marc Wilson wrote: > > I got around this by explicitly disabling I2C on both heads. I knew > > perfectly well what the specifications of my monitors were... I didn't > > need X to figure it out for me. ^_^ > > How do I go about trying that? I pored over the docs I could find on > xfree86.org but they didn't say anything about how to do that. The relevant sections from my archived (and hopefully correct) configuration file for the G550: Section "Device" Identifier "MatroxG550 Primary" VendorName "Matrox" Driver "mga" Screen 0 BusID "PCI:1:0:0" Option "NoDDC" Option "AGPMode" "2" EndSection Section "Device" Identifier "MatroxG550 Secondary" VendorName "Matrox" Driver "mga" Screen 1 BusID "PCI:1:0:0" Option "NoDDC" Option "AGPMode" "2" EndSection I think the "NoDDC" option is what you want. Here is some discussion from the Matrox forum via Google's cache regarding the detection problem (Ben is/was the only one of their moderators that had a brain): http://216.239.39.100/search?q=cache:W02FxzA7OjEJ:forum.matrox.com/mgaforum/Forum2/HTML/001921.html+matrox+%22noDDC%22&hl=en&ie=UTF-8&client=googlet The "NoDDC" option is discussed here: http://www.xfree86.org/4.0/RELNOTES2.html -- Marc Wilson | The disks are getting full; purge a file today. [EMAIL PROTECTED] |
Bug#199838: Re : Bug#199838: xfree86: 4.2.1-9 src fails to build
On Thu, Jul 03, 2003 at 01:55:37PM +0200, Jean-Luc wrote: > Thanks, but it does not works here. Just as a data point, I built 4.2.1-9 from source here last night, with no problem. Even used pentium-builder and did an athlon-xp build, just to see if I could. ^_^ Wanted to build it since the complete set of packages for i386 didn't appear in the archive on the same night, unfortunately. LC_COLLATE does the job here. > On 03-07-2003 13:37, Daniel Stone wrote: > >export LC_COLLATE=C, before you build. > > > >-- > >Daniel Stone > ><[EMAIL PROTECTED]> > >http://www.kde.org - http://www.debian.org - http://www.xwin.org > > -- Marc Wilson | Who loves me will also love my dog. -- John Donne [EMAIL PROTECTED] |
Re: Xfree 4.3 Experimental. netscape needs glue-package xlib6g?
On Tue, Aug 19, 2003 at 12:30:58AM +0200, Wilfried Goesgens wrote: > I think it's in the xlibs-package, should the package 'provide' xlib6g? xlib6g is deprecated, no one should be depending on it. If you MUST have Netscape 4.77, perhaps you can use equivs to fake it out. -- Marc Wilson | "One lawyer can steal more than a hundred men [EMAIL PROTECTED] | with guns." -- The Godfather
Bug#131155: xterm: -fa is respected, but provided font is ignored without error message
On Sat, Oct 11, 2003 at 02:56:32PM +0200, Friedrich Delgado Friedrichs wrote: > This also doesn't explain why the font looks so ugly. Every character > is in the upper left region of a rectangular box, with quite a lot of > space between the characters. This sounds more like you don't have any monospaced font that your xft configuration can fall back to, and it's substituting a proportional one. Proportional fonts will sometimes work for a basic xterm, although they usually look pretty strange, but they won't work right at all using Xft. Usually it looks like things are double-spaced. Xterm *asks* for a particular font, but Xft can pretty much do whatever it wants based on the configuration file. Debian's default /etc/X11/XftConfig will replace any request xterm makes for '-fa fixed' with "mono", which it doesn't alias again later on so I'm not quite sure what you'd end up with. Probably one of the Vera fonts, if you have those installed. Remember too that you can't pass an XLFD via '-fa'... xterm isn't going to like that at all. Snerf around the 'net and find a copy of the 'Andale Mono' or 'Monotype.com' TTF fonts. They'll look pretty good for you. -- Marc Wilson | A transistor protected by a fast-acting fuse will [EMAIL PROTECTED] | protect the fuse by blowing first. signature.asc Description: Digital signature
Bug#216317: /usr/X11R6/bin/xdm: use stars to show how many chars we type at password: prompt
On Sat, Oct 18, 2003 at 05:18:09AM +0800, Dan Jacobson wrote: > Use stars to show how many chars we type at password: prompt. Thank you, no, can the world not have this argument again? It's a security issue. *I* don't want someone to be able to look at a screen and divine how many characters comprise my password. The only person who needs to know how long it is is *you*, and you already have that information. > Hmmm, login(1) doesn't. OK, well, whatever. For the same reason. -- Marc Wilson | When we talk of tomorrow, the gods laugh. [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#215845: Seeing similar problem on x86
On Mon, Oct 20, 2003 at 09:30:32AM -0700, Brian Knotts wrote: > This is a dual-monitor setup 3200x1200, with a Matrox G450. > Setting X11 to single-monitor makes the problem go away. > Currently using latest available libxrender1 on this platform: 0.8.3-2 On WHICH platform? The buildd's haven't gotten to -4 yet on i386, apparently, but packages for it are available for several architectures. The source package for -4, however, is available and will fix the problem if you build it for yourself. $ apt-get source --build libxrender1 Build-Depends: cdbs (>= 0.4.12), debhelper (>= 4.0.0), pkg-config, xlibs-dev, render-dev -- Marc Wilson | Linus' Law: There is no heavier burden than a great [EMAIL PROTECTED] | potential. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Text in wrong location with Xinerama
On Wed, Oct 29, 2003 at 08:44:43AM -0800, Bill Moseley wrote: > I'm still having problems with Xinerama. With some applications running > on the primary screen when I select a menu and drag my mouse up and down > the menu *sometimes* instead of the menu item showing selected it > vanishes and the text shows up on my other screen. > Anyone else experience this? I've been using Xinerama for the last couple months (since -10 of the XFree packages) and I've not seen this behavior yet. I was about to jump on the window manager as being at fault, but you say it happens with toolkits too (Mozilla uses GTK and GTK would be responsible for its menus). What toolkit does OpenOffice use? I don't think I've ever thought about that. The -bin package has an explicit dependency on libxaw7, but what part of it is using Athena widgets? :) -- Marc Wilson | Misfortunes arrive on wings and leave on foot. [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Text in wrong location with Xinerama
On Wed, Oct 29, 2003 at 07:51:31PM +0100, Michel Dänzer wrote: > If this is with a Matrox card, see > http://bugs.xfree86.org/show_bug.cgi?id=130 . You know, I ran Matrox cards, both 450 and 550, in dual-head mode for ages and never saw this. Does it require Xinerama to tickle it? I never made significant use of Xinerama until recently. If it *does* require Xinerama, that "workaround" seems a little excessive... unless what the comment means that RENDER acceleration is only disabled if Xinerama is also active. :) I'm learning that Xinerama is even more of a gross hack than I'd ever known before. -- Marc Wilson | All great ideas are controversial, or have been at [EMAIL PROTECTED] | one time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#131155: xterm: -fa is respected, but provided font is ignored without error message
On Sat, Oct 11, 2003 at 02:56:32PM +0200, Friedrich Delgado Friedrichs wrote: > This also doesn't explain why the font looks so ugly. Every character > is in the upper left region of a rectangular box, with quite a lot of > space between the characters. This sounds more like you don't have any monospaced font that your xft configuration can fall back to, and it's substituting a proportional one. Proportional fonts will sometimes work for a basic xterm, although they usually look pretty strange, but they won't work right at all using Xft. Usually it looks like things are double-spaced. Xterm *asks* for a particular font, but Xft can pretty much do whatever it wants based on the configuration file. Debian's default /etc/X11/XftConfig will replace any request xterm makes for '-fa fixed' with "mono", which it doesn't alias again later on so I'm not quite sure what you'd end up with. Probably one of the Vera fonts, if you have those installed. Remember too that you can't pass an XLFD via '-fa'... xterm isn't going to like that at all. Snerf around the 'net and find a copy of the 'Andale Mono' or 'Monotype.com' TTF fonts. They'll look pretty good for you. -- Marc Wilson | A transistor protected by a fast-acting fuse will [EMAIL PROTECTED] | protect the fuse by blowing first. signature.asc Description: Digital signature
Bug#218864: xlibs-dev: won't install because of version conflict with xlibs
On Sun, Nov 02, 2003 at 09:38:24PM -0500, Brian Minton wrote: > The following packages have unmet dependencies: > xlibs-dev: Depends: xlibs (= 4.2.1-13) but 4.3.0-0ds3v1 is to be > installed > E: Broken packages It's hardly a grave bug, when YOU are the one with unofficial packages installed breaking things. -- Marc Wilson | Blessed be those who initiate lively discussions [EMAIL PROTECTED] | with the hopelessly mute, for they shall be know | as Dentists. signature.asc Description: Digital signature
Re: how to start X with NumLock on?
On Wed, Nov 19, 2003 at 09:38:27AM +0100, Louis-David Mitterrand wrote: > Am I the only one who finds that NumLock being off when X starts is > counter-intuitive? Probably not. > After all it is ON at the console. If you configure it that way. Big whoop. > And, really, the numeric keypad on an extended keyboard (pc105) is not > that useful when NumLock is OFF. It's not? The keys there stop working when NumLock isn't engaged? > 1) would it be a good idea to make the default ON? Not for me. > 2) how can I make it the default in my own config? $ apt-get install numlockx -- Marc Wilson | QOTD: "If I'm what I eat, I'm a chocolate chip [EMAIL PROTECTED] | cookie."
Bug#225685: xfree86-common: Xsession does not perform a proper login
On Wed, Dec 31, 2003 at 04:53:48PM +0100, Hadmut Danisch wrote: > when logging in through Xsession, there is no proper login > when having a csh type shell: The .login is never executed. Yes, and that'd probably be due to the fact that csh isn't ever executed, either. Do you see a shell anywhere? If you're depending on ~/.login to set environment variables for you, do it somewhere else. Better yet, don't use csh. ^_^ -- Marc Wilson | Excusing bad programming is a shooting offence, no [EMAIL PROTECTED] | matter _what_ the circumstances. -- Linus Torvalds, | to the linux-kernel list
Bug#230422: xfree86-common: Should include /etc/X11/Xreset{.d}
On Fri, Jan 30, 2004 at 11:23:50PM +0100, Petter Reinholdtsen wrote:
>
> Package: xfree86-common
> Version: 4.2.1-16
> Severity: wishlist
>
> In skolelinux, we would like to run a script when the users are
> logging out, to do general cleanup. For this, it would be useful if
> the display managers had hooks in Xreset we could use to have our
> script executed.
>
> Could you please add /etc/X11/Xreset and /etc/X11/Xreset.d (like the
> current /etc/X11/Xsession{.d}), and thus make it possible for the
> display managers to share one such file?
>
> If you are interested in adding this feature, I'll provide a patch and
> send bugreports against wdm, xdm and kdm to ask them to use this file.
What patch would you be adding against xdm, exactly, since xdm already
knows how to do this quite well on its own?
Well, it doesn't do anything silly like /etc/X11/Xreset.d, but it does
support Xreset and has pretty much forever. The fact that Debian doesn't
ship one just means that you get to create one.
See xdm(1).
--
Marc Wilson | For the next hour, WE will control all that you see
[EMAIL PROTECTED] | and hear.
Bug#230537: xdm: warn of unused Identifiers
On Sun, Feb 01, 2004 at 01:38:39AM +0800, Dan Jacobson wrote: > Package: xdm > Version: 4.2.1-14 > Severity: wishlist > > In /var/log/XFree86.0.log there could be warnings/notices about > Identifiers declared, but then never used in ServerLayout, e.g.: > (II) ... Identifier "ZZ" declared, but then never used in ServerLayout > (II) ... Identifier "ZZ" unused in ServerLayout Why? You can have any number of ServerLayout sections too, and tell xinit/startx which one you want to use. I suppose you'll want FURTHER noise in the log detailing the ServerLayout(s) that don't get used? I don't know about you, oh clueless one, but I keep many things defined in my XFree configuration so that I don't have to *re-define* them when I want to use them. Doesn't mean I need the log nattering at me to tell me what I already know. Daniel is right. Don't file bugs against X without thinking first. Or at least reading a man page. -- Marc Wilson | If bankers can count, how come they have eight [EMAIL PROTECTED] | windows and only four tellers?
Bug#782505: libxrender1 still blocks *all* security updates on affected systems
Unsubscribe -- Marc Wilson > On Apr 28, 2015, at 8:11 AM, Toomas Tamm wrote: > > As of 28-apr-2015 (11 days after the bug was claimed fixed), on systems > where both 32- and 64-bit libxrender1 is installed, all upgrades > remain blocked due to this bug. For example, the kernel security fix > of 27-apr-2015 does not get installed on affected systems. > > Affected system: > > # apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > You might want to run 'apt-get -f install' to correct these. > The following packages have unmet dependencies: > libxrender1 : Breaks: libxrender1:i386 (!= 1:0.9.7-1+deb7u1) but > 1:0.9.7-1+deb7u1+b1 is installed > libxrender1:i386 : Breaks: libxrender1 (!= 1:0.9.7-1+deb7u1+b1) but > 1:0.9.7-1+deb7u1 is installed > E: Unmet dependencies. Try using -f. > > Unaffected system: > > # apt-get upgrade > Reading package lists... > Building dependency tree... > Reading state information... > The following packages will be upgraded: > linux-headers-3.2.0-4-amd64 linux-headers-3.2.0-4-common > linux-image-3.2.0-4-amd64 linux-libc-dev > 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 28.5 MB of archives. > After this operation, 9,490 kB of additional disk space will be used. > [snip] > > IMO this deserves "grave" classification and appropriate handling > because unrelated software is affected and security fixes do not get > installed. > > If manual intervention is needed, please provide appropriate > instructions at bugs.debian.org. > > Regards, > > Toomas Tamm > Estonia > -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/d21c3c79-554e-4ad6-b4b7-163e825f9...@gmail.com
Bug#198447: xserver-xfree86: [mga] DDC queries to second monitor going to first monitor instead
On Sat, 2007-01-13 at 23:54 +0100, Brice Goglin wrote: > About 4 years ago, you reported (or replied to) a bug in the Debian BTS > regarding DDC queries not going to the 2nd monitor on a MGA board. Did > any of you guys reproduce this problem recently? If not, I will close > this bug in the next weeks. Last time I checked, Matrox still had all sorts of problems with the idea of supporting the second head on a G450/G550 correctly, including but not limited to the DCC problem and mis-implemented maximum refresh rates. But that "last time" was a long time ago... while I still own the card, I don't run X (indeed, don't run Linux) on that box any longer. It works just fine as a text console on OpenBSD. :) I'm not the original submitter, but you can close it for all of me, if necessary. -- Marc Wilson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#322284: x11-common: dbus provides a session since 2004
Package: x11-common Followup-For: Bug #322284 Apparently dbus has provided a session bus for X since Feb of 2004, as detailed in: http://lists.debian.org/debian-devel-changes/2004/02/msg00194.html Anyone know whether Debian's xorg is suddenly going to inherit a dbus dependency? It'd be a show-stopper for allowing it to install, if it does. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: update-alternatives and window-manager and display-manager
On Sun, Aug 21, 2005 at 11:55:14AM +0200, Paolo Pantaleo wrote: > 1) I think that the display mangaer should be choosen using > update-alternatives --confi x-display-manager > (btw: how is it made now?) The startup scripts for the various display managers pay attention to the contents of the file /etc/X11/default-display-manager > 2) I have gnome installed, but in > update-alternatives --config x-window-manager > gnome it is not displayed Gnome isn't a window manager, and has never been a window manager. > So i think that the update-alternatives method is not fully supported. You'd be wrong. > I think that * update-alternatives is a good facility It isn't, really. > * there should be a unified method for chosing window/desktop manager or > whatever, since it gives the users some chances to do things without much > pain, and make easy to document and learn how things works No, actually a user should never be messing with the alternatives system. Further, users don't need to know and shouldn't have to know how things work. > So, is update-alternatives the standard method? If not which is the > standard method? The standard method is to actually launch the environment you want. Gdm provides session files for this purpose, as does KDM. Xdm uses your ~/.xsession file. How do you expect a user to be changing the alternatives system? They don't have the power to do so. -- Marc Wilson | Once, adv.: Enough. -- Ambrose Bierce, "The Devil's [EMAIL PROTECTED] | Dictionary" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#325488: Wishlist: please add complete support for type 6 keyboard
Package: xlibs
Version: 6.8.2.dfsg.1-5
Severity: wishlist
Please include patch to provide complete Sun Type 6 keyboard support
under Xorg as detailed in f.d.o bug #2037:
https://bugs.freedesktop.org/show_bug.cgi?id=2037
This has already been committed upstream.
-- Package-specific info:
Keyboard-related contents of X.Org X server log file
/var/log/Xorg.0.log:
(**) | |-->Monitor "SyncMaster 171v"
(**) | |-->Device "nVidia GF4 MX440 Primary"
(**) |-->Screen "Secondary" (1)
(**) | |-->Monitor "SyncMaster 171v"
(**) | |-->Device "nVidia GF4 MX420 Secondary"
(**) |-->Input Device "LiteON SK-6000 Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc104"
(**) XKB: model: "pc104"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(**) Option "XkbOptions" "altwin:meta_win"
(**) XKB: options: "altwin:meta_win"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Microsoft WheelMouse Optical USB"
(**) FontPath set to "unix/:7100"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(**) Option "BlankTime" "15"
--
(II) LoadModule: "nvidia"
(II) Loading /usr/X11R6/lib/modules/drivers/nvidia_drv.o
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.7174
Module class: XFree86 Video Driver
(II) LoadModule: "keyboard"
(II) Loading /usr/X11R6/lib/modules/input/keyboard_drv.o
(II) Module keyboard: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.4
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
--
(II) Entity 0 shares no resources
(II) Entity 1 shares no resources
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
--
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) LiteON SK-6000 Keyboard: Core Keyboard
(**) Option "Protocol" "standard"
(**) LiteON SK-6000 Keyboard: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) LiteON SK-6000 Keyboard: XkbRules: "xfree86"
(**) Option "XkbModel" "pc104"
(**) LiteON SK-6000 Keyboard: XkbModel: "pc104"
(**) Option "XkbLayout" "us"
(**) LiteON SK-6000 Keyboard: XkbLayout: "us"
(**) Option "XkbOptions" "altwin:meta_win"
(**) LiteON SK-6000 Keyboard: XkbOptions: "altwin:meta_win"
(**) Option "CustomKeycodes" "off"
(**) LiteON SK-6000 Keyboard: CustomKeycodes disabled
(**) Option "Protocol" "ImPS/2"
(**) Microsoft WheelMouse Optical USB: Device: "/dev/input/mice"
(**) Microsoft WheelMouse Optical USB: Protocol: "ImPS/2"
(**) Option "CorePointer"
(**) Microsoft WheelMouse Optical USB: Core Pointer
--
(**) Microsoft WheelMouse Optical USB: ZAxisMapping: buttons 4 and 5
(**) Microsoft WheelMouse Optical USB: Buttons: 5
(**) Option "Resolution" "200"
(**) Microsoft WheelMouse Optical USB: Resolution: 200
(II) XINPUT: Adding extended input device "Microsoft WheelMouse Optical USB"
(type: MOUSE)
(II) XINPUT: Adding extended input device "LiteON SK-6000 Keyboard" (type:
KEYBOARD)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(II) Microsoft WheelMouse Optical USB: ps2EnableDataReporting: succeeded
Warning: font renderer for ".pcf" already registered at priority 0
Warning: font renderer for ".pcf.Z" already registered at priority 0
X.Org X server log files on system:
-rw-r--r-- 1 root root 38713 2005-08-28 07:03 /var/log/Xorg.0.log
Compiled XKB description for X server ":0.0":
xkb_keymap {
xkb_keycodes "xfree86+aliases(qwerty)" {
minimum = 8;
maximum = 255;
= 9;
= 10;
= 11;
= 12;
= 13;
= 14;
= 15;
= 16;
= 17;
= 18;
= 19;
= 20;
= 21;
= 22;
= 23;
= 24;
= 25;
= 26;
= 27;
= 28;
= 29;
= 30;
= 31;
= 32;
= 33;
= 34;
= 35;
= 36;
= 37;
= 38;
= 39;
= 40;
= 41;
= 42;
= 43;
= 44;
= 45;
= 46;
= 47;
= 48;
= 49;
= 50;
= 51;
= 52;
= 53;
= 54;
= 55;
= 56;
= 57;
= 58;
= 59;
= 60;
= 61;
= 62;
= 63;
= 64;
= 65;
= 66;
= 67;
= 68;
= 69;
= 70;
= 71;
= 72;
= 73;
= 74;
= 75;
= 76;
= 77;
= 78;
=
Re: New xterm packages.
On Tue, Sep 27, 2005 at 02:08:24AM +0200, David Martínez Moreno wrote: > The configure line is (apart from usual XXXdir=/usr...and so on): > > ./configure --enable-logging --enable-wide-chars --enable-luit > --enable-256-color Are those the same options the monolithic package is compiled with? I ask not because I have a problem with these options (other than the logging), but that if the behavior of xterm suddenly changes, I'll know where to look. ^_^ -- Marc Wilson | "It's kind of fun to do the impossible." -- [EMAIL PROTECTED] | Walt Disney signature.asc Description: Digital signature
Bug#350113: Library dependencies
Why is libxft2 not depending on v2.1.10 of libfreetype6 if it's going to use symbols exclusive to that version? Some of us Sid users are holding libfreetype6 at 2.1.7-2.4 until someone decides how to fix things with THAT package. Of course,that begs the question of when the libfreetype6 maintainer is going to get around to doing something about #316031 in specific, along with other bugs caused by the unilateral move to 2.1.10, such as #315150, #318671, and etc. As was pointed out in #325526, libfreetype6 v2.1.10 isn't going to get to testing any time soon, so.... -- Marc Wilson | "One Architecture, One OS" also translates as "One [EMAIL PROTECTED] | Egg, One Basket". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350113: Library dependencies
On Tue, Feb 07, 2006 at 08:43:33PM -0500, David Nusinow wrote: > The real issue is of course with freetype's shlibs file. I have an NMU > sitting on my hard drive that would correct this problem, but it was > rejected by the release team because freetype is apparently cracktacular. I > haven't decided if creating a shlibs.local file for xft is the right > solution in the end, so I defer to the release team and the freetype > maintainer since I have no desire to wade in to those waters. So in the meantime, the new libxft2 moves into testing, except it doesn't work with the libfreetype6 in testing... and unstable's libfreetype6 can't move into testing due to the multitude of bugs filed against it. Wow... this should be fun. And, of course, we have the new libfreetype6 maintainer, who uploads this apparently broken version to unstable and then goes into hiding. -- Marc Wilson | Logic is a pretty flower that smells bad. [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347857: Setup script for XDM login screen
On Sat, Feb 25, 2006 at 01:14:12AM +0100, Björn Lindström wrote: > Where is the right place to put stuff that you want to run when > starting XDM now. Still in /etc/X11/xdm/Xsetup. > but it's not working anymore with xdm-6.9.0.dfsg.1-4 Actually the XSF broke it without notice (and no changelog entry) back in 6.9.0-1. See bug #347857. You can fix it by adding the line back to xdm-config: rei $ grep Xsetup /etc/X11/xdm/xdm-config DisplayManager*setup: /usr/X11R6/lib/X11/xdm/Xsetup -- Marc Wilson | Nintendo Declares GCN Most Popular Console [EMAIL PROTECTED] | Ever Who are they kidding? | knghtbrd: Stock holders? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#355706: xdm: Xsetup stopped working
On Tue, Mar 07, 2006 at 03:14:21PM +0100, Diego Biurrun wrote: > sometime in January xdm stopped displaying a background picture (and > boy, that gray grid pattern is ugly..). It seems that support for > /etc/X11/xdm/Xsetup was dropped silently. This contradicts the > documentation since xdm.1 still says that background images should be > set using Xsetup. No, /etc/X11/xdm/Xsetup is still the place. The problem is that the XSF dropped the line from /etc/X11/xdm/xdm-config that told xdm to actually USE it. You can put it back yourself. See bug #347857. -- Marc Wilson | Inspired by a true story. [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debug XFree86 vs X.org font rendering
On Mon, Mar 13, 2006 at 03:31:22PM +1100, Mark Hannon wrote: > Found an answer ... downgraded to libfreetype6=2.1.7-2.4 and font > rendering is much better. Unfortunately the broken 2.1.10 libfreetype6 is now part of both Sid and Etch, and at least libxft2 depends on symbols the broken library provides. -- Marc Wilson | We are all in the gutter, but some of us are looking [EMAIL PROTECTED] | at the stars. -- Oscar Wilde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: APT-able Debian DRI CVS packages ready for testing.
Ok, perhaps I'm really dense, but what's the advantage of using this over just using Branden's X debs? I have 3d acceleration and working DRI for both my V3 and my G450 as it stands, without adding any further software. And I can turn it on or off as I want (if I need 24 bit for something, for example). So, what's the scoop? - Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.moonkingdom.net/mwilson -Original Message- From: Zephaniah E. Hull [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2001 9:56 PM To: debian-x@lists.debian.org; debian-devel@lists.debian.org; dri-devel@lists.sourceforge.net Subject:APT-able Debian DRI CVS packages ready for testing. << File: ATT00048.dat >> Yes, thats right, it is now apt-able. Aside from not having kernel modules yet, there are no known packaging issues. Same warnings from the previous message apply. The URL is http://people.debian.org/~warp/dri/. For APT throw the following two lines into your /etc/apt/sources.list. deb http://people.debian.org/~warp/dri/ ./ deb-src http://people.debian.org/~warp/dri/ ./ Please send me reports on if it works, possible issues, etc. Zephaniah E. Hull. -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. "And now, little kittens, we're going to run across red-hot motherboards, with our bare feet." -- Buzh.
Re: XFree-4.1 SID
Please read: http://lists.debian.org/debian-x/2001/debian-x-200110/msg4.html This will tell you what's wrong with the Xsession.d file in question. On Thu, Oct 11, 2001 at 12:18:15PM +0200, Clemens Wohld wrote: > > Hallo, > > I have big problems to get my xserver back after the last > "apt-get dist-upgrade". > > Somebody told me that the /etc/X11/Xsession have any bugs, > any escape is not theredont know. > > Can find nothing. > Also google tells me nothing about this error. > > My Debian "Sid-update" I made on 10.10.2001, there are KDE include. > > Someone can gimmi any hints/help to run xinit normal? > > > > Thx and Greetings > > Clemens Wohld > > PS: I speak better german, so when your can write the mail in > german will be happy ;) > > > -- > _ _ _ http://urlz.de/xpage > __| | ___| |__ (_) __ _ _ __ _ __ __ __ __ ___ ___ > / _` |/ _ \ '_ \| |/ _` | '_ \ | '_ \ / \\ \ /\ / // _ \| _| > | (_| | __/ |_) | | (_| | | | | | _)-| () |\ V V /| __/| | > \__,_|\___|_.__/|_|\__,_|_| |_| |_|\__/ \_/\_/ \___||_| > Debian GNU/Linux: The OS So Big Its Scary-*-senc-*- > ------ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Bug#118173: xmms: playlist fonts screwed up, shows empty squares instead of text
On Sun, Nov 04, 2001 at 08:38:49PM +0100, Josip Rodin wrote: > On Sat, Nov 03, 2001 at 04:33:08PM -0500, rj fleck wrote: > > Package: xmms > > Version: 1.2.5-2 > > Severity: important > > > > seems to have only started happening on newer versions of the x-libraries > > > > ii xlibs 4.1.0-7X Window System client > > libraries > > I've got xlibs 4.1.0-5 here and it's fine. WTF? :) It's the old "fonts as boxes" thing. You'd think all these people running testing/unstable would learn how to read someday. -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] pgpPJtw8jGNxB.pgp Description: PGP signature
Re: gsfonts-x11 removal problems
On Wed, May 08, 2002 at 08:09:16PM -0500, Colin Watson wrote: > The offender would appear to be libgnomeprint-data (and hence > libgnomeprint15, and hence large quantities of GNOME). I'm not familiar > with why it might be doing this, so I haven't filed a bug. I don't claim to understand the packaging system, but does this make any sense? Package: libgnomeprint-data Status: install ok installed Priority: optional Section: libs Installed-Size: 1516 Maintainer: Christian Marillat <[EMAIL PROTECTED]> Source: gnome-print Version: 0.35-4 Replaces: libgnomeprint6, gnome-print Depends: libgnomeprint-bin (>= 0.32-1), gs, gsfonts-x11 Recommends: gsfonts Description: The GNOME Print architecture - data files This package contains fonts and locale files needed by gnome-print. Why does it depend on gsfonts-x11, but only recommend gsfonts? Or is that OK, because gsfonts-x11 itself depends on gsfonts? Or does that mean that it doesn't need the Recommends: line at all? Actually, it's supposed to be the other way around, isn't it? Depend on gs and gsfonts, recommend gsfonts-x11. 'Cept gs itself only recommends gsfonts... I'm soo confused. :) -- Marc Wilson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xdm in 4.2.0-0pre1v1
On Thu, Aug 01, 2002 at 11:23:01AM +0200, Lars G. T. Jorgensen wrote: > I don't know if it's just me that has messed up my configuration or a > real problem. But after I updated to X 4.2 the installation of xdm > looks like the default one with the XFree86 logo and logging in just > bounces me back to the same login screen. Known issue... replace its configuration with the one you saved from xdm 4.1.0 (these are pre debs, you did do a backup first, of course), and it'll act normally again. Failing that, search the archives... the essential configuration changes were in a message thread of less than a week ago. -- Marc Wilson [EMAIL PROTECTED]
Bug#165416: xfree86: no warning of meta/alt/windows key behavior change
On Fri, Oct 18, 2002 at 02:58:48PM -0700, David Parker wrote: > After reading the changelogs I figured out that I had to add the > following to my XF86Config-4 file: > > Option "XkbOptions""altwin:meta_win" > > There was no warning of this change, and for a long time I was > unable to fix the problem. I'm sure Branden will be considerably more caustic, but the best possible answer would be... whyinhell hadn't you read the changelog in the first place, where this is explicitly described? This *is* unstable, after all. You really gotta love the way people think nowadays... oh, no, I don't see any reason why I should look at a changelog and find out what changed in package "X"... I'll decide the KERNEL, which hasn't changed, must suddenly be at fault. Sheesh. > I think that if this setting isn't added automatically to the user's > config file, it should at least be documented in README.Debian and > displayed in a dialog before the package is installed. For every person that expects that ALT is ALT and Windows is META, there's another person who expects that ALT is META and is going to lame about how you've broken their copy of emacs. Don't gratuitously add options to configuration files. -- Marc Wilson [EMAIL PROTECTED]
Bug#166497: x-window-system: should depend on x-display-manager instead of xdm
On Sat, Oct 26, 2002 at 11:32:11AM -0700, Agthorr wrote: > Package: x-window-system > Version: 4.1.0-16 > Severity: normal > > The x-window-system should depend on x-display-manager (provided by > xdm, gdm, kdm, and wdm) instead of on xdm. How is this anything more than a wishlist bug? What's going to win if NOTHING is installed, which is when people are going to be installing x-window-system in the first place. Xdm is the XFree-provided display manager. Install another if you want another. All the display managers can co-exist. -- Marc Wilson [EMAIL PROTECTED]
Bug#166413: mga driver doesn't set gamma on second screen
On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote: > 2) It is possible that this is a hardware limitation. Multiple-output > video cards often don't support all features on secondary "heads". I always had the problem with my G450 and later with my G550 that X wouldn't set the gamma the same on both heads, although it claimed that it was according to the log. The monitors were the same make and model, and the difference was distinct and annoying. OTOH, xgamma was always quite willing to set the gamma on the heads separately, and I was also able to specify specific gamma settings for each monitor in XF86Config-4 and have them take effect. > [I'd appreciate feedback from Matrox users on the debian-x list so I > know whether I'm right about 2) or not.] Hope that helps. -- Marc Wilson [EMAIL PROTECTED] pgp5sfCXdUe48.pgp Description: PGP signature
Bug#166413: mga driver doesn't set gamma on second screen
On Sun, Oct 27, 2002 at 11:14:37PM -0500, [EMAIL PROTECTED] wrote: > On Sun, Oct 27, 2002 at 07:07:15PM -0800, Marc Wilson wrote: > > I always had the problem with my G450 and later with my G550 that X > > wouldn't set the gamma the same on both heads, although it claimed that it > > was according to the log. The monitors were the same make and model, and > > the difference was distinct and annoying. > > > > OTOH, xgamma was always quite willing to set the gamma on the heads > > separately, and I was also able to specify specific gamma settings for each > > monitor in XF86Config-4 and have them take effect. > > In that case I'm confused. Has there been a regression since XFree86 > 4.1 or not? I should clarify... When I was still using the G450/G550, X would claim that it was setting the gamma on the two monitors identically. Anyone who looked at them, though, would be able to tell that they were wildly different. I used xgamma (at first) in $HOME/.xsession, and later manipulating XF86Config-4 directly, to reduce the gamma on the second monitor, like so: Section "Monitor" Identifier "Viewsonic PF790" HorizSync 30-97 VertRefresh 50-180 Option "DPMS" "Yes" Gamma 0.8 0.8 1.15 EndSection This was the only way I could make the two of them balance. I always chalked it up to just hardware differences in the respective video outputs (ie they had different ideas of what gamma 1.0 meant) and got on with things. I haven't run either of my Matrox cards on XF 4.2.x... it's a nVidia world in my box now (I wouldn't have, but they were free). Sorry for any confusion I may have introduced. I think I was trying to point out that even though they weren't being set the same (and X claimed they were), there was still individual control on both heads. -- Marc Wilson [EMAIL PROTECTED]
Bug#362078: xserver-xorg: dpkg-reconfigure doesn't work if the xorg.conf has been customized
On Wed, Apr 12, 2006 at 01:02:45AM -0400, David Nusinow wrote: > The dpkg-reconfigure script needs to write a new xorg.conf if the file has > been customized. A user in #debian reported that this failed on his system, > and it made it difficult for him to automagically adapt to the new paths > for modular. This will provide a manual easy way out of this dilemma, > easing future support. As long as it writes it somewhere OTHER than on top of /etc/X11/xorg.conf, please. The fact that a customized configuration will not be destroyed without a deliberate action is a good thing, whether or not that customized configuration is "correct" by some definition, or not. I know I'd be more than a little offended if my carefully worked-out dual-screen-and-additional-input-devices configuration were arbitrarily overwritten. -- Marc Wilson | Your job is being a professor and researcher: [EMAIL PROTECTED] | That's one hell of a good excuse for some of the | brain-damages of minix. (Linus Torvalds to Andrew | Tanenbaum) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362253: Neither discover1, laptop-detect, mdetect nor xresprobe are needed
On Thu, Apr 13, 2006 at 04:43:20PM -0700, Russ Allbery wrote: > Well, I do. Depends is also used for package configuration. If the > package can't configure itself without those packages, Depends is > appropriate. The problem with discover, IMHO, is that once it gets installed, it's not going to be just called upon as part of producing a working X configuration. It's going to screw things up every time the machine reboots, since it has an init script. Or it used to. CD-ROMs that come and go randomly, interfaces that get renamed for no apparent reason, etc. OTOT, I have to admit that none of Debian's auto-detection tools save for hotplug (and now udev) have been allowed on any box I control in a very long time, so perhaps that's changed. Certainly udev has the same or similar set of problems. If it were a dependency of a meta-package, at least you could remove it and only lose the meta-package. But xserver-xorg *depends* on it now, rather than just recommending it, so you're stuck with it. Can't this be fixed? -- Marc Wilson | "The sixties were good to you, weren't they?" -- [EMAIL PROTECTED] | George Carlin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#363081: x11-common still depends on laptop-detect
Package: x11-common Version: 7.0.12 Severity: important The x11-common package still depends on laptop-detect, which pulls in dmidecode, even though the other hardware detection tools have been pushed back to recommends (see bug #362253). I have checked the 7.0.13 currently in incoming, and it still has the dependency. And no, I haven't actually *installed* it, I'm waiting for the modular dust to settle. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14.2 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy ii debianutils 2.15.6 Miscellaneous utilities specific t ii lsb-base 3.1-3 Linux Standard Base 3.1 init scrip x11-common recommends no packages. -- debconf information: x11-common/experimental_packages: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#372077: use NEWS.Debian
On Thu, Jun 29, 2006 at 09:09:31PM -0400, David Nusinow wrote: > On Fri, Jun 23, 2006 at 04:01:38PM -0400, Joey Hess wrote: > > 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. > > I would love this personally. I feel like apt-listchanges should be > standard, and to be honest, I'm sick of telling newbies in #debian to > install it. That it would solve this bug is the cherry on top. Of course, now that apt-listchanges is broken in unstable while people argue about upstream changes to tar, maybe y'all need to find another way. :) Just FYI. -- Marc Wilson | need help: my first packet to my provider [EMAIL PROTECTED] | gets lost :-( sel: dont send the first one, | start with #2 * netgod is kidding -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391304: IMO, right-clicking in xterm should bring up the font size menu
On Thu, Oct 05, 2006 at 05:12:15PM -0400, Jason Spiro wrote: > IMO, right-clicking in xterm should bring up the font size menu > (currently only accessible by Control+rightclick). And in MY opinion, not. Gee, we offset each other, don't we? And both our opinions are even valid. Fortunately, Tom Dickey's opinion actually controls. > The font menu would be more useful than the current feature that is bound > to the right mouse button (extend selection). Oh yes, because after all, you spend *so* much time changing the font size of your xterm. I, on the other hand, use selections all the time. > Plus, most people currently don't know how to access the font menu. > Once this change is made, everybody will know how. Most people start xterm with the font they want it to use in the first place. If you want xterm to act that way, why don't you just configure it to? Not like it's hard, and you have an excellent built-in example. -- Marc Wilson | Wait! You have not been prepared! -- Mr. Atoz, [EMAIL PROTECTED] | "Tomorrow is Yesterday", stardate 3113.2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#399638: xterm: broken rendering in ncurses programs
On Tue, Nov 21, 2006 at 06:29:15AM -0500, Thomas Dickey wrote: > On Tue, Nov 21, 2006 at 03:40:08AM +0100, Marc Wilson wrote: > > "avoid repainting the screen" sounds very like what I'm seeing in mutt. > > Layout inside the xterm window is correct, it's just that characters are... > > missing. > > Maybe - if it were that simple, I think I'd be seeing more reports. Here's an example of what I see with mutt running inside xterm: http://members.cox.net/msw/05.png Moving mutt's highlight bar over the lines missing characters causes them to be redrawn correctly. -- Marc Wilson | My only love sprung from my only hate! Too early [EMAIL PROTECTED] | seen unknown, and known too late! -- William | Shakespeare, "Romeo and Juliet" signature.asc Description: Digital signature
Bug#401726: xterm: color change on redraw
So, does this mean that it's a bug in xterm, or a but in mutt, or what? I know it's mutt that *triggers* it... when mutt launched vim in its window to compose this message, the window flashed cyan, and I've got this cyan border. It didn't do that before. -- Marc Wilson | BOFH excuse #61: not approved by the FCC [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: APT-able Debian DRI CVS packages ready for testing.
Ok, perhaps I'm really dense, but what's the advantage of using this over just using Branden's X debs? I have 3d acceleration and working DRI for both my V3 and my G450 as it stands, without adding any further software. And I can turn it on or off as I want (if I need 24 bit for something, for example). So, what's the scoop? - Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.moonkingdom.net/mwilson -Original Message- From: Zephaniah E. Hull [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 27, 2001 9:56 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject:APT-able Debian DRI CVS packages ready for testing. << File: ATT00048.dat >> Yes, thats right, it is now apt-able. Aside from not having kernel modules yet, there are no known packaging issues. Same warnings from the previous message apply. The URL is http://people.debian.org/~warp/dri/. For APT throw the following two lines into your /etc/apt/sources.list. deb http://people.debian.org/~warp/dri/ ./ deb-src http://people.debian.org/~warp/dri/ ./ Please send me reports on if it works, possible issues, etc. Zephaniah E. Hull. -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. "And now, little kittens, we're going to run across red-hot motherboards, with our bare feet." -- Buzh. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XFree-4.1 SID
Please read: http://lists.debian.org/debian-x/2001/debian-x-200110/msg4.html This will tell you what's wrong with the Xsession.d file in question. On Thu, Oct 11, 2001 at 12:18:15PM +0200, Clemens Wohld wrote: > > Hallo, > > I have big problems to get my xserver back after the last > "apt-get dist-upgrade". > > Somebody told me that the /etc/X11/Xsession have any bugs, > any escape is not theredont know. > > Can find nothing. > Also google tells me nothing about this error. > > My Debian "Sid-update" I made on 10.10.2001, there are KDE include. > > Someone can gimmi any hints/help to run xinit normal? > > > > Thx and Greetings > > Clemens Wohld > > PS: I speak better german, so when your can write the mail in > german will be happy ;) > > > -- > _ _ _ http://urlz.de/xpage > __| | ___| |__ (_) __ _ _ __ _ __ __ __ __ ___ ___ > / _` |/ _ \ '_ \| |/ _` | '_ \ | '_ \ / \\ \ /\ / // _ \| _| > | (_| | __/ |_) | | (_| | | | | | _)-| () |\ V V /| __/| | > \__,_|\___|_.__/|_|\__,_|_| |_| |_|\__/ \_/\_/ \___||_| > Debian GNU/Linux: The OS So Big Its Scary-*-senc-*- > ------ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#118173: xmms: playlist fonts screwed up, shows empty squares instead of text
On Sun, Nov 04, 2001 at 08:38:49PM +0100, Josip Rodin wrote: > On Sat, Nov 03, 2001 at 04:33:08PM -0500, rj fleck wrote: > > Package: xmms > > Version: 1.2.5-2 > > Severity: important > > > > seems to have only started happening on newer versions of the x-libraries > > > > ii xlibs 4.1.0-7X Window System client libraries > > I've got xlibs 4.1.0-5 here and it's fine. WTF? :) It's the old "fonts as boxes" thing. You'd think all these people running testing/unstable would learn how to read someday. -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] msg03207/pgp0.pgp Description: PGP signature
Re: Default X background.
On Sun, Apr 28, 2002 at 10:22:31PM +0100, Pedro Corte-Real wrote: > X uses by default (and tradition I supose) that grey/white pattern for > it's background. Ugly, ain't it? :) > I know I can run "xsetroot" or equivalent and change it afterwards but > It'd rather not have to see the thing at all. Can you really see it for that split-second before the copy of xsetroot called from your .xinitrc/.xsession resets it? Certainly typing the command yourself gets old... that's what the startup file is for. :) -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] msg03567/pgp0.pgp Description: PGP signature
