Bug#661627: Avoid /tmp ?
This appears to be a pretty serious problem. I agree, just dropping '-p' won't work for functional reasons. As a better long-term solution, have you considered just moving those directories out of /tmp? There's almost always a safer place to put temporary files/directories. For instance, under /var/lib or /var/run, or whatever is most appropriate as an application-specific directory, whose parent isn't world-writable. tim -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120229215118.gh1...@sentinelchicken.org
Bug#661627: Avoid /tmp ?
Hi Bernhard, > > As a better long-term solution, have you considered just moving those > > directories out of /tmp? > > Those are for sockets whose name is part of the interface to access > them. So you cannot move them. And the directory itself needs to be > world-writeable, so it is best placed within /tmp. Hmm, sounds like a badly-designed interface. Where is this interface defined? I don't doubt you, I'm merely naive about X design/interface, and curious as to how flexible this is. Is this use of /tmp a Debian thing, an Xorg thing, or an X11R6 thing? thanks, tim -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120229223919.gi1...@sentinelchicken.org
Bug#661627: Avoid /tmp ?
As far as the short-term solution to this problem goes, how about this (untested)? if [ -e $SOCKET_DIR ] && [ ! -d $SOCKET_DIR ]; then mv $SOCKET_DIR $SOCKET_DIR.$$ || exit $? fi if [ ! -e $SOCKET_DIR ]; then mkdir $SOCKET_DIR || exit $? chown root:root $SOCKET_DIR chmod 1777 $SOCKET_DIR fi First move other types of files out of the way, as before (is this even necessary?). After that, we should have either no SOCKET_DIR or a directory by that name we have created previously. If it doesn't exist as a directory, create it. If something by that name suddenly appears in the race after our second existence test, then fail, since someone is clearly doing some hanky-panky. Otherwise, we should own the file and there shouldn't be a risk. I realize that the "|| exit $?" items are redundant given the script's "set -e", but I like to see things explicit when security matters, since some future maintainer might accidentally remove the "set -e" for seemingly unrelated reasons. Note that the "chown root:root $SOCKET_DIR" also seems redundant to me (if we didn't already own it, we would have bigger problems, right?). tim -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120301195529.gj1...@sentinelchicken.org
Bug#661627: Avoid /tmp ?
Hi Julien,
> > As far as the short-term solution to this problem goes, how about
> > this (untested)?
> >
> >
> > if [ -e $SOCKET_DIR ] && [ ! -d $SOCKET_DIR ]; then
> > mv $SOCKET_DIR $SOCKET_DIR.$$ || exit $?
> > fi
> > if [ ! -e $SOCKET_DIR ]; then
> > mkdir $SOCKET_DIR || exit $?
> > chown root:root $SOCKET_DIR
> > chmod 1777 $SOCKET_DIR
> > fi
> >
> So far I have this:
>
> diff --git a/debian/x11-common.init b/debian/x11-common.init
> index 34835ac..71f9fd5 100644
> --- a/debian/x11-common.init
> +++ b/debian/x11-common.init
> @@ -30,10 +30,12 @@ set_up_socket_dir () {
>if [ "$VERBOSE" != no ]; then
> log_begin_msg "Setting up X server socket directory $SOCKET_DIR..."
>fi
> - if [ -e $SOCKET_DIR ] && [ ! -d $SOCKET_DIR ]; then
> -mv $SOCKET_DIR $SOCKET_DIR.$$
> + # if $SOCKET_DIR exists and isn't a directory, move it aside
> + if [ -e $SOCKET_DIR ] && ! [ -d $SOCKET_DIR ] || [ -h $SOCKET_DIR ]; then
> +mv $SOCKET_DIR "$(mktemp -d $SOCKET_DIR.XX)"
>fi
> - mkdir -p $SOCKET_DIR
> + # make sure $SOCKET_DIR exists and isn't a symlink
> + mkdir $SOCKET_DIR 2>/dev/null || [ -d $SOCKET_DIR ] && ! [ -h $SOCKET_DIR ]
>chown root:root $SOCKET_DIR
>chmod 1777 $SOCKET_DIR
>do_restorecon $SOCKET_DIR
> @@ -44,10 +46,10 @@ set_up_ice_dir () {
>if [ "$VERBOSE" != no ]; then
> log_begin_msg "Setting up ICE socket directory $ICE_DIR..."
>fi
> - if [ -e $ICE_DIR ] && [ ! -d $ICE_DIR ]; then
> -mv $ICE_DIR $ICE_DIR.$$
> + if [ -e $ICE_DIR ] && [ ! -d $ICE_DIR ] || [ -h $ICE_DIR ]; then
> +mv $ICE_DIR "$(mktemp -d $ICE_DIR.XX)"
>fi
> - mkdir -p $ICE_DIR
> + mkdir $ICE_DIR 2>/dev/null || [ -d $ICE_DIR ] && ! [ -h $ICE_DIR ]
>chown root:root $ICE_DIR
>chmod 1777 $ICE_DIR
>do_restorecon $ICE_DIR
>
> Compared to your version it allows moving aside a broken symlink, but
> other than that (and the mktemp use) they should be equivalent, I think.
> Another pair of eyes would be appreciated though...
I think there is still a race in your version in the lines which look
like:
> + mkdir $ICE_DIR 2>/dev/null || [ -d $ICE_DIR ] && ! [ -h $ICE_DIR ]
mkdir will fail if the file already exists for any reason. After
mkdir fails, it is possible that another process will be able to run
and remove/create new versions of the path with different properties
after your tests run.
Here's a specific attack that could work, I think:
1. create a plain file named $ICE_DIR
2. monitor the file and wait for it to be moved to the new mktemp name
3. create a directory with the $ICE_DIR name before mkdir runs
4. mkdir will fail
5. After the -h test finishes, but before the chown is run, remove the
directory and replace it with a symlink
Yes, this is complicated and would require lots of luck given the
context of the script, but it would certainly be best to avoid any
dangerous races.
The reason that my version of the script avoids this issue is that it
relies on the atomicity of mkdir. If that fails, simply bail out.
Don't do any additional tests afterward, since that introduces a race.
I can't guarantee my version doesn't have other races though, so
please do pick over it carefully...
> > Note that the "chown root:root $SOCKET_DIR" also seems redundant to me
> > (if we didn't already own it, we would have bigger problems, right?).
> >
> I guess it protects against some user doing mkdir /tmp/.X11-unix before
> this runs (which probably means before the package is installed, so it's
> not like this is a very likely race) and then owning the directory.
Oh, right, duh. Well, the dir is created every time the box boots,
since /tmp is cleared, so it is needed for sure.
thanks,
tim
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120301203941.gl1...@sentinelchicken.org
Bug#661627: Avoid /tmp ?
> /etc/init.d/x11-common on boot should run before any unprivileged user > has a chance to do anything (it's in rcS.d, and depends only on > $local_fs), so it's less of a problem than initial package installation > AFAICT. I'm not that familiar with the newer dependency boot sequencing, but I know someone who looked into this and seemed to think cron or atd *could* run before it. Looking at the scripts I have on my box, it seems like you may be right, assuming nothing else has a similar set of dependencies (namely, only $local_fs) which could hand off control to a user non-root user. However, my analysis doesn't cover every init script in every possible package... tim -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120301210802.gm1...@sentinelchicken.org
Bug#778991: xserver-xorg-video-intel: graphical glitches in the circulating symbol while waiting for an application
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Severity: normal Dear Maintainer, this problem affects multiple application. E.g. Empathy: Connecting to an account takes a while. The process is visualized by two circulating symbols in the empathy window. The normal behaviour should be that these symbols integrate well in the background of the window. But instead of this they have a little black square background. Sorry, I can't give a more detailed description of the bug and will send a picture after recieve the bug number. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Feb 21 15:37 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 10 19:35 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) Xorg X server log files on system: -- -rw-r--r-- 1 root root 33205 Feb 22 11:57 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [44.723] X.Org X Server 1.16.4 Release Date: 2014-12-20 [44.723] X Protocol Version 11, Revision 0 [44.723] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [44.723] Current Operating System: Linux mobybit 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) x86_64 [44.723] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/mobybit--vg-root ro quiet [44.723] Build Date: 11 February 2015 12:32:02AM [44.723] xorg-server 2:1.16.4-1 (http://www.debian.org/support) [44.723] Current version of pixman: 0.32.6 [44.723]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [44.723] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [44.723] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 22 10:43:12 2015 [44.724] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [44.725] (==) No Layout section. Using the first Screen section. [44.725] (==) No screen section available. Using defaults. [44.725] (**) |-->Screen "Default Screen Section" (0) [44.725] (**) | |-->Monitor "" [44.725] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [44.725] (==) Automatically adding devices [44.725] (==) Automatically enabling devices [44.725] (==) Automatically adding GPU devices [44.726] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [44.726]Entry deleted from font path. [44.726] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [44.726]Entry deleted from font path. [44.726] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [44.726]Entry deleted from font path. [44.726] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [44.726]Entry deleted from font path. [44.726] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [44.726]Entry deleted from font path. [44.726] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [44.726]Entry deleted from font path. [44.726] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [44.726] (==) ModulePath set to "/usr/lib/xorg/modules" [44.726] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [44.726] (II) Loader magic: 0x7f1c9237bd80 [44.726] (II) Module ABI versions: [44.726]X.Org ANSI C Emulation: 0.4 [44.726]X.Org Video Driver: 18.0 [44.726]X.Org XInput driver : 21.0 [44.726]X.Org Server Extension : 8.0 [44.727] (II) xfree86: Adding drm device (/dev/dri/card0) [44.728] (--) PCI:*(0:0:2:0) 8086:0166:17aa:21fa rev 9, Mem @ 0xf000/4194304, 0xe000/268435456, I/O @ 0x5000/64 [44.728] (II) LoadModule: "glx" [44.729] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [44.737] (II) Module glx: vendor="X.Org Foundation" [44.737]compiled for 1.16.4, module version = 1.0.0 [44.737]ABI class: X.Org Server Extension, version 8.0 [44.737] (==) AIGLX enabled [44.737] (==) Matched intel as
Bug#778991:
Okay, now I have tried the xserver-xorg-video-intel from experimental without any improvement. -- 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/1424834031.5081.0.ca...@mobybit.de
Bug#815013: xserver-xorg-video-intel: SNA causes crash with Java application
Package: xserver-xorg-video-intel Version: 2:2.99.917+git20160127-1+b1 Severity: important I was using Debian jessie which was working fine. Then I upgraded to stretch and my X sessions started crashing. Without debugging too much, I then upgraded to sid in the hope that the X libraries/drivers would magically fix the problem. Still broken. So then I did some investigation. The behavior I observed on stretch and sid is that once I open a GUI-intensive Java application (in my case Burp Proxy) a little bit of clicking around and using scroll bars causes X to crash. I am unable to restart xdm after this, so I believe the video card gets stuck in a broken state. Upon reading a bit on the intel(4) man page, I saw the AccelMethod options, so I added this to my xorg.conf: Option "AccelMethod""UXA" The Xorg.0.log file indicates that UXA is indeed being used now, and so far I haven't had another crash. So it appears SNA is the culprit. The Xorg.0.log file you see below is from *after* I made this change. I will also attach the Xorg.0.log.old file, which shows what happens when SNA is enabled (note the crash at the end of the file). cheers, tim -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Mar 31 2014 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Feb 9 03:12 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) Xorg X server configuration file status: -rw-r--r-- 1 root root 4955 Feb 17 10:12 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/X11/misc" FontPath "/usr/share/fonts/X11/cyrillic" FontPath "/usr/share/fonts/X11/100dpi/:unscaled" FontPath "/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/share/fonts/X11/100dpi" FontPath "/usr/share/fonts/X11/75dpi" FontPath "built-ins" EndSection Section "Module" Load "glx" EndSection Section "InputClass" Identifier "evdevClass" # required MatchIsTouchpad "yes" # required Driver "evdev" # required EndSection Section "InputClass" Identifier "touchpadClass" # required MatchIsTouchpad "yes" # required Driver "synaptics" # required Option "MinSpeed" "0.5" Option "MaxSpeed" "1.0" Option "AccelFactor" "0.075" Option "TapButton1""1" Option "TapButton2""2" # multitouch Option "TapButton3""3" # multitouch Option "VertTwoFingerScroll" "1" # multitouch Option "HorizTwoFingerScroll" "1" # multitouch Option "VertEdgeScroll""1" Option "CoastingSpeed" "8" Option "CornerCoasting""1" Option "CircularScrolling" "1" Option "CircScrollTrigger" "7" Option "EdgeMotionUseAlways" "1" Option "LBCornerButton""8" # browser "back" btn Option "RBCornerButton""9" # browser "forward" btn EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputClass" Identifier "Kingsis Peripherals Evoluent VerticalMouse 2" #0x Product 0x3061 Driver "evdev" # required MatchUSBID ":3061" Option &q
Bug#443004: patch seems to work
FWIW, I've had this problem on two systems recently, one that was updated, another fresh install. I don't remember what I did to get around it the first time, but on the fresh install system I used this patch and it was indeed able to write the xorg.conf. thanks, tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#24192: getting to know you
Hi, Hope bI am nobt writing to wrong address. Ib am nice, pretty lookinag girl. I am planning on visitinga your town this month. Can we meet each other in person? Message me back at [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#616511: xserver-xorg-video-vesa: Blank screen on ATI R580
Hi Cyril, Thanks for your prompt reply. > as in “X :0”? That's normal, you get a black background and no X > client by default. You could try: > X :0 & sleep 5; DISPLAY=:0 xterm Ok, its been a long time since I ran X directly, as I normally use xdm. There have been so many different issues that have come up with Xorg in general (window manager config changes, etc) after the last upgrade that I've had a hard time narrowing down where the problem is. So let me back up and show you what I'm seeing with xdm: Currently, with both the radeon driver (with radeon kernel module loaded) and with vesa (with radeon not loaded) I am able to get to the xdm login screen. However, once I log in, xdm reports that X crashes. See the attached log. In the case of radeon, when this happens my video is completely toast and I have to reboot. With vesa, at least I can recover and try logging in again or stop xdm. However, the console font becomes so big after trying with vesa that it's very hard to use the console. > Your log indeed looks fine. There's the fbdev driver you could try by > the way. Or disabling KMS to see if that helps with your radeon > issue. Is the bug you're having with radeon reported in the BTS? I did try the fbdev driver with radeon loaded. I have not tried disabling KMS yet, but I'm starting to think this may not be directly related to the video driver. Let me know what you think. thanks much, tim -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305161415.ga1...@sentinelchicken.org
Bug#616511: xserver-xorg-video-vesa: Blank screen on ATI R580
Hi John, > I'll restate the obvious. note I'm not part of > xserver-xorg-video-vesa team - so look for more answers. > > make sure your linux kernel has radeon support. make sure X loads > the modules. make sure X.org supports the chipset that is actually > on the card. Yes, as I mentioned I'm using the latest generic kernel which does include the radeon module. Normally I use a custom built kernel which also has radeon+KMS, but I fell back to the generic in case I had screwed up some build options. As for support of the chipset... well the radeon kernel module doesn't complain about anything. It is an R580 which is well within the series supported by the radeon team. Thanks, tim -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305161654.gb1...@sentinelchicken.org
Bug#616511: xserver-xorg-video-vesa: Blank screen on ATI R580
figures... forgot to attach the log. tim Sat Mar 5 08:06:01 2011 xdm info (pid 1776): Starting Sat Mar 5 08:06:01 2011 xdm info (pid 1776): Starting X server on :0 X.Org X Server 1.9.4 Release Date: 2011-02-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian Current Operating System: Linux shannon 2.6.37-2-amd64 #1 SMP Sun Feb 27 10:12:22 UTC 2011 x86_64 Kernel command line: root=UUID=2c3be234-03c7-470d-abe8-322c4b19df93 ro Build Date: 20 February 2011 04:48:15AM xorg-server 2:1.9.4-3 (Cyril Brulebois ) Current version of pixman: 0.21.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 5 08:06:02 2011 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" Sat Mar 5 08:06:05 2011 xdm info (pid 1790): sourcing /etc/X11/xdm/Xsetup Sat Mar 5 08:06:09 2011 xdm info (pid 1790): sourcing /etc/X11/xdm/Xstartup Sat Mar 5 08:06:09 2011 xdm info (pid 1799): executing session /etc/X11/xdm/Xsession Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x45ceb8] 1: /usr/bin/X (0x40+0x64cd9) [0x464cd9] 2: /lib/libpthread.so.0 (0x7f6165336000+0xef60) [0x7f6165344f60] 3: /usr/bin/X (0x40+0x37631) [0x437631] 4: /usr/bin/X (0x40+0x38b2d) [0x438b2d] 5: /usr/bin/X (ProcessWorkQueue+0x21) [0x43afa1] 6: /usr/bin/X (WaitForSomething+0x82) [0x4653f2] 7: /usr/bin/X (0x40+0x32b12) [0x432b12] 8: /usr/bin/X (0x40+0x2573b) [0x42573b] 9: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f6164098c4d] 10: /usr/bin/X (0x40+0x252c9) [0x4252c9] Segmentation fault at address 0x14 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. Sat Mar 5 08:06:10 2011 xdm error (pid 1776): Server for display :0 terminated unexpectedly: 1536 Sat Mar 5 08:06:10 2011 xdm info (pid 1790): sourcing /etc/X11/xdm/Xreset Sat Mar 5 08:06:10 2011 xdm info (pid 1776): Starting X server on :0 X.Org X Server 1.9.4 Release Date: 2011-02-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian Current Operating System: Linux shannon 2.6.37-2-amd64 #1 SMP Sun Feb 27 10:12:22 UTC 2011 x86_64 Kernel command line: root=UUID=2c3be234-03c7-470d-abe8-322c4b19df93 ro Build Date: 20 February 2011 04:48:15AM xorg-server 2:1.9.4-3 (Cyril Brulebois ) Current version of pixman: 0.21.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 5 08:06:10 2011 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" Sat Mar 5 08:06:12 2011 xdm info (pid 1848): sourcing /etc/X11/xdm/Xsetup Sat Mar 5 08:06:19 2011 xdm info (pid 1776): Shutting down Sat Mar 5 08:06:19 2011 xdm info (pid 1776): display :0 is being disabled Sat Mar 5 08:06:19 2011 xdm info (pid 1776): Exiting
Bug#616511: xserver-xorg-video-vesa: Blank screen on ATI R580
> as in “X :0”? That's normal, you get a black background and no X > client by default. You could try: > X :0 & sleep 5; DISPLAY=:0 xterm I just tried this as well, as you suggested. I fired up X with: X :0 & and was able two switch back and forth between the blank X window and the console. Note that unlike with xdm, the mouse cursor did not show up. Next I ran: DISPLAY=:0 urxvt And at that point X crashed, just like it does when spawning from xdm. Let me know if there are other things I should try. thanks, tim -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305163100.ga1...@sentinelchicken.org
Bug#616511: xserver-xorg-video-vesa: Blank screen on ATI R580
> Don't bother, I think I know what fails. Try to remove those lines > from your config: > | Section "Files" > | FontPath"unix/:7100"# local font server > | FontPath"unix/:7101"# local font server > | EndSection > > IIRC, the xfs-related bug upstream is that one: > https://bugs.freedesktop.org/show_bug.cgi?id=31501 Oh, cheesh, that works. Sorry, I didn't see your replies right away because they got stuffed in my spam bucket. So yeah, I am able to use X fine now with radeon and everything. Hopefully that patch makes it downstream soon. Sorry for posting that extra bug, didn't see your solution at that point. Thanks much, tim -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305184128.gc1...@sentinelchicken.org
Bug#616578: Acknowledgement (xserver-xorg-core: X crashes when most programs attach to :0 / :0.0)
I didn't notice Cyril's reply right away to my initial issue. As it turns out the bug is probably this one: https://bugs.freedesktop.org/show_bug.cgi?id=31501 Disabling my font server config at least allows me to use X again. Let me know if/when the patch makes it downstream. Thanks, tim -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305184304.ga2...@sentinelchicken.org
Bug#642374: xauth: Doesn't seem to handle concurrency [SEC=UNCLASSIFIED]
Package: xauth Version: 1:1.0.6-1 Severity: normal for run in `seq 1 10` do ssh -X -l "xload" & done /usr/bin/xauth: error in locking authority file /home//.Xauthority X11 connection rejected because of wrong authentication. A sleep 0.1 though lets it through (most of the time, but like all race conditions, this is a deeply evil hack). One suspects xauth shouldn't just fail immediately if it can't hardlink the lockfile. Act more like procmail's lockfile utility, and back off a bit while retrying. -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'stable'), (5, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xauth depends on: ii libc6 2.13-7 Embedded GNU C Library: Shared lib ii libx11-6 2:1.4.3-2 X11 client-side library ii libxau6 1:1.0.6-3 X11 authorisation library ii libxext6 2:1.3.0-3 X11 miscellaneous extension librar ii libxmuu1 2:1.1.0-2 X11 miscellaneous micro-utility li xauth recommends no packages. xauth suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110922003828.27034.23637.report...@weinberg.bom.gov.au
Bug#708055: [libglapi-mesa] not upgradable on multiarch
Package: libgl1-mesa-dri Version: 8.0.5-4 Followup-For: Bug #708055 Control: retitle -1 [libglapi-mesa, libgl1-mesa-dri] not upgradable on multiarch Control: severity -1 serious Also affects libgl1-mesa-dri. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgl1-mesa-dri:amd64 depends on: ii libc6 2.17-0experimental2 ii libdrm-intel1 2.4.40-1~deb7u2 ii libdrm-nouveau1a 2.4.40-1~deb7u2 ii libdrm-radeon12.4.40-1~deb7u2 ii libdrm2 2.4.40-1~deb7u2 ii libexpat1 2.1.0-3 ii libffi5 3.0.10-3 ii libgcc1 1:4.8.0-6 ii libstdc++64.8.0-6 libgl1-mesa-dri:amd64 recommends no packages. Versions of packages libgl1-mesa-dri:amd64 suggests: pn libglide3 -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130515184048.7957.14585.report...@mitrobox.lan.naturalnet.de
Bug#765331: xserver-xorg-video-intel: occasional hangs in read from /dev/dri/card0 with "AccelMethod" "sna"
Package: xserver-xorg-video-intel Version: 2:2.99.916-1~exp1 Severity: important I'm running xserver-xorg-video-intel/experimental with Option "AccelMethod" "sna" because otherwise operation on haswell is incredibly unreliable (my latest problem being horible display corruption on webbrowsers with text). But I think in all versions of xserver-xorg-video-intel I've run, every now and then when coming home to a suspended screen, it doesn't wake up. I can ssh in and chvt 1, or I can run strace on the xorg process and the strace causes the xorg process to wake up (I think I see futex() calls in the first few lines but my eyes aren't quick enough, and I've not yet managed to remember to redirect the strace log to a file. However, this time, it hasn't woken up. Don't know whether it's the same bug or not, but here we go: 79151,46> strace -f -p 14075 Process 14075 attached with 4 threads - interrupt to quit [pid 14079] futex(0x7ffbe94db344, FUTEX_WAIT_PRIVATE, 503838665, NULL [pid 14078] futex(0x7ffbe94db2d4, FUTEX_WAIT_PRIVATE, 560566957, NULL [pid 14077] futex(0x7ffbe94db264, FUTEX_WAIT_PRIVATE, 759160725, NULL [pid 14075] read(9, 79152,47> l /proc/14075/fd/9 lrwx-- 1 root root 64 Oct 10 00:39 /proc/14075/fd/9 -> /dev/dri/card0 -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jul 3 2013 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2356320 Jul 18 08:25 /usr/bin/Xorg Diversions concerning libGL are in place diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104M [GeForce GTX 670MX] [10de:11a1] (rev ff) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 12 -rw-r--r-- 1 root root 220 Jul 11 2013 20-backspace-terminate.conf -rw-r--r-- 1 root root 1842 Jul 7 2013 50-synaptics.conf -rw-r--r-- 1 root root 717 Sep 24 00:12 70-sna-accel.conf KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.14-0.bpo.2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.14.15-2~bpo70+1 (2014-08-21) Xorg X server log files on system: -- -rw-r--r-- 1 root root 42264 Jul 9 2013 /var/log/Xorg.2.log -rw-r--r-- 1 root root 57523 Jul 14 2013 /var/log/Xorg.1.log -rw-r--r-- 1 root bumblebee 15344 Aug 30 21:47 /var/log/Xorg.8.log -rw-r--r-- 1 root root 36610 Oct 14 18:11 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 222.721] X.Org X Server 1.16.0 Release Date: 2014-07-16 [ 222.721] X Protocol Version 11, Revision 0 [ 222.721] Build Operating System: Linux
Bug#508867: Ping
Hi, I still see the bug, running -stable. On Tue, 21 Jan 2014, Solveig wrote: > Hi! > Do you still encounter this bug with latest versions? If yes, please > provide up-to-date data, and if not, this bug report might be closed, so > let us know :) > Cheers, > > Solveig > > -- Tim Connors -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.02.1401221104500.13...@dirac.rather.puzzling.org
Bug#192229: xfree overwrites new driver with old each upgrade
Package: xfree86-common Version: 4.2.1-6 Each and every time I've upgraded xfree in the last 2 years, my X breaks. I spend 30-40 minutes reworking my XF86Config-.. and puzzling over why it has broken, until my memory dimly recalls that I am using the latest video driver, and this new version of X has probably come equipped with an old driver. I'm puzzled as to why and maybe just plumb unlucky but old drivers always seem to break my system. Is there some way in which a newer driver can be flagged so that it doesn't get overwritten by an older driver? Debian package mgmt does so much other stuff well that this would seem possible (and should even be the default behaviour?) Tim Burgess
Bug#166234: xserver-xfree86: Removing patch 009_i810_xv_blue_bar_fix.diff fixes problem on i810e
I'm having the same problem on a similar setup with an i810e. Removing debian/patches/009_i810_xv_blue_bar_fix.diff and rebuilding fixes it for me. This fails to address bug #131602, which the patch was the original purpose of the patch. A modification of the patch, however, should be sufficient to close the bug. Bcc: Tim Pope <[EMAIL PROTECTED]> Package: xserver-xfree86 Version: 4.2.1-3 Followup-For: Bug #166234 ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "i810" Driver "i810" EndSection Section "Monitor" Identifier "Dell E770" HorizSync 30-60 VertRefresh 50-75 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "i810" Monitor "Dell E770" DefaultDepth16 SubSection "Display" Depth 1 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen&
Bug#171750: xlibs: XftConfig doesn't map sans/serif/mono
Package: xlibs Version: 4.2.1-3 Severity: important Tags: patch -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux hopper 2.2.22 #6 Sat Sep 21 21:00:42 CEST 2002 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages xlibs depends on: ii libc6 2.2.5-14.3 GNU C Library: Shared libraries an ii libfreetype6 2.1.2-9FreeType 2 font engine, shared lib ii xfree86-common4.2.1-3X Window System (XFree86) infrastr the default /etc/X11/XftConfig shipped with xlibs doesn't contain crucial mappings for the default font families. this is effecting many dependant packages. with the current setup any Gtk+-2.0 based application renders text using the wrong font families (e.g. monospaced/fixed text is rendered with a proportional font). in order to fix this, XftConfig needs to a) map "monospace" (which is the fixed width font gtk asks for) to "mono" and b) provide appropriate mappings for the "sans", "serif" and "mono" font families. appended is a sample XftConfig file based on /etc/X11/XftConfig from xlibs-4.2.1-3 which works with any of the three debian font packages ttf-freefont, msttcorefonts or gsfonts-x11, mapping sans, serif and mono to fonts which support varying weights (bold, etc.; not all fonts come in different weights) and which match the requested family: # Debian XftConfig for ttf-freefont, msttcorefonts or gsfonts-x11 # catch fixed X font queries match any family == "fixed" edit family =+ "mono"; # catch terminal font queries match any family == "console" edit family =+ "mono"; # Gtk+ likes to ask for "Monospace" match any family == "monospace" edit family =+ "mono"; # FreeFont TrueType setup (ttf-freefont) dir "/usr/share/fonts/truetype/freefont" # FreeMono*.ttf FreeSans*.ttf FreeSerif*.ttf match any family == "sans" edit family += "FreeSans"; match any family == "serif" edit family += "FreeSerif"; match any family == "mono" edit family += "FreeMono"; # MS TrueType fonts (msttcorefonts) dir "/usr/share/fonts/truetype" # Sans: Arial*.ttf Verdana*.ttf Trebuchet_MS*.ttf Comic_Sans_MS*.ttf Arial_Black.ttf # Serif: Georgia*.ttf Times_New_Roman*.ttf # Mono: Courier_New*.ttf Andale_Mono.ttf # Other: Impact.ttf Webdings.ttf match any family == "sans" edit family += "Arial"; #match any family == "sans" edit family =+ "Verdana"; #match any family == "sans" edit family =+ "Trebuchet MS"; #match any family == "sans" edit family =+ "Comic Sans MS"; match any family == "serif" edit family += "Georgia"; #match any family == "serif"edit family =+ "Times New Roman"; match any family == "mono" edit family += "Courier New"; # Type1 fonts (gsfonts-x11) dir "/usr/X11R6/lib/X11/fonts/Type1" # Sans: Nimbus_Sans_L* URW_Gothic_L* # Serif: Nimbus_Roman_No9_L* URW_Bookman_L* Century_Schoolbook_L* Bitstream_Charter* URW_Palladio_L* # Mono: Nimbus_Mono_L* Courier_10_Pitch* # Script: URW_Chancery_L* match any family == "sans" edit family += "Nimbus Sans L"; match any family == "serif" edit family += "Nimbus Roman No9 L"; #match any family == "mono" edit family += "Nimbus Mono L"; #match any family == "sans" edit family += "URW Gothic L"; #match any family == "serif"edit family += "URW Bookman L"; match any family == "mono" edit family += "Courier 10 Pitch"; # Check users config file # includeif "~/.xftconfig" # # Alias between XLFD families and font file family name, prefer local # fonts # match any family == "charter" edit family += "bitstream charter"; match any family == "bitstream charter" edit family =+ "charter"; -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263073: xserver-xfree86: Super keys now Super+Hyper
Package: xserver-xfree86 Version: 4.3.0.dfsg.1-6 Severity: normal Restarting X following a recent upgrade, I found that my Super (i.e. Win) keys no longer work as before: According to Emacs, keys pressed with them are now both Super- and Hyper-modified, instead of just Super. Since all of my window manager key bindings use Super this is a little inconvenient :-) This is the output from `xmodmap -pm`: shift Shift_L (0x32), Shift_R (0x3e) lockCaps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1Alt_L (0x40), BadKey (0x7d), BadKey (0x9c) mod2Num_Lock (0x4d) mod3 mod4BadKey (0x7f), BadKey (0x80) mod5Mode_switch (0x5d), ISO_Level3_Shift (0x7c) The left and right Win keys have keycodes 115 and 116, generating keysyms Super_L and Super_R. 127 and 128 appear to be "NoSymbol Super_L" and "NoSymbol Hyper_L", so having them both on mod4 seems a little dubious. The keyboard section of XF86Config-4: Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "gb" EndSection Keyboard-related output printed on stderr: (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc105" (**) XKB: model: "pc105" (**) Option "XkbLayout" "gb" (**) XKB: layout: "gb" (==) Keyboard: CustomKeycode disabled -- Package-specific info: -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.25-1-686 Locale: LANG=C, LC_CTYPE=C Versions of packages xserver-xfree86 depends on: ii debconf [debconf-2.0] 1.4.30 Debian configuration management sy ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an ii xserver-common4.3.0.dfsg.1-6 files and utilities common to all ii zlib1g1:1.2.1.1-5compression library - runtime -- debconf information: * xserver-xfree86/config/device/identifier: Gigabyte Radeon 9200SE xserver-xfree86/config/monitor/screen-size: 17 inches (430 mm) xserver-xfree86/config/device/use_fbdev: * xserver-xfree86/config/monitor/selection-method: Medium xserver-xfree86/config/doublequote_in_string_error: shared/default-x-server: xserver-xfree86 * xserver-xfree86/config/inputdevice/mouse/emulate3buttons: false * xserver-xfree86/config/device/bus_id: * xserver-xfree86/config/inputdevice/keyboard/layout: gb xserver-xfree86/config/monitor/horiz-sync: 30-94 * xserver-xfree86/config/monitor/identifier: LS902U * shared/no_known_x-server: * xserver-xfree86/autodetect_mouse: false * xserver-xfree86/config/device/video_ram: * xserver-xfree86/config/monitor/mode-list: 1600x1200 @ 75Hz * xserver-xfree86/config/monitor/lcd: false xserver-xfree86/config/inputdevice/keyboard/internal: * xserver-xfree86/config/inputdevice/keyboard/rules: xfree86 xserver-xfree86/multiple_possible_x-drivers: * xserver-xfree86/config/inputdevice/keyboard/model: pc105 * xserver-xfree86/config/write_dri_section: true * xserver-xfree86/config/device/driver: ati xserver-xfree86/config/monitor/vert-refresh: 50-75 * xserver-xfree86/config/display/default_depth: 24 * xserver-xfree86/config/inputdevice/mouse/zaxismapping: false * xserver-xfree86/config/display/modes: 1600x1200, 1024x768, 800x600, 640x480 xserver-xfree86/config/device/bus_id_error: * xserver-xfree86/config/modules: GLcore, bitmap, dbe, ddc, dri, extmod, freetype, glx, int10, record, speedo, type1, vbe * xserver-xfree86/config/inputdevice/keyboard/options: xserver-xfree86/config/nonnumeric_string_error: * xserver-xfree86/config/inputdevice/mouse/protocol: PS/2 shared/multiple_possible_x-servers: xserver-xfree86/config/null_string_error: xserver-xfree86/config/monitor/range_input_error: * xserver-xfree86/autodetect_video_card: true * xserver-xfree86/config/inputdevice/keyboard/variant: * xserver-xfree86/config/inputdevice/mouse/port: /dev/psaux * xserver-xfree86/config/write_files_section: true * xserver-xfree86/autodetect_monitor: true
Bug#270597: /usr/X11R6/bin/xbiff: request ability to temporarily disable xbiff
Package: xbase-clients Version: 4.3.0.dfsg.1-6 Severity: wishlist File: /usr/X11R6/bin/xbiff Having just come back from a time management seminar, I've decided I need the ability to temporarily shut off xbiff (I should also kill our USENET feed, too). I start xbiff within my FvwmButtons, and it automatically respawns if somethign goes wrong (the ssh connection dies, etc). So in a bid for more procrastination, I decided I could have a button to do: `killall -STOP xbiff` Unfortunately, this did not work, with FvwmButtons somehow deciding it had to spawn another xbiff. So my next plan for procrastination involves writing this feature request (if I get really bored, I can code it up too :). My ideas were perhaps having xbiff check for the presence of a file, say $HOME/.xbiff-disable, at poll time, and if there, skip over the mail check, and go back to polling. Does this sound like a worthwhile thing to include in xbiff? Is there perhaps a more elegant method that I haven't thought of, that would be a better way of implementing this? -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.26 Locale: LANG=en_AU, LC_CTYPE=en_AU Versions of packages xbase-clients depends on: ii cpp 4:3.3.4-2 The GNU C preprocessor (cpp) ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an ii libdps1 4.3.0.dfsg.1-6 Display PostScript (DPS) client li ii libexpat1 1.95.6-8 XML parsing C library - runtime li ii libfontconfig12.2.3-1generic font configuration library ii libfreetype6 2.1.7-2.2 FreeType 2 font engine, shared lib ii libice6 4.3.0.dfsg.1-6 Inter-Client Exchange library ii libncurses5 5.4-4 Shared libraries for terminal hand ii libpng12-01.2.5.0-7 PNG library - runtime ii libsm64.3.0.dfsg.1-6 X Window System Session Management ii libstdc++51:3.3.4-9 The GNU Standard C++ Library v3 ii libxaw7 4.3.0.dfsg.1-6 X Athena widget set library ii libxcursor1 1.1.3-1X cursor management library ii libxext6 4.3.0.dfsg.1-6 X Window System miscellaneous exte ii libxft2 2.1.2-6FreeType-based font drawing librar ii libxi64.3.0.dfsg.1-6 X Window System Input extension li ii libxmu6 4.3.0.dfsg.1-6 X Window System miscellaneous util ii libxmuu1 4.3.0.dfsg.1-6 lightweight X Window System miscel ii libxpm4 4.3.0.dfsg.1-6 X pixmap library ii libxrandr24.3.0.dfsg.1-6 X Window System Resize, Rotate and ii libxrender1 0.8.3-7X Rendering Extension client libra ii libxt64.3.0.dfsg.1-6 X Toolkit Intrinsics ii libxtrap6 4.3.0.dfsg.1-6 X Window System protocol-trapping ii libxtst6 4.3.0.dfsg.1-6 X Window System event recording an ii libxv14.3.0.dfsg.1-6 X Window System video extension li ii xlibmesa-gl [libgl1] 4.3.0.dfsg.1-6 Mesa 3D graphics library [XFree86] ii xlibmesa-glu [libglu1]4.3.0.dfsg.1-6 Mesa OpenGL utility library [XFree ii xlibs 4.3.0.dfsg.1-6 X Window System client libraries m ii xlibs-data4.3.0.dfsg.1-6 X Window System client data ii zlib1g1:1.2.1.1-5compression library - runtime -- no debconf information
Bug#263073: xlibs: Super still Super+Hyper
Sorry, 263073 is not fixed in the latest version. The only improvement
is that xmodmap's output is more helpful now:
shift Shift_L (0x32), Shift_R (0x3e)
lockCaps_Lock (0x42)
control Control_L (0x25), Control_R (0x6d)
mod1Alt_L (0x40), Alt_L (0x7d), Meta_L (0x9c)
mod2Num_Lock (0x4d)
mod3
mod4Super_L (0x7f), Hyper_L (0x80)
mod5Mode_switch (0x5d), ISO_Level3_Shift (0x7c)
I'm still seeing the same symptoms in Sawfish and Emacs. I tried adding
altwin:super_win, as suggested in 271259; it added Super_{L,R} to mod4:
mod4Super_L (0x73), Super_R (0x74), Super_L (0x7f), Hyper_L (0x80)
but the problem persists. Removing 0x80 from mod4 with xmodmap does
"fix" it.
Tim Bagot
Bug#263073: xlibs: Super still Super+Hyper
Sorry, my steps to reproduce weren't exactly very detailed. I'll try again: Sawfish: From Gnome, go to Desktop Preferences, Windows; Bindings tab. Set default modifier to super. (Should take effect immediately.) Try e.g. Win-TAB. Set to hyper, and try again. Emacs: Type C-h c Win-
Bug#263073: xlibs: Super still Super+Hyper
[EMAIL PROTECTED] (Denis Barbier) writes: > Can you please be more specific, how can this bug be reproduced both in > Sawfish and Emacs (with full instructions for people installing these > software for the first time)? If you are running GNOME, you may read > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=271259 Already read 271259 - it's in the bit you snipped. (BTW, /etc/X11/xkb/rules/xfree86.lst seems to need updating - altwin:super_win isn't there.) Sawfish: W- bindings (e.g. W-TAB) do not work with the default modifier set to super. (Oddly, they do work with it set to hyper, even though the keys are generating Super_L/R keysyms and mod4 includes both Super and Hyper.) Directly Super-modified bindings also do not work (and again Hyper does). Emacs: Keys pressed with a Windows key are reported as H-s- instead of just s-. Tim Bagot
Bug#263073: xlibs: Super still Super+Hyper
Christian Marillat <[EMAIL PROTECTED]> writes: > Tim could you try to reconfigure your keyboard in the control center ? > Keyborad icon and layouts tab. The layout is set correctly (generic 105-key, UK). There were no layout options selected. Adding "Super is mapped to the Win-keys (default)." didn't seem to do anything. I see the problem with Emacs if I run it in a "bare" second X session. Would it be worth my trying the same with Sawfish? Tim Bagot
Bug#240769: xlibs causing removal of j2sdk1.3, xv, et cetera?
Package: xlibs
Version: 4.3.0-7
Severity: important
I suspect that the xlibs upgrade in testing is going to cause a
substantial number of old programs to be deleted, including xv and
Java 1.3. At least those two are important to me, hence the severity.
I am using the testing release. (Whether this is sarge, woody, sid,
potato, or priceofteainchina, I don't know and don't know how to find
out.) I did an apt-get -yud dist-upgrade
The result:
The following packages will be REMOVED:
communicator-base-473 communicator-nethelp-473
communicator-smotif-473 communicator-spellchk-473
fonttastic-glibc-2.1 gwm j2sdk1.3 kaffe libwraster1 netscape-base-4
netscape-base-473 netscape-java-473 netscape-smotif-473
wine-wpo2000-glibc-2.1 wpo2000-minimal wpo2000-minimal-std xf86setup
xlib6g xproxy xv
The following NEW packages will be installed:
lam4 libice6 libsm6 libx11-6 libxext6 libxft1 libxi6 libxmu6
libxmuu1 libxp6 libxpm4 libxrandr2 libxt6 libxtrap6 libxtst6 libxv1
xlibs-data
The following packages will be upgraded:
apt apt-utils blacs-mpich-dev blacs1-lam blacs1-mpich doc-linux-html
doc-linux-text eject iptables lam-runtime libdb4.1 libdps1
libgpg-error0 libhdf5-serial-1.6.1-0 libmetacity0 libxaw6 libxaw7
libxcursor1 libxft2 libxrender1 metacity netpipe-lam netpipe-mpich
netpipe-pvm netpipe-tcp scalapack-mpich-dev scalapack1-lam
scalapack1-mpich scalapack1-pvm twm xbase-clients xdm xfonts-100dpi
xfonts-75dpi xfonts-base xfonts-cyrillic xfonts-scalable
xfree86-common xfs xlibs xmh xnest xprt xserver-common xterm xutils
xvfb
Note the large list of packages to be removed, including xlib6g (which
apparently a number of other packages depend on),
fonttastic-glibc-2.1, j2sdk1.3, xf86setup, xv, et cetera.
By going into dselect manually, I see
Dependency/conflict resolution - introduction.
One or more of your choices have raised a conflict or dependency
problem - ...
xlib6g's conflicts are listed as
xlibs conflicts with xlib6g
libwraster1 depends on xlib6g (>= 3.3.6-4)
fonttastic-glibc-2.1 depends on xlib6g (>= 3.3.5-1)
j2sdk1.3 depends on xlib6g (>= 3.3.6-4)
xv depends on xlib6g (>= 3.3.6)
communicator-smotif-473 depends on xlib6g (>= 3.3.6-4)
wine-wpo2000-glibc-2.1 depends on xlib6g (>= 3.3.5-1)
xf86setup depends on xlib6g (>= 3.3.6-4)
xproxy depends on xlib6g (>= 3.3.6-4)
netscape-base-4 depends on xlib6g (>= 3.3.6-4)
kaffe depends on xlib6g (>= 3.3.6)
gwm depends on xlib6g (>= 3.3.5)
but xlibs says just
xlibs conflicts with xlib6g
dselect reports xlibs as being Inst.ver 4.2.1-12.1 and Avail.ver
4.3.0-7, and
xlibs - X Window System client libraries metapackage and XKB data
This package smooths upgrades from Debian 3.0 by depending on the
individual library packages into which each shared object formerly
contained in this package has been split.
This package is only depended upon by packages that haven't yet
been compiled against the new shared library packages. ...
xlib6g says Inst.ver and Avail.ver are both 4.2.1-3, and
xlib6g - pseudopackage providing X libraries
This package smooths the migration from Debian 2.2 by depending on
xlibs and libxaw6. This pseudopackage is only depended upon by
packages that haven't yet been compiled against the newer X
library packages.
This package also conflicts with packages that are no longer
supported in Debian and do not comply with the Debian app-defaults
policy. (In some cases, the functionality of these old packages
has been absorbed into other packages in Debian 3.0 ("woody").)
I don't know what the state of the packages was before this apt-get --
I am not familiar with the apt/dpkg/dselect system. My guess is that
the latest xlibs update in testing now says that it conflicts with
xlib6g, so dselect/apt-get decided that it needs to get rid of xlib6g
and everything that depends on it.
I was taken aback at the number of packages to be lost. Though many
of those packages are obsolete or things that I don't use (so far as I
know), I would much rather not lose xv and Java 1.3 (and possibly
kaffe), at least. Netscape 4.73 is nice for compatibility testing.
Is it really necessary for Debian (or very useful) to blow them out of
the water?
--
Tim McDaniel (home); Reply-To: [EMAIL PROTECTED]; work is [EMAIL PROTECTED]
Bug#243314: xterm scrolling speed patch on LKML for 2.6
Package: xterm Version: 4.3.0-7 Severity: normal Please include the analagous patch that suggested and tested here (for multi-gnome-terminal) into xterm (and send upstream - why didn't reportbug ask me the upstream question this time?): http://www.uwsg.iu.edu/hypermail/linux/kernel/0404.0/0467.html In kernel 2.6, the scheduler changes have uncovered a bug in xterm that make the scrolling speed hideously slow[1] because it causes xterm to output one character at a time in a busy loop instead of jump scrolling. This will affect all terminals based on xterm, which is well, all of them. Presumably upstream will include this, but they don't seem to have done so yet[2][3], so I am submitting this bug report. [1] To demonstrate, open up an xterm to maximised, `ls -trlA --color` a big directory - say the 500 files in your home directory. See how slow. Now pipe the same through `cat` or `dd`, and see how quick. You may need a slow (~500MHz) computer to appreciate the full effect of just how hideous this is (6-10 seconds on my machine). [2] At least, xterm is still as slow as normal for me, but I can't download the xterm sources myself and verify yet, because hey, 50MB [3] the poster of the patch said it was in debian unstable already - I presume he meant only for gnome-terminal, because I just upgraded to test for the existance of this patch -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.4 Locale: LANG=en_AU, LC_CTYPE=en_AU Versions of packages xterm depends on: ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libexpat1 1.95.6-8 XML parsing C library - runtime li ii libfontconfig1 2.2.2-1 generic font configuration library ii libfreetype62.1.7-2 FreeType 2 font engine, shared lib ii libice6 4.3.0-7 Inter-Client Exchange library ii libncurses5 5.4-2Shared libraries for terminal hand ii libsm6 4.3.0-7 X Window System Session Management ii libxaw7 4.3.0-7 X Athena widget set library ii libxext64.3.0-7 X Window System miscellaneous exte ii libxft2 2.1.2-5 FreeType-based font drawing librar ii libxmu6 4.3.0-7 X Window System miscellaneous util ii libxpm4 4.3.0-7 X pixmap library ii libxrender1 0.8.3-5 X Rendering Extension client libra ii libxt6 4.3.0-7 X Toolkit Intrinsics ii xlibs 4.3.0-7 X Window System client libraries m ii xlibs-data 4.3.0-7 X Window System client data -- debconf information: * xterm/clobber_xresource_file: true xterm/xterm_needs_devpts:
Bug#250617: xbase-clients: [xbiff] wishlist: beep mute
Package: xbase-clients Version: 4.3.0-7 Severity: wishlist I wish to be able to turn the xbiff beep off on one of my machines (without disabling the speaker entirely), and just let xbiff invert the bitmap colour when mail is received. Xbiff has a volume setting that doesn't work for i386 (beep never seems to have had a working volume control on any machines I use), so I can't just set the volume to 0%. Perhaps there should be an option to xbiff to not try to beep the speaker at all. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.25-pre7 Locale: LANG=en_AU, LC_CTYPE=en_AU Versions of packages xbase-clients depends on: ii cpp 4:3.3.3-2The GNU C preprocessor (cpp) ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdps1 4.3.0-7 Display PostScript (DPS) client li ii libexpat1 1.95.6-8 XML parsing C library - runtime li ii libfontconfig1 2.2.2-2 generic font configuration library ii libfreetype62.1.7-2 FreeType 2 font engine, shared lib ii libice6 4.3.0-7 Inter-Client Exchange library ii libncurses5 5.4-3Shared libraries for terminal hand ii libpng12-0 1.2.5.0-5PNG library - runtime ii libsm6 4.3.0-7 X Window System Session Management ii libstdc++5 1:3.3.3-6The GNU Standard C++ Library v3 ii libxaw7 4.3.0-7 X Athena widget set library ii libxcursor1 1.0.2-5 X Cursor management library ii libxext64.3.0-7 X Window System miscellaneous exte ii libxft2 2.1.2-6 FreeType-based font drawing librar ii libxi6 4.3.0-7 X Window System Input extension li ii libxmu6 4.3.0-7 X Window System miscellaneous util ii libxmuu14.3.0-7 lightweight X Window System miscel ii libxpm4 4.3.0-7 X pixmap library ii libxrandr2 4.3.0-7 X Window System Resize, Rotate and ii libxrender1 0.8.3-7 X Rendering Extension client libra ii libxt6 4.3.0-7 X Toolkit Intrinsics ii libxtrap6 4.3.0-7 X Window System protocol-trapping ii libxtst64.3.0-7 X Window System event recording an ii libxv1 4.3.0-7 X Window System video extension li ii xlibmesa-gl [libgl1]4.3.0-7 Mesa 3D graphics library [XFree86] ii xlibmesa-glu [libglu1] 4.3.0-7 Mesa OpenGL utility library [XFree ii xlibs 4.3.0-7 X Window System client libraries m ii xlibs-data 4.3.0-7 X Window System client data ii zlib1g 1:1.2.1-5compression library - runtime -- no debconf information
Bug#256344: xserver-xfree86: [vesa] SEGV selecting 'tixus' or 'drift' fonts
Package: xserver-xfree86 Version: 4.1.0-16woody3 Severity: normal The X server immediately and reliably crashes when I select either font 'Drift' or 'Tixus' (from xfonts-artwiz 1.4) in a Tcl/Tk client (Trebuchet, a MUD client). It seems that the rendering in the preview pane causes this. I normally use the NVIDIA driver, so I switched to the VESA driver and the crash still happens. If I select 'tixus' in Galeon it doesn't crash, so perhaps this is a missing range-check in the font system? The XFree log is here: http://www.baverstock.org.uk/tim/debian xfonts-artwiz depends on: ii xutils4.1.0-16woody3 X Window System utility programs tk8.3 depends on: ii libc6 2.2.5-11.5 GNU C Library: Shared libraries an ii tcl8.38.3.3-7The Tool Command Language (TCL) v8 ii xlibs 4.1.0-16woody3 X Window System client libraries -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux cardinal 2.4.18.20040523 #1 Sat Apr 24 01:30:06 BST 2004 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages xserver-xfree86 depends on: ii debconf1.0.32Debian configuration management sy ii libc6 2.2.5-11.5GNU C Library: Shared libraries an ii xserver-common 4.1.0-16woody3files and utilities common to all ii zlib1g 1:1.1.4-1.0woody0 compression library - runtime
Roll your own X Packages problem with static libraries
Hi I am just tring to get some CVS-Head, which i injected into the experimental XFree Packages debianized. I managed to compile and install, but when i make an "debian/rules binary-arch". I get the following message: dh_install --sourcedir=debian/tmp cp: cannot stat `debian/tmp//usr/X11R6/lib/libdps.a': No such file or directory dh_install: command returned error code 256 make: *** [stampdir/binary-arch] Error 1 The problem is that there is no libdps.a build (but .so one are there!). So here comes the question to the x-wizards on the list, are there any configure options to get these static libraries built? Please cc me, since i am currently not subscribed to this list. Thanks for any suggestions Tim
Re: Roll your own X Packages problem with static libraries
Hi Branden Thanks for your answer. > This is more a question for one of XFree86 upstream's mailing lists. > > Anyway, I believe the Imake variable in question is "ForceNormalLib", or > something similar to that. That was the ticket. I was a little impatient and already posted to the xfree mailinglist. Marc gave me the same answer and it worked :) (http://www.mail-archive.com/devel@xfree86.org/msg04023.html) debian/rules install seems to work now. However debian/rules install-server failes to install because of missing chooser. I tried to apply patches 900_debian_config.diff 905_debian_xdm.diff to relocate the chooser but then wraphelp.c is beeing missed while building. (I didn't apply any other packages.). So if you have a suggestion (without digging to much) i would apreciate that. But right now i am to tiered... Thanks Tim
Re: Roll your own X Packages problem with static libraries
Hi > Anyway, I believe the Imake variable in question is "ForceNormalLib", or > something similar to that. Ok, after digging around much to long, i found that the patches: 900_debian_config.diff 901_Wraphelp.c.diff of experimental do the job nicely. No more problems currently, but the build is currently running. Does anybody know if there is a way to parallize the build process. I have a dual xeon box here and it seems to me as if only one processor is working with compiling? Tim
Publishing xfree 4.3.99 debs
Hi Branden > Anyway, I believe the Imake variable in question is "ForceNormalLib", or > something similar to that. This was the ticket to get me some running xfree86 4.4 (well 4.3.99-16 cvs from nov 1.) deb packages built. Is there something i have to pay attention to, when i am packaging non-offical packages? If there is no problem, i would publish the packages on apt-get.org or so? Since i ripped of the experimental packages there are a lot of mail etc from the x-stike-force in the package. The changelog makes however clear that these are not official packages. Cheers Tim
Bug#224353: /usr/X11R6/bin/xclock: xclock man page and options deficiencies
Package: xbase-clients Version: 4.3.0-0pre1v4 Severity: normal File: /usr/X11R6/bin/xclock xclock --help shows there is a -face argument The man page does not include -face, so I have little idea how to use it (similarly, the options -sharp/-render are not in the man page) Supplyng -face "Times New Roman" etc seems to work. There unfortunately seems not to be an asscoiated font size argument, as in the -fa and -fs args to xterm, so the text is way too big on my machine. man page also includes the font resource, but an entry of XClock.clock.font: -*-helvetica-medium-r-*-*-*-120-* seems to do nothing. Nor does the -fn option explained in the --help: xclock -fn '-*-helvetica-medium-r-*-*-*-120-*' -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux scuzzie 2.4.22 #1 Thu Nov 20 21:17:49 EST 2003 i686 Locale: LANG=en_AU, LC_CTYPE=en_AU Versions of packages xbase-clients depends on: ii cpp-3.2 1:3.2.3-8 The GNU C preprocessor ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an ii libdps1 4.2.1-14 Display PostScript (DPS) client li ii libexpat1 1.95.6-6 XML parsing C library - runtime li ii libfontconfig12.2.1-12 generic font configuration library ii libfreetype6 2.1.7-1FreeType 2 font engine, shared lib ii libncurses5 5.3.20030719-4 Shared libraries for terminal hand ii libpng12-01.2.5.0-4 PNG library - runtime ii libstdc++51:3.3.2-4 The GNU Standard C++ Library v3 ii libxaw7 4.2.1-14 X Athena widget set library ii libxcursor1 1.0.2-2X Cursor management library ii libxft2 2.1.2-5FreeType-based font drawing librar ii libxrender1 0.8.3-4X Rendering Extension client libra ii xlibmesa-gl [libgl1] 4.3.0-0pre1v4 Mesa 3D graphics library [XFree86] ii xlibmesa-glu [libglu1]4.3.0-0pre1v4 Mesa OpenGL utility library [XFree ii xlibs [libxpm4] 4.3.0-0pre1v4 X Window System client libraries ii zlib1g1:1.2.1-2 compression library - runtime -- no debconf information
Bug#434833: Spontaneous reboots on suspend-to-RAM with new Xorg "intel" driver
I must note that I do have the "composite" extension enabled. If I disable composite, I see these issues occur much less frequetly. On 7/27/07, Julien Cristau <[EMAIL PROTECTED]> wrote: > > On Thu, Jul 26, 2007 at 23:27:51 -0400, Tim Hull wrote: > > > When using the new "intel" video driver that replaced the former "i810" > > driver in Debian, I am experiencing spontaneous reboots randomly on > > suspend-to-RAM. > > What are you using for suspend/resume? > > > Right before the system spontaneously reboots, I see a checkered pattern > on > > a black-and-white console display. At times, though rare, I have also > seen > > similar crashes when stopping and restarting the X server manually - > which > > leads me to believe that starting/stopping the X server is what is > causing > > the issue. I have no such problem when using 915resolution and the old > i810 > > driver in Etch and on Ubuntu Feisty (their stable), but do see the same > > problem on Ubuntu Gutsy (their unstable) which uses the intel > driver. While > > it doesn't occur every time I suspend, it occurs often enough that this > is a > > MAJOR annoyance for me. I'm marking this as RC, as such crashes DO > cause > > data loss in open files - you're free to disagree with me, though... > > That's not what data loss means. > > > System configuration is a MacBook Core Duo (first generation) with 2GB > RAM > > and Debian Sid. > > I've attached my xorg.conf and appropriate logs... > > Thanks, > Julien > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGqclAmEvTgKxfcAwRAkL/AKCKOW6jyvcqKMCG0kOCqORzevVkRQCfYZdK > vj3gLM/cmygo5gkhzurvph8= > =6eET > -END PGP SIGNATURE- > >
Bug#434833: Spontaneous reboots on suspend-to-RAM with new Xorg "intel" driver
Actually, I don't think it happens at all - at least I can't reproduce it as of now without composite. So this seems to be an issue between composite (and/or additional settings needed to get it working) and the new mode-setting driver (it didn't happen w/i810+915resolution). On 8/9/07, Brice Goglin <[EMAIL PROTECTED]> wrote: > > Tim Hull wrote: > > I must note that I do have the "composite" extension enabled. If I > > disable composite, I see these issues occur much less frequetly. > > > > Less frequency or not at all? > > Brice > >
Bug#434833: Spontaneous reboots on suspend-to-RAM with new Xorg "intel" driver
I guess I was wrong - it just happened without composite. So I guess it's completely random, other than the fact that it freezes/reboots at random times when: * I switch from X to console * I suspend/resume the machine * I kill the X server (Ctrl-Alt-Backspace) with the new modesetting "intel" driver. This did not happen with i810+915resolution. Before freezing/rebooting, the console always displays a checkerboard pattern. On 8/9/07, Tim Hull <[EMAIL PROTECTED]> wrote: > > Actually, I don't think it happens at all - at least I can't reproduce it > as of now without composite. So this seems to be an issue between composite > (and/or additional settings needed to get it working) and the new > mode-setting driver (it didn't happen w/i810+915resolution). > > On 8/9/07, Brice Goglin <[EMAIL PROTECTED]> wrote: > > > > Tim Hull wrote: > > > I must note that I do have the "composite" extension enabled. If I > > > disable composite, I see these issues occur much less frequetly. > > > > > > > Less frequency or not at all? > > > > Brice > > > > >
Bug#437009: No window borders in latest Compiz
Package: compiz Version: 0.5.0.dfsg-2 Priority: important On Debian sid with the latest Compiz and X installed, running compiz --replace with an active Gnome/Metacity session results in there being no window borders. Compiz effects (cube, window effects, alt+tab, etc) all work, but none of my windows have window borders. I even tried unregistering the /apps/compiz settings in gconf, but it still doesn't work - hence Compiz is basically unusable. I'm using a MacBook with Intel GMA 950 graphics and the X.org "intel" driver. No such problems were experienced with Compiz with the same system in Etch.
Bug#437009: No window borders in latest Compiz
> > > Any warning? > > Is gtk-window-decorator running after starting compiz? if so, kill it > and compiz --replace again and again? > > Brice > > The warnings I got were: GLX_EXT_texture_from_pixmap is not available with direct rendering. GLX_EXT_texture_from_pixmap is available with indirect rendering. gtk-window-decorator IS running after I do compiz --replace, and if I kill it and run compiz --replace again, I initially lose the borders. However, if I do compiz --replace a third time, I get the borders to appear. However, only some applications - and not all - get borders. In particular, newly-launched applications (after Compiz is run) never acquire borders, and tend to start in the top left-most corner of the screen rather than the middle of the screen.
Bug#434833: Issue with X rebooting system/new "intel" driver
Hi, Is there any progress on this issue (spontaneous rebooting in X with the "intel" driver)? I'm experiencing this on both Debian and Ubuntu with said driver, so it definitely is an upstream issue. Has an upstream bug been filed? I'm not acquainted with X.org's bug reporting system myself... In the meantime, is there a place I can get the latest version of the old i810 driver? xserver-xorg-video-i810 in both testing and unstable is simply a transitional package. In my case, if I use i810+915resolution, I have no issues whatsoever with X and spontaneous rebooting. Tim
Fontconfig and making Debian's fonts look better...
(Please cc me on any replies - I don't currently subscribe to all the lists) Hi, I've been using Debian as well as other distributions and one thing I can't help but notice - especially on Debian - is that the default fontconfig settings leave a little bit to be desired. Granted, X will likely never have fonts which look as good as, say, OS X (mostly because of patents), but there is still many improvements that could be made to the default configuration that would make the fonts look noticeably better out-of-the-box. In particular, I wanted to raise the following issues: 1. First of all, the AMT and URW fonts substituted for the MS core fonts (in their absence) are - in a word - ugly. This was something I noticed right away when using Debian - other distributions don't use these fonts. In fact, Ubuntu has patched Debian's fontconfig defaults (located in /etc/fonts/conf.d) to *not* use these fonts if an application accepts any metrics - which results in it using DejaVu Sans/DejaVu Serif instead in most cases. Could these AMT/URW substitutions possibly be removed from the default configuration? Ideally we'd just use Red Hat's Liberation, but they still don't have their license issues sorted out... 2. Secondly, by default Debian currently has bitmap fonts enabled in fontconfig. While this allows said fonts to be used, it *also* has significant negative effects - at least with the default bitmap fonts for X installed. In particular, this basically involves common fonts with bitmap versions - if Helvetica is requested by a document, ugly bitmap Helvetica is used instead of a better-looking TrueType font. Could something be done about this in the defaults, either by removing bitmap versions of commonly-used X fonts from the standard X install metapackage or by disabling bitmaps entirely by default (as Ubuntu has done)? 3. Lastly, and most controversially, I have always noticed that with some fonts, turning the autohinter on makes them look MUCH better. However, by default the autohinter is turned off. I can see why - some fonts, especially from non-Latin character sets, have been known to look quite bad with the autohinter on. However, I am wondering - would it be worth considering to have fontconfig turn the autohinter on for a whitelist of fonts known to work well with it? Just throwing out some ideas... Tim
Bug#439183: Upgrade to 1.0.4-1 freezes X
Package: xtrans-dev Version: 1.0.4-1 Severity: serious --- Please enter the report below this line. --- Upgrading from 1.0.3-2 results in total freeze of system. Only rebootable by power cycle. On restart of X, again frozen, but can now ctrl-alt-f1, downgrade xtrans-dev (using snapshot.debian.net), restart X and back to usable. --- System information. --- Architecture: i386 Kernel: Linux 2.6.21-2-686 Debian Release: lenny/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#439183: Upgrade to 1.0.4-1 freezes X
Hi Julien, Julien Cristau wrote: None of these files are used at runtime, so there is no way in hell an xtrans upgrade is going to screw your system. Please run /usr/share/bug/xserver-xorg-core/script 3>&1 and send the output to this bug. It gives no output. Maybe I reported the bug in haste, but now I'm at a loss to explain the cause of the freeze. I just upgraded again to try to reproduce the bug, and succeeded (to upgrade - or failed to reproduce the bug, depending on your point of view). The other packages that were upgraded at the same time (see excerpt from /var/log/aptitude below) don't appear a likely cause, and as I say the downgrade fixed the problem. Anyway, feel free to close. Cheers Tim === [REMOVE, NOT USED] libavahi-compat-howl0 [UPGRADE] libmailtools-perl 1.74-1 -> 1.77-0 [UPGRADE] libxmmsclient-glib1 0.2DrJekyll-4 -> 0.2DrJekyll-4+b1 [UPGRADE] libxmmsclient2 0.2DrJekyll-4 -> 0.2DrJekyll-4+b1 [UPGRADE] pidgin 2.1.0-1 -> 2.1.1-1 [UPGRADE] pidgin-data 2.1.0-1 -> 2.1.1-1 [UPGRADE] powertop 1.7~svn-r227-3 -> 1.8-1 [UPGRADE] xmms2-client-cli 0.2DrJekyll-4 -> 0.2DrJekyll-4+b1 [UPGRADE] xmms2-core 0.2DrJekyll-4 -> 0.2DrJekyll-4+b1 [UPGRADE] xmms2-plugin-alsa 0.2DrJekyll-4 -> 0.2DrJekyll-4+b1 [UPGRADE] xmms2-plugin-id3v2 0.2DrJekyll-4 -> 0.2DrJekyll-4+b1 [UPGRADE] xmms2-plugin-mad 0.2DrJekyll-4 -> 0.2DrJekyll-4+b1 [UPGRADE] xmms2-plugin-vorbis 0.2DrJekyll-4 -> 0.2DrJekyll-4+b1 [UPGRADE] xtrans-dev 1.0.3-2 -> 1.0.4-1 === -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437009: No window borders in latest Compiz
I figure that's the issue for me - though I don't have access to a Lenny/Sid machine to test it at the moment. You can go ahead and close this if you wish... On 8/24/07, Sven Arvidsson <[EMAIL PROTECTED]> wrote: > > On Fri, 2007-08-24 at 22:14 +0200, Brice Goglin wrote: > > So the actual original bug would just be that the decoration plugin > > isn't loaded by default? If so, great, it's easy to fix. As I said in > > http://bgoglin.livejournal.com/11253.html, _lots_ of plugins have to be > > enabled manually to get something interesting in Compiz. > > I did read that post, but I guess I expected at least some basic plugins > by default (functionality similar to metacity, only with compositing). > > If that's not possible, at the very least should README.Debian be > updated, as it now reads; > > $ compiz --replace & > > Which will start compiz, make it replace the current window > manager and > background the process so you can safely close the terminal again. > If all went > well, compiz should start up and enable a whole bunch of desktop > effects. > > -- > Cheers, > Sven Arvidsson > http://www.whiz.se > PGP Key ID 760BDD22 > >
Re: Bug#826018: installation-reports: Stretch Alpha 6 successful installation, but no touchpad during install
Sure! Attached is my /var/log/installer/syslog file compressed with xz. Tim On Fri, Jun 3, 2016 at 8:53 PM, Cyril Brulebois wrote: > Hi Tim, > > Tim Heaney (2016-06-01): > > Dear Maintainer, > > > > My install was successful and I am very happy as described here > > > > https://oylenshpeegul.wordpress.com/2016/05/31/hello-stretch/ > > > > The only issue I've had so far was tiny. During the install, the > > touchpad was dead. I plugged in a usb mouse and proceeded. When the > > install was complete and I booted into debian from the hard disk, the > > touchpad worked. I didn't do anything to fix it. > > > > Thanks to everyone on the Debian team! The Stretch Alpha 6 installer > > looks like a winner! > > Thanks for your report. Can you please attach your installer's sylog > file (maybe compressed) in a group-reply? It can be found under the > /var/log/installer directory. > > > /proc/bus/input/devices: I: Bus=0011 Vendor=0002 Product=0007 > Version=01b1 > > /proc/bus/input/devices: N: Name="SynPS/2 Synaptics TouchPad" > > /proc/bus/input/devices: P: Phys=isa0060/serio1/input0 > > /proc/bus/input/devices: S: > Sysfs=/devices/platform/i8042/serio1/input/input2 > > /proc/bus/input/devices: U: Uniq= > > /proc/bus/input/devices: H: Handlers=mouse0 event3 > > /proc/bus/input/devices: B: PROP=9 > > /proc/bus/input/devices: B: EV=b > > /proc/bus/input/devices: B: KEY=6420 3 0 0 0 0 > > /proc/bus/input/devices: B: ABS=26080001103 > > I would expect a synaptics touchpad to get at least basic support with > evdev, and maybe there's a bug somwhere to be fixed. But maybe I'm out > of sync with reality. :) > > Also, wondering whether it would make sense to maybe have a synaptics > udeb at some point? Or maybe libinput will save us all? > > Putting -x@ in cc for input (no pun intended). > > > KiBi. > syslog.xz Description: application/xz
Bug#787241: xserver-xorg-video-intel: VT never returns from powersave on Haswell
Package: xserver-xorg-video-intel Followup-For: Bug #787241 Could you try: . Switch to VT . Log in as same use as X session on VT . run 'sleep 6 ; DISPLAY=:0 xrandr' on VT . switch to X VT before 6 seconds have elapsed, then switch back after 6 seconds have elapsed . Check output to see what mode your display is reporting . Possibly fix with 'xrandr --display FOO --auto' ?
Bug#778991: picture of the problem
signature.asc Description: This is a digitally signed message part
Bug#778991:
This happens not every time but always after reboot und often after suspend. signature.asc Description: This is a digitally signed message part
Bug#778991:
Thanks, I can try it. But: The animations in Gnome shell in Debian are smoother than in other distributions like Fedora or Archlinux, which are using a recent driver – I tested a lot configuration like tearfree or sna. It sounds crazy but the "old" Debian driver in combination with UXA seems to increase animation speed. I'm a little bit afraid to change the xorg-driver. signature.asc Description: This is a digitally signed message part
Bug#778991:
Okay, after generating /usr/share/X11/xorg.conf.d/20-intel.conf with the following content... Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" EndSection ...the problem is solved. This workaround results in little tearing. Adding the tearfree option doesn't help and results in stuttering. So ist definitly a video-intel bug. signature.asc Description: This is a digitally signed message part
Bug#778991: conclusion
I opened a bug report her: https://bugs.freedesktop.org/show_bug.cgi?id=89291 -The problem affects only ivybridge. -The problem is gone after activating sna acceleration. With -intel-2.21.15 from testing I recognized other bugs (e.g. big shadows under the nautilus window). -With -intel-2.99.917 from experimental only activating TearFree (perhaps i915.semaphore) results in smooth animations. I think it's not a major but annoying bug. All machines with ivybridge are infected. There isn't a solution with the actual driver in stable, testing or sid. The only workaround is fiddling around with experimental and some modifications in /xorg.conf.d. signature.asc Description: This is a digitally signed message part
Bug#785940: xserver-xorg: xserver fails to start cannot read int vect
Package: xserver-xorg Version: 1:7.7+9 Severity: important Dear Maintainer, Updating to 1.17.1 renders xserver unable to start for some using VESA. It appears that a patch is in the ubuntu repositories but has not yet made it back to debian. Link below https://launchpad.net/ubuntu/+source/xorg-server/2:1.17.1-0ubuntu3 -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Feb 5 2014 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2384712 May 4 18:24 /usr/bin/Xorg Diversions concerning libGL are in place diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by glx-diversions diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/mes
Bug#348873: regression: r128 on laptop ignores supplied modeline for external display, picking LCD panel pixel dimensions
On Tue, 19 Jun 2007, Brice Goglin wrote: > Hi, > > About a year ago, you reported a bug to the Debian BTS regarding > modelines for external display being ignored with a ATI R128 board. Did > you reproduce this problem recently? With Xorg/Etch? With latest > xserver-xorg-core and drivers? If not, I will close this bug in the next > weeks. Yep, latest sid. xdpyinfo still reports: dimensions:1024x768 pixels (321x241 millimeters) /var/log/Xorg.0.log acknowledges that it is picking up the right Monitor section in xorg.conf, (++) ServerLayout "IBM" (**) |-->Screen "IBM" (0) (**) | |-->Monitor "IBM" (**) | |-->Device "ATI mobility" that monitor section has 3 modelines defined: Section "Monitor" Identifier "IBM" VendorName "IBM 19inch+Sun 19inch" ... HorizSync 50-120 #Heck; too many valid modes. Lets just enable them all and be wery wery careful VertRefresh 50-160 DisplaySize 406 304 #Option "NoDPMS" Modeline "IBM_mode_1" 89.20 1024 1045 1205 1408 1024 1027 1030 1056 -hsync -vsync Modeline "IBM_mode_2" 111.50 1280 1298 1498 1756 1024 1024 1035 1040 -hsync -vsync Modeline "IBM_mode_3"120.00 1280 1308 1468 1696 1024 1027 1030 1060 -hsync -vsync ... using this setting in my Screen section: Option "Display" "CRT" Xorg.0.log acknowdlges I have asked for external CRT but then goes on to talk about the laptop's panel, which it should not be caring about: (**) R128(0): Using external CRT for display (II) R128(0): Primary Display == Type 2 (II) R128(0): Panel size: 1024x768 (II) R128(0): Panel ID: Samsung LT141X8-L02 (II) R128(0): Panel Type: Color, Single, TFT (II) R128(0): Panel Interface: LVDS (II) R128(0): PLL parameters: rf=2700 rd=12 min=12000 max=27000; xclk=10500 and then Xorg.0.log goes on to claim it knows nothing about the IBM modelines: (II) R128(0): Not using mode "IBM_mode_1" (no mode of this name) (II) R128(0): Not using mode "IBM_mode_2" (no mode of this name) (II) R128(0): Not using mode "IBM_mode_3" (no mode of this name) Then I end up with cruddy 1024x768: (**) R128(0): *Mode "[EMAIL PROTECTED]": 65.0 MHz (scaled from 83.9 MHz), 60.1 kHz, 74.4 Hz (which I find odd, because if it truly was using the flat panel's settings, should it not have picked up the 60Hz rate the flat panel requires? It works on both displays when I cycle through the laptop's external/interal settings) -- Tim Connors | Anglo-Australian Observatory http://site.aao.gov.au/twc | Coonabarabran, NSW 2357, Australia | Tel: +61 2 6842 6286 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348873: regression: r128 on laptop ignores supplied modeline for external display, picking LCD panel pixel dimensions
On Sat, 23 Jun 2007, Brice Goglin wrote: > Tim Connors wrote: > > and then Xorg.0.log goes on to claim it knows nothing about the IBM > > modelines: > > (II) R128(0): Not using mode "IBM_mode_1" (no mode of this name) > > (II) R128(0): Not using mode "IBM_mode_2" (no mode of this name) > > (II) R128(0): Not using mode "IBM_mode_3" (no mode of this name) > > > > Then I end up with cruddy 1024x768: > > (**) R128(0): *Mode "[EMAIL PROTECTED]": 65.0 MHz (scaled from 83.9 MHz), > > 60.1 kHz, 74.4 Hz > > (which I find odd, because if it truly was using the flat panel's > > settings, should it not have picked up the 60Hz rate the flat panel > > requires? It works on both displays when I cycle through the > > laptop's external/interal settings) > > > > Could you try with xserver-xorg-video-ati 1:6.6.192-1 currently in > experimental in case it helps? Same result with 1:6.6.192-1. > Or you feel more adventurous, you could try the randr-1.2 branch of the > upstream git repository since it should be better at discovering > modes/resolutions/... automatically without the need for anything in > xorg.conf. I have some packages of this somewhere if you want to try it. The latter certainly will be a problem -- I have good reason for wanting to supply my own modelines -- I have a fixed frequency external monitor. I don't need better discovery -- this all used to work, and I've already worked out which modelines will work on my monitor, and X will not do a better job than me at detecting necessary modelines from a monitor that doesn't do DDC. This used to work prior to 6.9 -- I haven't changed anything to do with my carefully crafted modelines, so those should continue to be working. -- Tim Connors | Anglo-Australian Observatory http://site.aao.gov.au/twc | Coonabarabran, NSW 2357, Australia | Tel: +61 2 6842 6286 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348873: regression: r128 on laptop ignores supplied modeline for external display, picking LCD panel pixel dimensions
On Sat, 23 Jun 2007, Tim Connors wrote: > On Sat, 23 Jun 2007, Brice Goglin wrote: > > > Tim Connors wrote: > > > and then Xorg.0.log goes on to claim it knows nothing about the IBM > > > modelines: > > > (II) R128(0): Not using mode "IBM_mode_1" (no mode of this name) > > > (II) R128(0): Not using mode "IBM_mode_2" (no mode of this name) > > > (II) R128(0): Not using mode "IBM_mode_3" (no mode of this name) > > > > > > Then I end up with cruddy 1024x768: > > > (**) R128(0): *Mode "[EMAIL PROTECTED]": 65.0 MHz (scaled from 83.9 MHz), > > > 60.1 kHz, 74.4 Hz > > > (which I find odd, because if it truly was using the flat panel's > > > settings, should it not have picked up the 60Hz rate the flat panel > > > requires? It works on both displays when I cycle through the > > > laptop's external/interal settings) > > > > > > > Could you try with xserver-xorg-video-ati 1:6.6.192-1 currently in > > experimental in case it helps? > > Same result with 1:6.6.192-1. > > > Or you feel more adventurous, you could try the randr-1.2 branch of the > > upstream git repository since it should be better at discovering > > modes/resolutions/... automatically without the need for anything in > > xorg.conf. I have some packages of this somewhere if you want to try it. > > The latter certainly will be a problem -- I have good reason for wanting > to supply my own modelines -- I have a fixed frequency external monitor. > I don't need better discovery -- this all used to work, and I've already > worked out which modelines will work on my monitor, and X will not do a > better job than me at detecting necessary modelines from a monitor that > doesn't do DDC. This used to work prior to 6.9 -- I haven't changed > anything to do with my carefully crafted modelines, so those should > continue to be working. A mandrake user has discovered a workaround, and I have just submitted more info upstream to https://bugs.freedesktop.org/show_bug.cgi?id=5832 Bad assumptions seem to be made about the presense of flat panel registers implying that a flat panel is being used. I have proposed a more robust workaround rather than the complete disabling of the valid-modelines-for-a-flat-panel check, but wouldn't know how to actually put this into action. Hopefully someone knows enough about the driver to be able to check this. -- TimC "I give up," said Pierre de Fermat's friend. "How DO you keep a mathematician busy for 350 years?" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#434833: Spontaneous reboots on suspend-to-RAM with new Xorg "intel" driver
Just default acpi-support + gnome-power-manager (I set my system to suspend on lid close). On 7/27/07, Julien Cristau <[EMAIL PROTECTED]> wrote: > > On Thu, Jul 26, 2007 at 23:27:51 -0400, Tim Hull wrote: > > > When using the new "intel" video driver that replaced the former "i810" > > driver in Debian, I am experiencing spontaneous reboots randomly on > > suspend-to-RAM. > > What are you using for suspend/resume? > > > Right before the system spontaneously reboots, I see a checkered pattern > on > > a black-and-white console display. At times, though rare, I have also > seen > > similar crashes when stopping and restarting the X server manually - > which > > leads me to believe that starting/stopping the X server is what is > causing > > the issue. I have no such problem when using 915resolution and the old > i810 > > driver in Etch and on Ubuntu Feisty (their stable), but do see the same > > problem on Ubuntu Gutsy (their unstable) which uses the intel > driver. While > > it doesn't occur every time I suspend, it occurs often enough that this > is a > > MAJOR annoyance for me. I'm marking this as RC, as such crashes DO > cause > > data loss in open files - you're free to disagree with me, though... > > That's not what data loss means. > > > System configuration is a MacBook Core Duo (first generation) with 2GB > RAM > > and Debian Sid. > > I've attached my xorg.conf and appropriate logs... > > Thanks, > Julien > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGqclAmEvTgKxfcAwRAkL/AKCKOW6jyvcqKMCG0kOCqORzevVkRQCfYZdK > vj3gLM/cmygo5gkhzurvph8= > =6eET > -END PGP SIGNATURE- > >
Bug#443059: Keyboard freezes - probably shouldn't be a closed bug.
I've seen this problem in several hardware combinations - using the i810 driver on real hardware and vmware drivers under VMWare Fusion on a Mac. I don't think the BusType hack is a good enough solution to warrant closing this bug - there's some sort of nasty interaction with gdm which causes this. I've found using other login managers (kdm or xdm) I never see the problem, but with gdm I do, on most boots of my virtual machine. Normally one of two things happens: 1) I can't log in at the gdm greeter at all 2) I can log in, but the keyboard lockup happens during the session a little later, sometimes almost immediately. Once the lockup has happened, I can log in remotely, and have tried to see what's going on. For example, I can run xev from a remote SSH session, and look to see if X events are appearing at all from the keyboard. They aren't. I can also then strace the X server, and see whether it's seeing activity from the keyboard, and it is. So the events are being discarded somewhere between the X server receiving them and the GNOME session receiving them. One suspicion I have is whether this is a security feature - if the time is changing on the machine (say, because of NTP, or VMWare's synchronise VM clock with host option) I wonder whether some protection mechanism against replay attacks is kicking in? Tim -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#456452: xserver-xorg-core: Dell laptop volume hotkey now changes linein not speakers
Package: xserver-xorg-core Version: 2:1.4.1~git20071212-1 Severity: normal First: I don't really know the right place to report this. Bug: the volume control hotkeys FN+Page Up, FN+Page Down, no longer change the output volume. I see in the Gnome preferences app Volume Control that the Line-in setitng is being changed when I use the hotkeys. This bug is only a few days old. I have an old Dell laptop: Latitude C610 -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2007-08-03 18:36 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1672732 2007-12-13 02:48 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 2983 2007-11-25 09:28 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Extensions" Option "Composite" "Enable" EndSection Section "DRI" Mode 0666 EndSection Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "TouchpadOff" "0" #note: GuestMouseOff "true" really works, but the stick can come back to life # because of the mouse input device, unless you specifically indicate which usb port the external mouse uses Option "GuestMouseOff" "true" Option "CorePointer" # Option "SendCoreEvents""true" Option "Device""/dev/psaux" Option "Protocol" "auto-dev" Option "SHMConfig" "on" EndSection Section "InputDevice" Identifier "Configured Mouse2" Driver "mouse" Option "SendCoreEvents""true" #Option "Device""/dev/input/mice" Option "Device""/dev/input/mouse2" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Configured Mouse0_extern" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" #Option "Device""/dev/input/mouse0" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "ATI Technologies Inc Radeon Mobility M6 LY" Driver "radeon" BusID "PCI:1:0:0" Option "EnablePageFlip" "on" Option "DisableGLXRootClipping" "true" Option "AddARGBGLXVisuals" "true" Option "AllowGLXWithComposite" "true" Option "XAANoOffscreenPixmaps" "true" Option "RenderAccel" "True" Option "backingstore" "True" Option "TripleBuffer" "True" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies Inc Radeon Mobility M6 LY" Monitor "Generic Monitor" DefaultDepth24 SubSection "Display" Modes "1024x768" EndSubSection EndSection Section "ServerLayout" Option "AIGLX" "true" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Synaptics Touchpad" InputDevice "Configured Mouse0_extern # InputDevice "Configured Mouse2" EndSection Section "Module" Load "dbe" Load "dri" Load "glx" Load "synaptics" EndSection Xorg X server log
Bug#458415: xserver-xorg-video-ati: Windows maximise beyond right of screen boundary
Package: xserver-xorg-video-ati Version: 1:6.7.196-1 Severity: important Starting with xserver-xorg-video-ati version 1:6.7.196-1, windows are maximising beyond the right of the screen, making it difficult to hit scrollbars and so on. Version 1:6.7.195-2 worked correctly. Version 1:6.7.198~git20071223.ad3325f6-1 has not fixed it. As well as the usual reportbug spam below, here is a diff between the last working Xorg log and the first broken one. The screen physical size has been set a bit larger, and 'VGA-0' is now using initial mode 1152x768. Thanks. :) --- Xorg.fixed.log 2007-12-31 03:19:48.0 + +++ Xorg.broken.log 2007-12-31 03:19:21.0 + @@ -12,7 +12,7 @@ Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. -(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 31 03:17:28 2007 +(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 31 03:18:43 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) @@ -302,7 +302,7 @@ (II) LoadModule: "ati" (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so (II) Module ati: vendor="X.Org Foundation" - compiled for 1.4.0, module version = 6.7.195 + compiled for 1.4.0, module version = 6.7.196 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 2.0 (II) LoadModule: "kbd" @@ -323,7 +323,7 @@ compiled for 4.3.99.902, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 2.0 -(II) ATI: ATI driver wrapper (version 6.7.195) for chipsets: mach64, rage128, radeon +(II) ATI: ATI driver wrapper (version 6.7.196) for chipsets: mach64, rage128, radeon (II) Primary Device is: PCI 01:05:0 (II) Loading sub module "radeon" (II) LoadModule: "radeon" @@ -500,7 +500,7 @@ [35] 0 0 0x03b0 - 0x03bb (0xc) IS[B] [36] 0 0 0x03c0 - 0x03df (0x20) IS[B] (II) Setting vga for screen 0. -(II) RADEON(0): MMIO registers at 0xd430: size 64KB +(II) RADEON(0): MMIO registers at 0xd430: size 64KB (II) RADEON(0): PCI bus 1 card 5 func 0 (**) RADEON(0): Depth 24, (--) framebuffer bpp 32 (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) @@ -523,7 +523,7 @@ (II) RADEON(0): initializing int10 (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (--) RADEON(0): Chipset: "ATI Radeon XPRESS 200M 5975 (PCIE)" (ChipID = 0x5975) -(--) RADEON(0): Linear framebuffer at 0xc000 +(--) RADEON(0): Linear framebuffer at 0xc000 (II) RADEON(0): PCI card detected (II) RADEON(0): Legacy BIOS detected (II) RADEON(0): Direct rendering not officially supported on RN50/RC410 @@ -554,7 +554,6 @@ XRes: 1024, YRes: 768, DotClock: 65000 HBlank: 320, HOverPlus: 24, HSyncWidth: 136 VBlank: 38, VOverPlus: 3, VSyncWidth: 6 -(II) RADEON(0): Using LVDS Native Mode (II) RADEON(0): Output S-video has no monitor section (II) RADEON(0): Default TV standard: NTSC (II) RADEON(0): TV standards supported by chip: NTSC PAL PAL-M NTSC-J @@ -624,6 +623,7 @@ (II) RADEON(0): I2C device "MONID:ddc2" registered at address 0xA0. (II) RADEON(0): I2C device "MONID:ddc2" removed. (II) RADEON(0): DDC Type: 1, Detected Monitor Type: 0 +in RADEONProbeOutputModes (II) RADEON(0): DDC Type: 5, Detected Monitor Type: 2 (II) RADEON(0): EDID data from the display on connector: Proprietary/LVDS -- (II) RADEON(0): Manufacturer: LPL Model: bb00 Serial#: 0 @@ -654,9 +654,10 @@ (II) RADEON(0):004c503135305830382d544c414300e5 in RADEONProbeOutputModes (II) RADEON(0): EDID vendor "LPL", prod id 47872 -(II) RADEON(0): Output VGA-0 disconnected +(II) RADEON(0): Output VGA-0 connected (II) RADEON(0): Output LVDS connected (II) RADEON(0): Output S-video disconnected +(II) RADEON(0): Output VGA-0 using initial mode 1152x768 (II) RADEON(0): Output LVDS using initial mode 1024x768 after xf86InitialConfiguration (==) RADEON(0): DPI set to (75, 75) @@ -725,6 +726,7 @@ [38] 0 0 0x03b0 - 0x03bb (0xc) IS[B](OprU) [39] 0 0 0x03c0 - 0x03df (0x20) IS[B](OprU) (==) RADEON(0): Write-combining range (0xc000,0x800) +(WW) RADEON(0): Cannot read colourmap from VGA. Will restore with default Entering TV Save Save TV timing tables saveTimingTables: reading timing tables @@ -735,9 +737,9 @@ (II) RADEON(0): MC_FB_LOCATION : 0x3fff3800 (II) RADEON(0): MC_AGP_LOCATION : 0xffc0 (II) RADEON(0): Depth moves disabled by default -(II) RADEON(0): Memory manager initialized to (0,0) (1024,8191) -(II) RADEON(0): Reserved area from (0,1024) to (1024,1026) -(II) RADEON(0): Largest offscreen area available: 1024 x 7165 +(II) RADEON(0): Memory manager initialized to (0,0) (1280,8191) +(II) RADEON(0): Reserved area f
Bug#458415: xserver-xorg-video-ati: Windows maximise beyond right of screen boundary
retitle 458415 virtual screen size larger than display since 1:6.7.196-1 kthxbye On Mon, 2007-12-31 at 10:48 +0100, Brice Goglin wrote: > The upstream bug report is marked as duplicate of another one which is fixed > (https://bugs.freedesktop.org/show_bug.cgi?id=13231) > > So if it's not fixed for you with git20071223.ad3325f6, you should > reopen it. Did you read/check what Alex Deucher said there? Yes, I've been studying the bugs and the mailing list to decide what to do upstream. Running "xrandr --output VGA-0 --off" does fix this until X restarts. I haven't bothered working out the exact xorg.conf changes to fix this. The problem arises because VGA output is now enabled by default even if no external monitor is attached, and for some reason it has a resolution of 1152x768 (not 1024x768). So, it's as if I'm using an external monitor that's slightly bigger than the laptop screen, and the mouse carries on past the right-hand edge of the display. With metacity, windows still maximise to the correct size (but Fitts' law is broken), and with simpler window managers (e.g. evilwm) the windows maximise to the size of the virtual screen. I suspect that either: * the commit that caused this needs to be backed out, * the default VGA resolution needs changing (hacky), or * external monitor detection for the Xpress cards needs to be added as soon as possible. I'll reopen the upstream bug report. -- Tim Retout <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Bug#458415: xserver-xorg-video-ati: Windows maximise beyond right of screen boundary
On Mon, 2007-12-31 at 12:48 +0100, Brice Goglin wrote: > Tim Retout wrote: > > * external monitor detection for the Xpress cards needs to be > > added as soon as possible. > > > > That's probably the problem here. Not sure you need to reopen the > upstream bug there. Alex is well aware that multi-head on Xpress does > not work very well yet. Hmm, oh well, it's reopened now. :/ > What does xrandr report with 1:6.7.198~git20071223.ad3325f6-1 ? The VGA > output status should be unknown. The set of available resolutions is a bit weird. $ xrandr -q Screen 0: minimum 320 x 200, current 1152 x 768, maximum 1280 x 1200 VGA-0 unknown connection 1152x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1280x800 60.0 1152x768 54.8* 800x60056.2 640x48059.9 LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 304mm x 228mm 1024x768 60.0*+ 800x60060.3 640x48059.9 S-video disconnected (normal left inverted right x axis y axis) -- Tim Retout <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Bug#458415: xserver-xorg-video-ati: wrong VGA load detection on Xpress 200M confuses the window manager
On Wed, 2008-01-02 at 11:41 +0100, Brice Goglin wrote: > No, Tim has a real bug caused by the VGA output not being correctly > detected. It confuses the window manager by saying that the screen is > 1152x864 while it is actually smaller. I am retitling the bug accordingly. Running `dpkg-reconfigure xserver-xorg' resulted in a much smaller xorg.conf, and the problem went away. It also went away when removing the VertSync option, because the VGA-0 output then supported a 1024x768 resolution. The VGA output is still there, but it causes no harm. I suspect that the problematic patch might actually have the benefit of enabling VGA output on my laptop by default, so 1024x768 projectors will now just work. My xorg.conf is managed by dexconf; perhaps trigger a reconfigure of xorg.conf on upgrade of the ati driver...? But then, a lot of people have the ati driver installed but use a different one. So perhaps the only safe solution is to actually detect when VGA devices are attached. -- Tim Retout <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Bug#459041: xterm: version 230-1 segfaults somewhere when involving cut and paste
Package: xterm Version: 230-1 Severity: grave Justification: causes non-serious data loss Cutting text somewhere in an xterm causes it to segfault with the most recent upgrade. It may involve either the cut or paste of long lines. I'm pretty sure it happens as soon as I click the mouse to make a selection, and can happen after a successful cut and paste or two. I haven't yet restarted X, but that's not going to cause a dynamic library inconsistency problem. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23 (SMP w/2 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages xterm depends on: ii libc6 2.7-5 GNU C Library: Shared libraries ii libfontconfig12.5.0-2generic font configuration library ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libncurses5 5.6+20071215-1 Shared libraries for terminal hand ii libsm62:1.0.3-1+b1 X11 Session Management library ii libx11-6 2:1.0.3-7 X11 client-side library ii libxaw7 2:1.0.4-1 X11 Athena Widget library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxft2 2.1.12-2 FreeType-based font drawing librar ii libxmu6 1:1.0.3-1 X11 miscellaneous utility library ii libxt61:1.0.5-3 X11 toolkit intrinsics library ii xbitmaps 1.0.1-2Base X bitmaps Versions of packages xterm recommends: ii xutils1:7.3+9X Window System utility programs m -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465707: compiz-core: X crashes machine when x-server shuts down (restart, shutdown, ctrl-alt-bs)
Package: compiz-core Version: 0.6.3~git20071222.061ff159-1 Severity: important This is a new install of Debian testing. With compiz running, the machine hanges on shutdown (or x server restart). The screen partially blanks, but fills with dark gray flashing squares. I don't see anything useful in system logs. I will upgrade compiz to sid versions and see if it is fixed. The machine is a Dell latitude D420 notebook running intel video card 945GM -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages compiz-core depends on: ii libc6 2.7-6 GNU C Library: Shared libraries ii libgl1-mesa-glx [libgl1] 7.0.2-4 A free implementation of the OpenG ii libice62:1.0.4-1 X11 Inter-Client Exchange library ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libstartup-notification0 0.9-1 library for program launch feedbac ii libx11-6 2:1.0.3-7 X11 client-side library ii libxcomposite1 1:0.4.0-1 X11 Composite extension library ii libxdamage11:1.1.1-3 X11 damaged region extension libra ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library ii libxml22.6.31.dfsg-1 GNOME XML library ii libxrandr2 2:1.2.2-1 X11 RandR extension library ii libxslt1.1 1.1.22-1 XSLT processing library - runtime ii mesa-utils 7.0.2-4 Miscellaneous Mesa GL utilities Versions of packages compiz-core recommends: ii compiz-plug 0.6.3~git20071222.061ff159-1 OpenGL window and compositing mana -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#466039: xserver-xorg-core: DPMS wakes up on spontaneous 1 pixel mouse moves
Package: xserver-xorg-core Version: 2:1.4.1~git20080131-1 Severity: normal My laptop is set to blank its display after 10 minutes, and turn it off after 15. (**) Option "BlankTime" "10" (**) Option "StandbyTime" "0" (**) Option "SuspendTime" "15" (**) Option "OffTime" "0" Alas, when I have an external USB mouse plugged in, it only ever goes blank. If I xset force dpms off, then it will turn the backlights off on the internal monitor, and an external LCD, but then come back on at a random time later, from seconds to 10 minutes later. The display remains blank though, but with the backlights turned on. Eventually, I tracked this down to random 1 or 2 pixel spontaneous moves of the mouse, and demonstrate that in the following example: > ( while : ; do while read -n 1 -e -s -t 10 c ; do #read one character at a time with a 10 second timeout echo -n `date` -- ; ord "$c" done echo #print a blank line every 10 seconds done ) < /dev/input/mice Sat Feb 16 12:00:58 EST 2008 -- 24 Sat Feb 16 12:01:00 EST 2008 -- 255 Sat Feb 16 12:01:00 EST 2008 -- 0 Sat Feb 16 12:06:39 EST 2008 -- 8 Sat Feb 16 12:06:39 EST 2008 -- 0 Sat Feb 16 12:06:40 EST 2008 -- 1 Sat Feb 16 12:06:40 EST 2008 -- 8 Sat Feb 16 12:06:40 EST 2008 -- 2 Sat Feb 16 12:06:40 EST 2008 -- 0 I find it odd that 1 or 2 pixel moves (presumably caused by light variations in the optical mouse's detector) is enough to light the backlight, but a bigger movement is required to unblank the display. I suggest this means the X server needs to have a configurable threshold of number of number of pixels of mouse movement in a certain polling period, needed to retrigger the DPMS timer. Until then, I need to unplug my external USB mouse every time I leave my laptop so that I can turn off the displays. This is particularly annoying, since closing the laptop's screen turns the backlight off through the dpms method using ACPI detection of the lid switch. Since this gets erroneously turned back on, my laptop's backlight is still on even when its display is folded close. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Sep 16 20:58 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1831520 Feb 1 16:08 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GT (rev a1) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: lrwxrwxrwx 1 root root 50 Oct 7 22:47 /etc/X11/xorg.conf -> /home/tconnors/debian-common-files/xorg.conf-dirac Contents of /etc/X11/xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "Module" Load"synaptics" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" # Driver "evdev" #Option "Dev Phys" "isa0060/serio0/input0" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" #altwin:meta_win Option "XkbOptions""ctrl:nocaps" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "ButtonNumber" "5" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" # Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents""true" Option "Device""/dev/psaux" ## Option "Device""/dev/input/mice" Option "Protocol" "auto-dev" Option "LeftEdge" "1700" Option "RightEdge" "5300" Option "TopEdge" "1700" Option "BottomEdge""4200" Option "FingerLow" "2
Bug#466044: xserver-xorg-core: internal screen of laptop with external screen attached not blanked when laptop closed but still in use
Package: xserver-xorg-core Version: 2:1.4.1~git20080131-1 Severity: normal Laptop screens backlights are turned off these days by getting acpi to intercept the lid button, and it runs xset to force the display off via 'xset dpms force off' (after a series of other attempts at locking the display etc, which are all equally invalid in the circumstances I outline below). This is a rather course control, and just turns off the backlights of all attached screens. My old laptop, when it was running APM, controlled the backlight itself, and it worked well such that you could close the laptop and it would turn off the interal display, but leave the external display turned on. DPMS would then turn off the external display when it was left alone, and when the display was woken up again, only the external display was woken up - the internal one was left undisturbed until the screen was opened again. This is not bug 466042, where the internal display is turned on and off via dpms, but the external display is let alone. In the circumstances in that bug, the internal display should be completely ignored. The lid switch would have no effect on the external display (but xset dpms would still work on it) or the internal display (because the resolution is wrong), if both this and bug 466042 were fixed. I think the lid button should be intercepted by X itself, rather than handing the functionality off to acpid, which then runs 'xset dpms force off'. This way you can close the laptop screen, which would shut off the backlight to the internal display. And DPMS timeouts or running 'xset dpms force off' would turn off both displays. Pressing a key when DPMS was on would only turn on the external display unless the screen was open, in which case the internal display would be turned on too. In other words, the internal backlight being controlled by the lid switch has absolutely nothing to do with dpms. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Sep 16 20:58 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1831520 Feb 1 16:08 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GT (rev a1) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: lrwxrwxrwx 1 root root 50 Oct 7 22:47 /etc/X11/xorg.conf -> /home/tconnors/debian-common-files/xorg.conf-dirac Contents of /etc/X11/xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "Module" Load"synaptics" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" # Driver "evdev" #Option "Dev Phys" "isa0060/serio0/input0" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" #altwin:meta_win Option "XkbOptions""ctrl:nocaps" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "ButtonNumber" "5" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" # Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents""true" Option "Device""/dev/psaux" ## Option "Device""/dev/input/mice" Option "Protocol" "auto-dev" Option "LeftEdge" "1700" Option "RightEdge" "5300" Option "TopEdge" "1700" Option "BottomEdge""4200" Option "FingerLow" "25" Option "FingerHigh""30" Option "MaxTapTime""180" Option "MaxTapMove""220"
Bug#466104: xinit: please use sessreg like in xdm, to log startx in the wtmp database
Package: xinit
Version: 1.0.7-2
Severity: normal
For those of us who choose not to start X every boot using xdm, we
don't get the X session being logged in the wtmp database like it does
from xdm.
Because X can be started and the parent shell subsequently exited, the
lack of an entry in wtmp gives the sysadmin a false impression that
noone is actually logged into the system when it comes time for them
to do maintenance and rebooting.
xdm has its mechanism in /etc/X11/xdm/{Xstartup,Xreset} to log the
details using sessreg - it would be good if startx could make use of a
similar scheme too.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24 (SMP w/2 CPU cores)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages xinit depends on:
ii cpp 4:4.2.2-2 The GNU C preprocessor (cpp)
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libx11-6 2:1.0.3-7 X11 client-side library
ii x11-common1:7.3+10 X Window System (X.Org) infrastruc
xinit recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#466104: xinit: please use sessreg like in xdm, to log startx in the wtmp database
reassign 466104 x11-common
thanks
On Sun, 17 Feb 2008, Julien Cristau wrote:
> severity 466104 wishlist
> kthxbye
>
> On Sun, Feb 17, 2008 at 02:51:53 +1100, Tim Connors wrote:
>
> > For those of us who choose not to start X every boot using xdm, we
> > don't get the X session being logged in the wtmp database like it does
> > from xdm.
> >
> > Because X can be started and the parent shell subsequently exited, the
> > lack of an entry in wtmp gives the sysadmin a false impression that
> > noone is actually logged into the system when it comes time for them
> > to do maintenance and rebooting.
> >
> > xdm has its mechanism in /etc/X11/xdm/{Xstartup,Xreset} to log the
> > details using sessreg - it would be good if startx could make use of a
> > similar scheme too.
> >
> xdm runs as root, and actually lets the user log in. Neither of those
> is the case for xinit. The user running xinit has already logged in.
> (I'm actually tempted to close this bug or at least tag it wontfix)
Except that the user is free to logout of the terminal which started X, so
it truly is a seperate login.
With xdm, w shows the TTY as :0 (or :1 or xdmcphost:0 or whatever), and
with startx, it should also show the display being used (since individual
xterms within that X session won't log their logins/logouts).
xinit doesn't run as root, but X certainly does. It knows the real uid of
the user running X, it knows the time it is running for, and it knows the
display, and thus it has all the info it needs to log an entry in the wtmp
database. It might need/want to check that an entry hasn't already been
logged by sessreg on behalf of xdm, which may or may not be part of the
same X session because of xdmcp remote displays.
Perhaps I need to reassign this bug from xinit to x11-common since it owns
the X binary.
--
TimC
"Think of bicycles as rideable art that can just about save the
world." - Grant Peterson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#444656: xserver-xorg-video-nv: Samsung LCD Syncmaster does not resume after dpms sleep
Package: xserver-xorg-video-nv Version: 1:2.1.5-1 Severity: normal A recent change to the nv driver causes my monitor to "crash" when attempting to wake up after being sent into poweroff. When resuming because I move the mouse or use the keyboard, the monitor dispalys broad stripes of colors and then goes into a kind of psychadelic color splash. Restarting X does nothing. All I need to do is to turn the monitor off and on. It looks like the machine has crashed, but this is not the case. This problem does not occur with the "nvidia" driver and it did not occur until recently with the nv driver. The problem (bad resume) is more likely to happen the longer the monitor has been in sleep. Right now I am using the nvidia driver, so the xorg.conf file attached is wrong. I get the problem with the nv driver with a minimal xorg; no modules, and DPMS set for the monitor. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2007-08-09 07:03 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1669528 2007-09-16 20:56 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: nVidia Corporation GeForce 7300 GS (rev a1) /etc/X11/xorg.conf unchanged from checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1573 2007-09-30 08:29 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "nVidia Corporation G71 [GeForce 7300 GS]" Driver "nv" BusID "PCI:1:0:0" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" HorizSync 30-70 VertRefresh 50-160 EndSection Section "Screen" Identifier "Default Screen" Device "nVidia Corporation G71 [GeForce 7300 GS]" Monitor "Generic Monitor" DefaultDepth24 EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 1049 2007-09-28 18:34 /var/log/Xorg.20.log -rw-r--r-- 1 root root 47503 2007-09-30 08:30 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4-2) Current Operating System: Linux antec 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 Build Date: 16 September 2007 02:37:21PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sun Sep 30 08:30:13 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Generic Monitor" (**) | |-->Device "nVidia Corporation G71 [GeForce 7300 GS]" (**) |-->Input Device "Generic Keyboard" (**) |-->Input Device "Configured Mouse" (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (WW) The directory "/
Bug#444656: xserver-xorg-video-nv: Samsung LCD Syncmaster does not resume after dpms sleep
On 9/30/07, Julien Cristau <[EMAIL PROTECTED]> wrote: te: > can you bisect which exact change did this? To rule out an X server > bug, it'd be good to first test a previously-working version of the nv > driver rebuilt against xserver 1.4. > > Cheers, > Julien > Yesterday, I compiled the nv-driver source package in testing against the X server distribution in unstable. (I never would have guessed how easy it is to do that, and apparently the build is smart enough to make new dependencies). I've been checking ever since; the problem with the monitor resuming is not present. So it seems that a change to the nv driver is the cause of the problem. The xserver-xorg-video-nv package version I built is called 1:2.1.3-1 the xserver-xorg-core package version I have is 2:1.4-2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#444656: xserver-xorg-video-nv: Samsung LCD Syncmaster does not resume after dpms sleep
On 10/1/07, Brice Goglin <[EMAIL PROTECTED]> wrote: > > So your problem appeared between 2.1.3 and 2.1.5. There are only 8 > commits between there releases. The only one that really changes some > code is: > http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-nv.git;a=commitdiff_plain;h=b2db7d414400d80a5567d71eed9a7e94f1043a20;hp=07fb9f0b00fafe18bd33bddff23cbb4325eb50f8 > > Could you try applying on top of your rebuilt 2.1.3 and see whether it > causes the problem to occur? > > Thanks, > Brice > > I applied this patch, and it changed two source files. I rebuilt the package, which has a slightly different size so it definitely changed. The problem now appears, so this patch causes the problem. After installing the patched version of 2.1.3 I rebooted to be sure. The problem appeared after letting the monitor sleep for about three minutes. Power-cycling the monitor restores the image; nothing else can. Let me know if I can help further. Thanks for you interest in this, I've had fun learning how to do new things. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#446777: xserver-xorg-core: Dell laptop screen brightness FN keys don't work
Package: xserver-xorg-core Version: 2:1.4-3 Severity: normal Fn keys to control screen brightness have stopped working. Reverting to the testing version of xserver packages fixes the problem. Reverting to testing versions of gnome-power-manager, acpid, hal does not solve the problem. In sid, both kde and gnome show the problem. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 Aug 3 18:36 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1669976 Sep 29 16:33 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 2622 Oct 14 19:47 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents""true" Option "Device""/dev/psaux" Option "Protocol" "auto-dev" Option "HorizScrollDelta" "0" Option "SHMConfig" "true" EndSection Section "Device" Identifier "ATI Technologies Inc Radeon Mobility M6 LY" Driver "radeon" BusID "PCI:1:0:0" Option "BusType" "PCI" #Optimized values (changed from driver default) #Option "AGPMode" "4" #Option "AGPFastWrite" "on" #Faster than default (off) Option "SWcursor" "off" #Faster than default (on) Option "EnablePageFlip" "on" #Faster than default (off) Option "AccelMethod" "EXA" # or XAA, EXA, XAA more stable, XAA is deafult Option "DynamicClocks" "on" #Option "BIOSHotkeys" "on" #These are not mentioned in man page for driver Option "AGPSize" "32" # default: 8 Option "EnableDepthMoves" "true" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" HorizSync 28-51 VertRefresh 43-60 EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies Inc Radeon Mobility M6 LY" Monitor "Generic Monitor" DefaultDepth24 SubSection "Display" Modes "1024x768" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Synaptics Touchpad" EndSection Section "Module" Load"i2c" Load"bitmap" Load"ddc" Load"freetype" Load"int10" Load"type1" Load"vbe" Load"dri" Load"extmod" Load"glx" Load"GLcore" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 38188 Sep 16 10:14 /var/log/Xorg.20.log -rw-r--r-- 1 root root 42533 Oct 15 18:03 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4-3) Current Operating System: Linux oldLaptop 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 Build Date
Bug#446777: additional info
Also, the brightness keys work when I switch to a console (alt-ctrl-F1), and when the computer is booting up. The same behaviour was observed in KDE. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#446777: xserver-xorg-core: Dell laptop screen brightness FN keys don't work
On Tue, 2007-10-16 at 00:11 +0200, Brice Goglin wrote: > > [...] > > > > #Option "BIOSHotkeys" "on" > > > > Does this option make any difference ? > No. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451705: xserver-xorg-input-mouse: Mouse detection fails when USB mouse is unplugged and replugged
Package: xserver-xorg-input-mouse Version: 1:1.2.3-1 Severity: important If I unplug my usb mouse to use only the touchpad (because I am leaving my desk), and then later reconnect my USB mouse, the mouse is no longer detected as an input device. I have to restart X. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Aug 3 18:36 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1669976 Sep 29 16:33 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 2967 Nov 7 23:04 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Extensions" Option "Composite" "Enable" EndSection Section "DRI" Mode 0666 EndSection Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "TouchpadOff" "0" #note: GuestMouseOff "true" really works, but the stick can come back to life # because of the mouse input device, unless you specifically indicate which usb port the external mouse uses Option "GuestMouseOff" "true" Option "CorePointer" # Option "SendCoreEvents""true" Option "Device""/dev/psaux" Option "Protocol" "auto-dev" Option "SHMConfig" "on" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "SendCoreEvents""true" #Option "Device""/dev/input/mice" Option "Device""/dev/input/mouse2" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Configured Mouse1" Driver "mouse" Option "SendCoreEvents""true" #Option "Device""/dev/input/mice" Option "Device""/dev/input/mouse0" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "ATI Technologies Inc Radeon Mobility M6 LY" Driver "radeon" BusID "PCI:1:0:0" Option "EnablePageFlip" "on" Option "DisableGLXRootClipping" "true" Option "AddARGBGLXVisuals" "true" Option "AllowGLXWithComposite" "true" Option "XAANoOffscreenPixmaps" "true" Option "RenderAccel" "True" Option "backingstore" "True" Option "TripleBuffer" "True" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies Inc Radeon Mobility M6 LY" Monitor "Generic Monitor" DefaultDepth24 SubSection "Display" Modes "1024x768" EndSubSection EndSection Section "ServerLayout" Option "AIGLX" "true" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Synaptics Touchpad" InputDevice "Configured Mouse" InputDevice "Configured Mouse1" EndSection Section "Module" Load "dbe" Load "dri" Load "glx" Load "synaptics" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 38188 Sep 16 10:14 /var/log/Xorg.20.log -rw-r--r-- 1 root root 42596 Nov 17 22:00 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var
Bug#451708: xserver-xorg-input-synaptics: Option "GuestMouseOff" "true" not working
Package: xserver-xorg-input-synaptics Version: 0.14.7~git20070706-1 Severity: normal Option "GuestMouseOff" "true" appears to not work for me. I think this is because I have a USB mouse configured using device /dev/input/mice and the stick is /dev/input/mouse1 If I force the USB mouse to be /dev/input/mouse0, then I have no stick. This solutions means I lose the mouse if I unplug it and reconnect it. I have to restart X. So I was hoping that "GuestMouseOff" which really kill the stick. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-input-synaptics depends on: ii libc6 2.6.1-6GNU C Library: Shared libraries ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxi62:1.1.3-1 X11 Input extension library ii xserver-xorg-core 2:1.4-3Xorg X server - core server xserver-xorg-input-synaptics recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451708: xserver-xorg-input-synaptics: Option "GuestMouseOff" "true" not working
In my opinion, the stick should be disabled. The Windows control panel for Synaptic touchpads has this option; when selected, the stick no longer moves the mouse. I expect the same behaviour. It seems that the stick gets its own /dev/input/mouse* device when the machine is booting. Perhaps when the display manager starts and xorg.conf is parsed, the device should be "unplugged". Can I "unplug" a USB device virtually? as for the bug, I see no evidence that the stick is being affected at all by the use of "GuestMouseOff" true. regards, Tim On Sun, 2007-11-18 at 12:57 +0900, Mattia Dongili wrote: > On Sat, Nov 17, 2007 at 10:58:26PM +0100, Tim Richardson wrote: > > Package: xserver-xorg-input-synaptics > > Version: 0.14.7~git20070706-1 > > Severity: normal > > > > Option "GuestMouseOff" "true" appears to not work for me. I think this > > is because I have a USB mouse configured using device /dev/input/mice > > and the stick is /dev/input/mouse1 > > If I force the USB mouse to be /dev/input/mouse0, then I have no stick. > > This solutions means I lose the mouse if I unplug it and reconnect it. I > > have to restart X. So I was hoping that "GuestMouseOff" which really > > kill the stick. > > Hi Tim, > > actually this sounds like the option is working, just not as you expect > or not as you would like to in your specific setup. > What would be needed in your opinion to fix this? > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451708: xserver-xorg-input-synaptics: Option "GuestMouseOff" "true" not working
Mattia, this problem is still annoying me. If I use default settings, all pointing devices become unusable because the trackpoint pushes the pointer to the edge of the screen and over-rides all mouse movement. I can't disable it in BIOS. I can't disable it with the "guestMouseOff" option to the synaptics driver I can only disable it as long as I do not use /dev/input/mice Since I want my external USB mouse to work, I specifically add an entry for that, using /dev/input/mouse2 However, this means I lose the advantages of /dev/input/mice, which is dynamic reconfiguration if I plug the USB mouse in and out. I've looked in the source code of synaptics.c and it seems that the use of guestMouseOff is very high level. It doesn't really disable the stick, it just ignores it. Do you know a way to disable a hardware device (like you can in the Windows XP Device Manager)? and instead I point specifically to the /dev/input/mouse0 and On Sun, 2007-11-18 at 12:57 +0900, Mattia Dongili wrote: > On Sat, Nov 17, 2007 at 10:58:26PM +0100, Tim Richardson wrote: > > Package: xserver-xorg-input-synaptics > > Version: 0.14.7~git20070706-1 > > Severity: normal > > > > Option "GuestMouseOff" "true" appears to not work for me. I think this > > is because I have a USB mouse configured using device /dev/input/mice > > and the stick is /dev/input/mouse1 > > If I force the USB mouse to be /dev/input/mouse0, then I have no stick. > > This solutions means I lose the mouse if I unplug it and reconnect it. I > > have to restart X. So I was hoping that "GuestMouseOff" which really > > kill the stick. > > Hi Tim, > > actually this sounds like the option is working, just not as you expect > or not as you would like to in your specific setup. > What would be needed in your opinion to fix this? > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#188567: great notice
The planet has gone wireless and Mobile Airwaves (mbwc) is in the right place in the right time with a Red Hot Product! We are anticipate Financial Results to be announced by the company any moment. With all the New Contracts they have acquired we are waiting for Record Earnings! mbwc is currently under priced at around 3 cents. With the Mobile Airwaves being so Tightly held we awaiting the inlux of buying to Push the price off the charts! Get in on this Breakout Winner Early! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#424975: please vote for the real bug(s) on ATI's bugzilla
The real bug that is the source of this problem is in ATI's code. ATI has a bugzilla issue for this at http://ati.cchtml.com/show_bug.cgi?id=609 Please register for a bugzilla account on their site and vote for this bug if you haven't done so already. You can allocate up to 100 votes per bug so please allocate all 100 if you can. There's also another bug that may cause a problem with a generic kernel: http://ati.cchtml.com/show_bug.cgi?id=643 Bug 643 doesn't seem to affect me however on my amd64 machine when using Aric's script. (maybe it's x86 specific or Aric's script works around it?). Thanks, Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354261: Fixed
This is now fixed with the latest evdev driver. Thanks, Tim. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#166515: A small gift 4 u
For your immediate review: Good Day, your file has been reviewed and there now are a few potential options for you to consider. Please note that this issue is time sensitive and that your previous credit situation is not of concern. Confirm your details on our secure form to ensure the data we have is up to date, thank you. http://www.quarxc.net/index2.php?refid=windsor --Tim Moses Lead Financial Advisor - eLMR Corp. opt out of our list here: http://www.quarxc.net/r.php -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318413: xlibs: Backslash Key is broken on Japanese Keyboards
Hi, Just to report that I also suffer from this bug on my Hitachi Prius laptop under xfree86 (but not under xorg; however I cannot get the 1200x800 mode working under xorg - I need to use 855resolution to get it working under xfree86, but I digress). The patch posted above (to /etc/X11/xkb/symbols/pc/jp) does not fix the bug for me; however, the patch (to /etc/X11/xkb/keycodes/xfree86) posted at http://www.vergenet.net/~horms/ does fix the problem. Cheers Tim Tim Gershon http://belle.kek.jp/~gershon/contact.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#24192: For your immediate review:
CLIENT ALERT - For your immediate review: Sorry for the initial delay, but your file has now been reviewed and we are happy to present you with three options for you to consider. Please note that this is a time sensitive matter and that your previous credit situation should not be a factor. Please confirm your details with our secure form to ensure our records are accurate and we will contact you via the method of your choice shortly. Thank You and Good Day. http://www.quicker-apps.net/index.php?refid=windsor --Tim Howe Senior Financial Advisor - eLMR Inc Did this reach you in error? please let our office know so you won't recieve again: http://www.quicker-apps.net/r.php -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
failure to get 1280x800 with xorg
Hi, I have been successfully using the 855resolution package to get the 1280x800 mode under XFree86 with my hardware, however this does not work under xorg, and I cannot decipher the logs. [AFAICT, the xorg log reports the mode, but then duly complains that "Not using mode "1280x800" (no mode of this name)", whereas XFree86 is perfectly happy.] I have attached the conf. and log files for both XFree86 and xorg. Any help will be gratefully received. Cheers Tim Tim Gershon http://belle.kek.jp/~gershon/contact.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Xorg
Hi, Sorry if I'm just not looking in the right place, but when are you planning to put together a package for the new xorg server 7.0? I tried to find a website with estimated release dates, but I couldn't find anything. Thanks, Tim Davis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348873: Regression from 6.8.2.dfsg.1-11 to 6.9.0.dfsg.1-4
A little bit of testing shows that this regression of video mode selection happens when upgrading from 6.8.2.dfsg.1-11 (currently still in testing) to 6.9.0.dfsg.1-4 (unstable). Since the release date on 6.8.2 is about 12 months ago, obviously this isn't going to be much help in narrowing down where things went wrong, but perhaps it's a start. -- TimC -- http://http://astronomy.swin.edu.au/staff/tconnors/ >Cats are intended to teach us that not everything in nature has a function. You're saying cats are the opposite of bijectiveness? -- ST in RHOD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351457: libexa.so: libexa.so fails to load due to undefined symbol
Package: xserver-xorg Version: 6.9.0.dfsg.1-4 Severity: normal File: libexa.so Xorg.0.log indicates that the exa module failed to load due to an undefined symbol: fgGlyph16. Relevant output from log: (II) Loading /usr/X11R6/lib/modules/libexa.so dlopen: /usr/X11R6/lib/modules/libexa.so: undefined symbol: fbGlyph16 (EE) Failed to load /usr/X11R6/lib/modules/libexa.so (II) UnloadModule: "exa" (EE) Failed to load module "exa" (loader failed, 7) -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 17 2005-11-11 21:54 /etc/X11/X -> /usr/bin/X11/Xorg -rwxr-xr-x 1 root root 1883716 2006-01-14 20:40 /usr/bin/X11/Xorg Contents of /var/lib/xfree86/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: :01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] /etc/X11/xorg.conf does not match checksum in /var/lib/xfree86/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 3902 2006-02-03 02:32 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # XF86Config-4 (XFree86 X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # This file is automatically updated on xserver-xfree86 package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xfree86 # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom # md5sum /etc/X11/XF86Config-4 >/var/lib/xfree86/XF86Config-4.md5sum # dpkg-reconfigure xserver-xfree86 Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/CID" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" Load"synaptics" Load"exa" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Touchpad" Driver "synaptics" Option "SHMConfig" "on" Option "CorePointer" Option "Device""/dev/psaux" Option "Protocol" "auto-dev" Option "LeftEdge" "1700" Option "RightEdge" "5300" Option "TopEdge" "1700" Option "BottomEdge""4200" Option "FingerLow" "25" Option "FingerHigh""30" Option "MaxTapTime""180" Option "MaxTapMove""220" Option "VertScrollDelta" "0" Option "HorizScrollDelta" "0" Option "ScrollingMode" "0" Option "MinSpeed" "0.06" Option "MaxSpeed" "0.12" Option "AccelFactor" "0.0010" #Option "Emulate3Buttons" "true" #Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Generic Video Card" #Driver "fglrx" Driver "ati" Opt
Bug#348873: logged in xorg
Hi, logged this into the bug tracking system at xorg: https://bugs.freedesktop.org/show_bug.cgi?id=5832 -- TimC My other car is a cdr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354261: xserver-xorg: evdev input driver allocates two device buttons to one keycode.
Package: xserver-xorg Version: 6.9.0.dfsg.1-4 Severity: normal I'm using the evdev input driver to get a Hauppauge remote control to work. All the buttons work but two of the buttons end up with the same keycode which is not much use. Using evtest the kernel device driver is providing the correct event types: Event: time 1140800533.454718, type 1 (Key), code 114 (VolumeDown), value 1 Event: time 1140800533.454722, -- Report Sync Event: time 1140800533.692121, type 1 (Key), code 114 (VolumeDown), value 0 Event: time 1140800533.692126, -- Report Sync Event: time 1140800536.363065, type 1 (Key), code 370 (Subtitle), value 1 Event: time 1140800536.363069, -- Report Sync Event: time 1140800536.600470, type 1 (Key), code 370 (Subtitle), value 0 Event: time 1140800536.600475, -- Report Sync (Sorry about the wrapping, each line starts with Event:) As you can see the two buttons are VolumeDown and Subtitle, both of which are useful to me but the end up with keycode 122. It would be nice if X had some Multimedia keysyms defined but I'd settle for the driver just assigning a unique keycode to each button on the device. Instead I've got these two duplicates and the number buttons comes in as Keypad numbers and I'd rather have them as the normal numbers so I don't have to try to get NumLock on (there will e no normal keyboard once I've finished futzing). The server layout in use is orac-mythtv, it uses the inpute device called Remote which uses the evdev driver on a device called /dev/input/remote. That device is set up by udev to point to the real event device since that seems to change depending on the phase of the moon. -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 17 2006-01-24 13:29 /etc/X11/X -> /usr/bin/X11/Xorg -rwxr-xr-x 1 root root 1878044 2006-01-15 01:40 /usr/bin/X11/Xorg Contents of /var/lib/xfree86/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: :00:08.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) :01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266] /etc/X11/xorg.conf does not match checksum in /var/lib/xfree86/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 5478 2006-02-24 17:18 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (Xorg X Window System server configuration file) Section "Files" # local font server FontPath "unix/:7101" # if the local font server has problems, we can fall back on these FontPath "/usr/lib/X11/fonts/misc" FontPath "/usr/lib/X11/fonts/cyrillic" FontPath "/usr/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/lib/X11/fonts/Type1" FontPath "/usr/lib/X11/fonts/CID" FontPath "/usr/lib/X11/fonts/100dpi" FontPath "/usr/lib/X11/fonts/75dpi" EndSection Section "ServerFlags" Option "AllowMouseOpenFail" "True" Option "BlankTime" "0" EndSection Section "Module" Load "bitmap" Load "dbe" Load "ddc" Load "dri" Load "evdev" Load "extmod" Load "freetype" Load "glx" Load "int10" Load "record" Load "type1" Load "v4l" Load "vbe" EndSection # Keyboards. Section "InputDevice" Identifier "Default Keyboard" Driver "keyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "gb" EndSection Section "InputDevice" Identifier "Remote" Driver "evdev" Option "Device" "/dev/input/remote" EndSection Section "InputDevice" Identifier "First Keyboard" Driver "evdev" Option "Device" "/dev/input/keybrd" EndSection Section "InputDevice" Identifier "Media Keyboard" Driver "evdev" Option "Device" "/dev/input/mmkeys" EndSection # Mice. Section "InputDevice" Identifier "Default Mouse" Driver "mouse" Option "Device" "/dev/input/mice" Option "Protocol" "ExplorerPS/2" EndSection Section "InputDevice" Identifier "No Mouse" Driver "mouse" Option "Device" "/no/mouse" EndSection # Graphics cards. Section "Device" Identifier "Default Video Card" Driver "vesa" EndSection Section "Device" Identifier "VIA" Driver "via" Option "ActiveDevice" "CRT" EndSection Section "Device" Identifier "VIA TV" Driver "via" Option "ActiveDevice" "TV" Option "TVType" "PAL" Option "TVOutput" "S-Video" Option "EnableAGPDMA" "True" EndSection Section "Device" Identifier "Savage" Driver "savage" EndSection Section "Device" Identifier "Radeon" Driver "radeon" Option "BusType" "PCI" Option "ColorTiling" "off" Option "RenderAccel" "off" EndSection # Things attached to the graphics cards. Section "Monitor" Identifier "Default Monitor" EndSection Section "Monitor" Identifier "PAL TV" HorizSync 30-68 VertRefresh 50-120 Mode "720x576" # D: 41.475
Bug#347790: xterm: boldMode patch
Package: xterm
Version: 208-3.1
Followup-For: Bug #347790
The attached patch fixes this issue, and additionally alters the
behavior of boldMode. Previously, boldMode only had an effect on the
primary font. This patch extends the option to also affect the
alternate fonts font1, font2, font3, etc. This, in my opinion, is
more useful, more consistent, and better coincides with the
description in the manpage.
Cheers,
Tim Pope
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable'), (700, 'stable'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.4
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages xterm depends on:
ii libc62.3.6-2 GNU C Library: Shared libraries an
ii libfontconfig1 2.3.2-1.1 generic font configuration library
ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library
ii libncurses5 5.5-1 Shared libraries for terminal hand
ii libsm6 6.9.0.dfsg.1-4 X Window System Session Management
ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li
ii libxaw8 6.9.0.dfsg.1-4 X Athena widget set library
ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte
ii libxft2 2.1.8.2-3 FreeType-based font drawing librar
ii libxmu6 6.9.0.dfsg.1-4 X Window System miscellaneous util
ii libxt6 6.9.0.dfsg.1-4 X Toolkit Intrinsics
ii xlibs6.9.0.dfsg.1-4 X Window System client libraries m
ii xlibs-data 6.9.0.dfsg.1-4 X Window System client data
Versions of packages xterm recommends:
ii xutils6.9.0.dfsg.1-4 X Window System utility programs
-- no debconf information
--- fontutils.c 2006-03-14 15:14:11.0 -0600
+++ fontutils.c.patched 2006-03-14 15:05:53.0 -0600
@@ -704,7 +704,10 @@
}
TRACE(("...derived bold %s\n", myfonts.f_b));
}
- if (fp == 0 || bfs == 0) {
+if (!screen->bold_mode) {
+bfs = nfs;
+TRACE(("...not loading a bold font, as per boldMode\n"));
+} else if (fp == 0 || bfs == 0) {
bfs = nfs;
TRACE(("...cannot load a matching bold font\n"));
} else if (same_font_size(xw, nfs, bfs)
Bug#347790: xterm: boldMode patch
Hi, thanks for the feedback!
On Sun, Mar 19, 2006 at 09:24:46AM -0500, Thomas Dickey wrote:
> I agree that it should do what you're describing, but the patch is applied
> before xterm has found the data that it needs to do the boldMode feature.
> For instance, on the next line (see the context of the patch) it checks to
> see if it was able to derive a bold font specifier. Later it checks if
> that was different from the normal (or font1, etc) font.
I see some problems with my previous approach, most notably a
potential memory leak I'm not sure how I missed. Here's a second
attempt. Perhaps you can tell me if I'm on the right track. Is this
how you would go about it?
Thanks,
Tim Pope
--- fontutils.c 2006-03-14 15:14:11.0 -0600
+++ fontutils.c.dealloc-later 2006-03-19 14:29:02.0 -0600
@@ -789,6 +789,12 @@
bfs = nfs;
}
+if (!screen->bold_mode && bfs != nfs) {
+TRACE(("...ignoring bold font, as per boldMode\n"));
+ XFreeFont(screen->display, bfs);
+ bfs = nfs;
+}
+
if_OPT_WIDE_CHARS(screen, {
if (wfs != 0
&& wbfs != 0
Bug#166234: xserver-xfree86: Removing patch 009_i810_xv_blue_bar_fix.diff fixes problem on i810e
I'm having the same problem on a similar setup with an i810e. Removing debian/patches/009_i810_xv_blue_bar_fix.diff and rebuilding fixes it for me. This fails to address bug #131602, which the patch was the original purpose of the patch. A modification of the patch, however, should be sufficient to close the bug. Bcc: Tim Pope <[EMAIL PROTECTED]> Package: xserver-xfree86 Version: 4.2.1-3 Followup-For: Bug #166234 ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "i810" Driver "i810" EndSection Section "Monitor" Identifier "Dell E770" HorizSync 30-60 VertRefresh 50-75 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "i810" Monitor "Dell E770" DefaultDepth16 SubSection "Display" Depth 1 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen&
Bug#171750: xlibs: XftConfig doesn't map sans/serif/mono
Package: xlibs Version: 4.2.1-3 Severity: important Tags: patch -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux hopper 2.2.22 #6 Sat Sep 21 21:00:42 CEST 2002 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages xlibs depends on: ii libc6 2.2.5-14.3 GNU C Library: Shared libraries an ii libfreetype6 2.1.2-9FreeType 2 font engine, shared lib ii xfree86-common4.2.1-3X Window System (XFree86) infrastr the default /etc/X11/XftConfig shipped with xlibs doesn't contain crucial mappings for the default font families. this is effecting many dependant packages. with the current setup any Gtk+-2.0 based application renders text using the wrong font families (e.g. monospaced/fixed text is rendered with a proportional font). in order to fix this, XftConfig needs to a) map "monospace" (which is the fixed width font gtk asks for) to "mono" and b) provide appropriate mappings for the "sans", "serif" and "mono" font families. appended is a sample XftConfig file based on /etc/X11/XftConfig from xlibs-4.2.1-3 which works with any of the three debian font packages ttf-freefont, msttcorefonts or gsfonts-x11, mapping sans, serif and mono to fonts which support varying weights (bold, etc.; not all fonts come in different weights) and which match the requested family: # Debian XftConfig for ttf-freefont, msttcorefonts or gsfonts-x11 # catch fixed X font queries match any family == "fixed" edit family =+ "mono"; # catch terminal font queries match any family == "console" edit family =+ "mono"; # Gtk+ likes to ask for "Monospace" match any family == "monospace" edit family =+ "mono"; # FreeFont TrueType setup (ttf-freefont) dir "/usr/share/fonts/truetype/freefont" # FreeMono*.ttf FreeSans*.ttf FreeSerif*.ttf match any family == "sans" edit family += "FreeSans"; match any family == "serif" edit family += "FreeSerif"; match any family == "mono" edit family += "FreeMono"; # MS TrueType fonts (msttcorefonts) dir "/usr/share/fonts/truetype" # Sans: Arial*.ttf Verdana*.ttf Trebuchet_MS*.ttf Comic_Sans_MS*.ttf Arial_Black.ttf # Serif: Georgia*.ttf Times_New_Roman*.ttf # Mono: Courier_New*.ttf Andale_Mono.ttf # Other: Impact.ttf Webdings.ttf match any family == "sans" edit family += "Arial"; #match any family == "sans" edit family =+ "Verdana"; #match any family == "sans" edit family =+ "Trebuchet MS"; #match any family == "sans" edit family =+ "Comic Sans MS"; match any family == "serif" edit family += "Georgia"; #match any family == "serif"edit family =+ "Times New Roman"; match any family == "mono" edit family += "Courier New"; # Type1 fonts (gsfonts-x11) dir "/usr/X11R6/lib/X11/fonts/Type1" # Sans: Nimbus_Sans_L* URW_Gothic_L* # Serif: Nimbus_Roman_No9_L* URW_Bookman_L* Century_Schoolbook_L* Bitstream_Charter* URW_Palladio_L* # Mono: Nimbus_Mono_L* Courier_10_Pitch* # Script: URW_Chancery_L* match any family == "sans" edit family += "Nimbus Sans L"; match any family == "serif" edit family += "Nimbus Roman No9 L"; #match any family == "mono" edit family += "Nimbus Mono L"; #match any family == "sans" edit family += "URW Gothic L"; #match any family == "serif"edit family += "URW Bookman L"; match any family == "mono" edit family += "Courier 10 Pitch"; # Check users config file # includeif "~/.xftconfig" # # Alias between XLFD families and font file family name, prefer local # fonts # match any family == "charter" edit family += "bitstream charter"; match any family == "bitstream charter" edit family =+ "charter";
Bug#362465: xserver-xorg: Man page for evdev has dissapeared.
Package: xserver-xorg Version: 6.9.0.dfsg.1-6 Severity: normal This version of xserver-xorg has removed the evdev man page, I'm sure it was there in previous versions. -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 17 2006-01-24 13:29 /etc/X11/X -> /usr/bin/X11/Xorg -rwxr-xr-x 1 root root 1878204 2006-04-04 04:44 /usr/bin/X11/Xorg Contents of /var/lib/xfree86/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: :01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266] /etc/X11/xorg.conf does not match checksum in /var/lib/xfree86/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 5481 2006-04-05 23:16 /etc/X11/xorg.conf Xorg X server log files on system: -rw-r--r-- 1 root root 45654 2006-04-12 20:38 /var/log/Xorg.0.log -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg depends on: ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libgcc1 1:4.1.0-1 GCC support library ii libxau6 6.9.0.dfsg.1-6 X Authentication library ii libxdmcp6 6.9.0.dfsg.1-6 X Display Manager Control Protocol ii xserver-common6.9.0.dfsg.1-6 files and utilities common to all ii zlib1g1:1.2.3-11 compression library - runtime Versions of packages xserver-xorg recommends: pn discover | discover1 (no description available) ii laptop-detect 0.12.1 attempt to detect a laptop ii mdetect 0.5.2.1mouse device autodetection tool ii xlibs 6.9.0.dfsg.1-6 X Window System client libraries m ii xresprobe 0.4.18-1 X Resolution Probe -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#365341: xft: Neither package includes debug symbols.
Package: xft Version: 2.1.8.2 Severity: important Tags: patch, etch, sid I needed to debug a problem involving a crash in libxft.so.2 (This seems not to be due to a bug in this library). But, it turns out, that: 1. The libxft2-dbg package does not contain any libraries. 2. According to the rules file the intention was to keep debugging symbols in the main package libxft2. Nevertheless, that is not the case. Even _after_changing_ the definition PACKAGE = libxft1 (in debian/rules), which causes a dh_strip --dbg-package=libxft1 , the resulting library gets stripped. Solution(s) Either, simply comment out the line dh_strip --dbg-package=$(PACKAGE) making the definition of PACKAGE obsolete. Or, put the debugging enabled libraries into the -dbg package. I guess there is something about that in the policy, but I am too lazy to search for that. greets, t1m -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.5-upagupta Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
