Bug#622581: nouveau driver fails to load with error undefined symbol: miEmptyData
Package: xserver-xorg-video-nouveau Version: 1:0.0.16+git20101210+8bb8231-2 Severity: critical Just installed new the kernel+drm+x11 in testing, and I get start x11. It dies with a dlopen error complaining of an undefined symbol. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Aug 13 2008 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1926464 Mar 25 22:49 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: nVidia Corporation G72 [GeForce 7300 SE/7200 GS] [10de:01d3] (rev a1) Xorg X server configuration file status: -rw-r--r-- 1 root root 2735 Oct 26 11:18 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- # xorg.conf (X.Org 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 InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us,il Option XkbVariant,lyx Option XkbOptions grp:shifts_toggle,grp_led:scroll,grp:win_switch EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section Device Identifier Configured Video Device Driver nouveau Option Monitor-DVI-I-1 VP2030b Option Monitor-VGA-1 VP2030b2 EndSection Section Monitor Identifier VP2030b EndSection Section Monitor Identifier VP2030b2 Option RightOf VP2030b EndSection #Section Monitor # Identifier Monitor Not Appearing In This Config # Option Ignore 1 #EndSection Section Screen Identifier Default Screen Monitor VP2030b Monitor VP2030b2 SubSection Display Virtual 3200 1600 EndSubSection EndSection Section ServerLayout Identifier Itai #Screen LCD #Screen CRT Screen Default Screen #InputDevice Configured Mouse #InputDevice Generic Keyboard Option Xinerama 0 EndSection #Commented out 11/18/09. #Updated notes: (12/04/09) # * Commenting out didn't change much for stability. # * Kernel update on 11/26/09.seems to have fixed things; # * Tried again. decided to leave commented out b/c seems it's not actually #necessary. Once I ran the glxgears from the mesa directory everything was #fine. May be an issue for running system 3D programs # Section ServerFlags Option GlxVisuals all EndSection #Section ServerFlags # Option Xinerama 1 #EndSection Section Device Identifier VD0 Driver nouveau Screen 0 EndSection Section Device Identifier VD1 Driver nouveau Screen 1 EndSection Section Screen Identifier LCD Monitor VP2030b Device VD1 SubSection Display Modes 1600x1200 ViewPort 0 0 EndSubSection EndSection Section Screen Identifier CRT Monitor E75 Device VD0 SubSection Display Modes 1280x1024 ViewPort 1600 0 EndSubSection EndSection /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 Xorg X server log files on system: -- -rw-r--r-- 1 root root 111075 Nov 9 2009 /var/log/Xorg.1.log -rw-r--r-- 1 root root 40647 Nov 24 01:21 /var/log/Xorg.3.log -rw-r--r-- 1 root root 32622 Dec 15 11:13 /var/log/Xorg.2.log -rw-r--r-- 1 root root 5874 Apr 13 01:57 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 1605.079] X.Org X Server 1.9.5 Release Date: 2011-03-17 [ 1605.079] X Protocol Version 11, Revision 0 [ 1605.079] Build Operating System: Linux 2.6.38-1-amd64 x86_64 Debian [ 1605.079]
Bug#622581: nouveau driver fails to load with error undefined symbol: miEmptyData
On Wed, Apr 13, 2011 at 09:33:42AM +0200, Sven Joachim wrote: On 2011-04-13 09:01 +0200, Itai Seggev wrote: Just installed new the kernel+drm+x11 in testing, and I get start x11. It dies with a dlopen error complaining of an undefined symbol. I suppose that is because you have outdated locally installed files. Did you build nouveau from source some time in the past? [ 1605.083] (II) LoadModule: nouveau [ 1605.083] (II) Loading /usr/lib/xorg/modules/nouveau_drv.so This file is not supposed to exist, the nouveau module from the Debian package lives in /usr/lib/xorg/modules/drivers/. Move /usr/lib/xorg/modules/nouveau_drv.so out of the way and retry. Yes, this was problem. Thanks, and sorry for the noise. -- Itai In 1997 a group of programmers started writing a desktop environment to fix a travesty they didn't create. Their program promptly found its way onto un*x systems everywhere. Today, still opposed by a software monopolist, they survive as soldiers of fortune. If you share their vision, if you know you can help, and if you can connect to internet, maybe you can join... the K-Team. -- 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/20110413154514.ga3...@knuth.cs.hmc.edu
problems with xserver 1.7
Hi X guys: I have upgrade to the xserver packages in experimental, and I'm have some difficulties which I'm not sure what to report them against. Any solutions/suggestions for packages to report against would be appreciate. I can provide xorg.conf and Xorg.0.log. I'd be happy to supply other useful data. Note: I am using nouveau_drv corresponding kernel from git sources. 1) Xrandr is weird. Doing xrandr --output DVI-I-0 --auto crashes the server. Doing xrandr --output DVI-I-0 --size 1600x1200 (the natural size of the lcd) produces the obscure message Output TV-0 is not disconnected but has no modes. I've never seen TV-output with this card. I'm not sure it even has it. 2) Xv has vanished. xvinfo reports no adaptor presents Downgrading back to Xserver 1.6 solves both of these problems. -- Itai Itai Seggev, Knox College, Mathematics Department In 1997 a group of programmers started writing a desktop environment to fix a travesty they didn't create. Their program promptly found its way onto un*x systems everywhere. Today, still opposed by a software monopolist, they survive as soldiers of fortune. If you share their vision, if you know you can help, and if you can connect to internet, maybe you can join... the K-Team. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532995: synclient output for two and three-fingered failure
On Tue, Jul 07, 2009 at 06:55:36PM -0700, Don Armstrong wrote: On Tue, 07 Jul 2009, Itai Seggev wrote: On Sat, Jun 20, 2009 at 12:25:58PM -0700, Don Armstrong wrote: On Sat, 20 Jun 2009, Don Armstrong wrote: Here is the output; I can reconfirm that this happens on powerbooks. synclient -m 1; registers two fingers, so at least that part is working properly. Ah, now I see the problem. If I do: synclient -s -l; I see that TapButton1 isn't set. synclient -s TapButton1=1 TapButton2=3 TapButton3=1; resolves these issues. Itai: doing the above will probably fix it for you too. I tried it, but it didn't have much of an effect. All it did was set two fingers to right click and three fingers to left click, but it had no effect on single finger tap. I can set TapButton1 to pretty much any value without any effect. Is there some other setting I should be mucking with? What's the ouptut of synclient -s -l; ? Are you changing the values using -s? Sorry it's taken me three months to reply. I thought I had, but apprently not. Sometime in the last couple of weeks (new Xserver was put out), the behavior changed. Now, synclient will allow me to assign all three taps at will. However, the settings in xorg.conf are completely ignored, and all three taps are set to zero but defaults. I can work around this by adding synclient to Xsetup, but it would be nice to understand why xorg.conf is being ignore and if its possible to fix this. -- Itai Itai Seggev, Knox College, Mathematics Department In 1997 a group of programmers started writing a desktop environment to fix a travesty they didn't create. Their program promptly found its way onto un*x systems everywhere. Today, still opposed by a software monopolist, they survive as soldiers of fortune. If you share their vision, if you know you can help, and if you can connect to internet, maybe you can join... the K-Team. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#368818: x11-common: insufficient error checking in Xsession can prevent users from logging in
On Wed, Aug 15, 2007 at 12:10:10AM +0200, Brice Goglin wrote: Hi, I am trying to see what to do with this old bug, but I don't see yet why COLUMNS would be set to 0 and why we should support this (buggy?) case. Do you guys know any valid use of COLUMNS=0 ? No, there is no valid reason for COLUMNS=0. There have been versions of 'resize' which incorrectly reported sizes of 0 on various terminals, but such buggy version are hard to find these days (as are actual terminals, :) so it may simply be a matter of those bugs no longer being triggered). As I noted in my original report, this behaviour was some underlying bug which I was never able to find. I don't entirely understand the whole logic of Xsession and Xsession.d, so I'm not sure what, if anything, in the scripts was causing COLUMNS=0. Perhaps some version of my shell was buggy. (I think tcsh users were _not_ affected, but I no longer recall). I, personally, think the error check is trivial and worth it, but of course the final decision is up to you. I've just tested removing COLUMNS=80 from the script, and it seems to be working fine, so I'm OK with the bug being closed. -- Itai Itai Seggev, Knox College In 1997 a group of programmers started writing a desktop environment to fix a travesty they didn't create. Their program promptly found its way onto un*x systems everywhere. Today, still opposed by a software monopolist, they survive as soldiers of fortune. If you share their vision, if you know you can help, and if you can connect to internet, maybe you can join... the K-Team. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430885: xserver-xorg-video-intel: new intel driver doesn't support all modes of i810 driver
On Thu, Aug 09, 2007 at 12:44:56AM +0200, Brice Goglin wrote: Drew Parsons wrote: Your X log reports that the server knows about your desired mode: (II) intel(0): Modeline 1280x1024x85.0 157.50 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync (91.1 kHz) (II) intel(0): Modeline 1280x1024x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz) (II) intel(0): Modeline 1280x1024x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz) Do you have xrandr 1.2 installed? What does xrandr say? Does xrandr --verbose show the modes listed above? Did you select your mode with xrandr --mode 1280x1024? Work is ongoing in the server to make xorg.conf redundant altogether. One thing you could try is deleting xorg.conf completely and seeing what kind of success you get. Or alternatively delete the Modes lines from the Screen section. Hi Itai, Any news about this? Could you reply to what Drew requested above? It would for instance let us know whether your monitor has a preferred mode, which might explain why the new driver chooses one mode instead of another. Thanks, Brice Sorry, I thought I had replied to this... The output to the first two commands is below. I didn't know about xrandr and using it to resize. When I tried the command above involving --mode, I got a usage message but that's it. I'll be losing access to this machine in a few days (new job), so I won't be able to help with tings for much longer. -- Itai Seggev Visiting Assistant ProfessorOffice: Lewis 121A Department of Physics and Astronomy Phone: +1-662-915-3887 University of Mississippi Fax: +1-662-915-5045 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430885: xserver-xorg-video-intel: new intel driver doesn't support all modes of i810 driver
On Thu, Aug 09, 2007 at 08:30:11AM +0200, Brice Goglin wrote: Itai Seggev wrote: The output to the first two commands is below. Did you forget to paste it ? *sigh* That's what I get for sending email at 1am. It's at the end of the email. I didn't know about xrandr and using it to resize. When I tried the command above involving --mode, I got a usage message but that's it. You need to upgrade xbase-clients to 7.2 (in testing). I'm already at 7.2. Is there something else I need to check? het:/etc/X11# dpkg -l xbase-clients Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii xbase-clients 1:7.2.ds2-2miscellaneous X clients I'll be losing access to this machine in a few days (new job), so I won't be able to help with tings for much longer. Ok, if you're not able to test/debug/help things anymore for this bug, we'll probably close it until somebody else meets it. But I am pretty confident that your problem is just about the preferred mode of your monitor not being the largest one, and xrandr should allow to change it after starting X. Screen 0: minimum 320 x 200, current 1280 x 768, maximum 2048 x 2048 VGA connected 1280x768+0+0 (normal left inverted right) 0mm x 0mm 2048x1536 60.0 1920x1440 60.0 1856x1392 60.0 1792x1344 60.0 1920x1200 72.8 60.0 1600x1200 75.0 70.0 65.0 60.0 1680x1050 60.0 1600x1024 60.0 1400x1050 85.3 74.8 70.0 60.0 1280x1024 85.0 75.0 60.0 1440x900 60.2 1280x960 85.0 60.0 1280x800 60.0 1152x864 85.1 75.0 1280x768 60.0* 1152x768 54.8 1024x768 85.0 75.0 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 72.8 75.0 59.9 720x40085.0 640x40085.1 640x35085.1 Screen 0: minimum 320 x 200, current 1280 x 768, maximum 2048 x 2048 VGA connected 1280x768+0+0 normal (normal left inverted right) 0mm x 0mm Identifier: 0x43 Timestamp: 1227476509 Subpixel: unknown Clones: CRTC: 0 CRTCs: 0 2048x1536 (0x44) 266.9MHz h: width 2048 start 2200 end 2424 total 2800 skew0 clock 95.3KHz v: height 1536 start 1537 end 1540 total 1589 clock 60.0Hz 1920x1440 (0x45) 234.0MHz h: width 1920 start 2048 end 2256 total 2600 skew0 clock 90.0KHz v: height 1440 start 1441 end 1444 total 1500 clock 60.0Hz 1856x1392 (0x46) 218.3MHz h: width 1856 start 1952 end 2176 total 2528 skew0 clock 86.4KHz v: height 1392 start 1393 end 1396 total 1439 clock 60.0Hz 1792x1344 (0x47) 204.8MHz h: width 1792 start 1920 end 2120 total 2448 skew0 clock 83.7KHz v: height 1344 start 1345 end 1348 total 1394 clock 60.0Hz 1920x1200 (0x48) 230.0MHz h: width 1920 start 1936 end 2096 total 2528 skew0 clock 91.0KHz v: height 1200 start 1201 end 1204 total 1250 clock 72.8Hz 1920x1200 (0x49) 193.2MHz h: width 1920 start 2048 end 2256 total 2592 skew0 clock 74.5KHz v: height 1200 start 1201 end 1204 total 1242 clock 60.0Hz 1600x1200 (0x4a) 202.5MHz h: width 1600 start 1664 end 1856 total 2160 skew0 clock 93.8KHz v: height 1200 start 1201 end 1204 total 1250 clock 75.0Hz 1600x1200 (0x4b) 189.0MHz h: width 1600 start 1664 end 1856 total 2160 skew0 clock 87.5KHz v: height 1200 start 1201 end 1204 total 1250 clock 70.0Hz 1600x1200 (0x4c) 175.5MHz h: width 1600 start 1664 end 1856 total 2160 skew0 clock 81.2KHz v: height 1200 start 1201 end 1204 total 1250 clock 65.0Hz 1600x1200 (0x4d) 162.0MHz h: width 1600 start 1664 end 1856 total 2160 skew0 clock 75.0KHz v: height 1200 start 1201 end 1204 total 1250 clock 60.0Hz 1680x1050 (0x4e) 147.1MHz h: width 1680 start 1784 end 1968 total 2256 skew0 clock 65.2KHz v: height 1050 start 1051 end 1054 total 1087 clock 60.0Hz 1600x1024 (0x4f) 106.9MHz h: width 1600 start 1620 end 1640 total 1670 skew0 clock 64.0KHz v: height 1024 start 1027 end 1030 total 1067 clock 60.0Hz 1400x1050 (0x50) 184.0MHz h: width 1400 start 1464 end 1656 total 1960 skew0 clock 93.9KHz v: height 1050 start 1051 end 1054 total 1100
Bug#430885: xserver-xorg-video-intel: new intel driver doesn't support all modes of i810 driver
On Thu, Aug 09, 2007 at 08:30:11AM +0200, Brice Goglin wrote: I didn't know about xrandr and using it to resize. When I tried the command above involving --mode, I got a usage message but that's it. You need to upgrade xbase-clients to 7.2 (in testing). From a subsequent email in this thread, I figured out that I need to add --output VGA to the command line. Once I did this, I was able to set the resolution to my desired resolution. It still seems to be a bug that before the upgrade in respected my preferences in xorg.conf, but afterwards it didn't. -- Itai Seggev Visiting Assistant ProfessorOffice: Lewis 121A Department of Physics and Astronomy Phone: +1-662-915-3887 University of Mississippi Fax: +1-662-915-5045 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430885: xserver-xorg-video-intel: new intel driver doesn't support all modes of i810 driver
On Thu, Aug 09, 2007 at 06:15:53PM +0200, Brice Goglin wrote: Get a modeline with: $ gtf 1280 1024 75 # 1280x1024 @ 75.00 Hz (GTF) hsync: 80.17 kHz; pclk: 138.54 MHz Modeline 1280x1024_75.00 138.54 1280 1368 1504 1728 1024 1025 1028 1069 -HSync +Vsync And then add the last line above and the following to the monitor section of your xorg.conf Option PreferredMode 1280x1024_75.00 (as explained in http://www.tetromino.net/blog/2007/04/25/manual-modesetting-for-xf86-video-intel/) OK. This fixed it (and I learned a few things along the way). Many thanks! -- Itai Itai Seggev, University of Mississippi, Department of Physics and Astronomy In 1997 a group of programmers started writing a desktop environment to fix a travesty they didn't create. Their program promptly found its way onto un*x systems everywhere. Today, still opposed by a software monopolist, they survive as soldiers of fortune. If you share their vision, if you know you can help, and if you can connect to internet, maybe you can join... the K-Team. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430885: xserver-xorg-video-intel: new intel driver doesn't support all modes of i810 driver
Package: xserver-xorg-video-intel Version: 2:2.0.0-1 Severity: normal This seems very similar to bug #424952, but manifests differently. I have a Dell Dimension with an i845 Rev 1 graphics. I've been happily using it in 1280x1024 mode for a couple of years. I upgraded today to the new intel driver and and X started using modes with a 4:3 aspect ratio. If I tried to force 1280x1024, I would get no usable screen. Downgrading to the i810 (1.7.2-4) fixed the problem. If there's more data you need, let me know. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: LANG=he_IL.UTF-8, LC_CTYPE=he_IL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-video-intel depends on: ii libc6 2.5-9+b1 GNU C Library: Shared libraries ii libdrm2 2.3.0-4 Userspace interface to kernel DRM ii xserver-xorg-core 2:1.3.0.0.dfsg-6 X.Org X server -- core server xserver-xorg-video-intel recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430885: xserver-xorg-video-intel: new intel driver doesn't support all modes of i810 driver
On Thu, Jun 28, 2007 at 01:03:27AM +0200, Brice Goglin wrote: Itai Seggev wrote: Package: xserver-xorg-video-intel Version: 2:2.0.0-1 Severity: normal Please try xserver-xorg-video-intel 2:2.0.0-5 currently in experimental. It contains a much more recent git snapshot. If it does not help, please send the whole output of /usr/share/bug/xserver-xorg/script 31 OK, I tried this, same result. Although it seems I was mistaken about 4:3 in my bug report. It's the resolution it selects is actually 1280x768, not 1280x960. Output of the bug script is below. I thought this bug might be because I hadn't cleaned out all the xfree86 cruft from my xorg.conf, so I generated a new xorg.conf using dpkg-reconfigure xserver-xorg. That didn't make any difference, but I'm including that alternate config at the very end for completeness Contents of /var/lib/x11/X.roster: xserver-xfree86 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 2006-07-12 22:56 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1736280 2007-06-01 08:28 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) /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 3366 2007-06-27 17:42 /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 commands as root: # # cp /etc/X11/xorg.conf /etc/X11/xorg.conf.custom # md5sum /etc/X11/xorg.conf /var/lib/xfree86/xorg.conf.md5sum # dpkg-reconfigure xserver-xorg Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/share/fonts/X11/misc FontPath/usr/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/CID FontPath/usr/lib/X11/fonts/CID FontPath/usr/share/fonts/X11/100dpi FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section Module Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us,il Option XkbVariant,lyx Option XkbOptions grp:switch,grp:shifts_toggle,grp_led:scroll EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol ImPS/2 Option Emulate3Buttons false Option ZAxisMapping 4 5 EndSection Section Device Identifier Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device Driver i810 EndSection Section Monitor Identifier Generic Monitor Option DPMS HorizSync 30-100 VertRefresh 50-160 EndSection Section Screen Identifier Default Screen Device Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes
Bug#368817: x11-common: man page for Xsession.options fails to document use-session-dbus
Package: x11-common Version: 6.9.0.dfsg.1-6 Severity: minor The default Xsession.options now has 5 options in it, the last being use-session-dbus. This option is not documented in the corresponding man page, however. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (110, 'unstable'), (10, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16cavy1 Locale: LANG=he_IL.UTF-8, LC_CTYPE=he_IL.UTF-8 (charmap=UTF-8) Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.5.1 Debian configuration management sy ii debianutils 2.16 Miscellaneous utilities specific t ii lsb-base 3.1-5 Linux Standard Base 3.1 init scrip x11-common recommends no packages. -- debconf information: x11-common/experimental_packages: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368818: x11-common: insufficient error checking in Xsession can prevent users from logging in
Package: x11-common
Version: 6.9.0.dfsg.1-6
Severity: normal
If fold is given zero columns as an argument, it dies with the error
message below. If the $COLUMNS enivornment variable is for some reason
set to zero, then the command fold -s -w ${COLUMNS:-80} in
Xsessions's message functions will cause xinit to die with only the
following output in .xsession-errors:
Xsession: X session started for iseggev at Wed May 24 23:51:20 CDT 2006
fold: invalid number of columns: `0'
The result is that the user cannot log in. This can be fixed by
setting COLUMNS=80 by hand in Xsession.
Clearly the ultimate cause is some underlying bug which I have yet to
identify. I would appreciate help in tracking down that bug as well,
but given the ugly results for X and simple work around, (test
COLUMNS and set it to 80 if it equals zero), I'm filing this bug.
This never happened to me in the past; it started happening today
after an upgrade. Kdm and curses seem like the most likely culprits of
the packages upgraded today. The really wierd thing is that it only
happens for some accounts and not others. I don't entirely understand
the X login process, which makes it difficult for me to figure out
exactly why this is happening. Any help would be appreciated.
Thanks,
Itai
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (110, 'unstable'), (10, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16cavy1
Locale: LANG=he_IL.UTF-8, LC_CTYPE=he_IL.UTF-8 (charmap=UTF-8)
Versions of packages x11-common depends on:
ii debconf [debconf-2.0] 1.5.1 Debian configuration management sy
ii debianutils 2.16 Miscellaneous utilities specific t
ii lsb-base 3.1-5 Linux Standard Base 3.1 init scrip
x11-common recommends no packages.
-- debconf information:
x11-common/experimental_packages:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352833: xlibs: xkb no longer handles grp:shift_toggle)
I think this information (renaming the option) should be put in the NEWS.Debian.gz file. When I first upgraded to 6.9 and discovered shift_toggle no lnoger works, I looked first in the bug tracking system[1], then NEWS.Debian.gz. This file mentioned major changes to xkb and recommended installing xkb-data (which I think was in experimental at the time, but was of no help in any event), but not this specific fix. I think this is worth mentioning. [1] I thought I had reported bug about this, but apprently I forgot to the repeat was eaten by @[EMAIL PROTECTED] exim. Fortunately, exim no longer runs on that box. -- Itai Itai Seggev, University of Mississippi, Department of Physics and Astronomy In 1997 a group of programmers started writing a desktop environment to fix a travesty they didn't create. Their program promptly found its way onto un*x systems everywhere. Today, still opposed by a software monopolist, they survive as soldiers of fortune. If you share their vision, if you know you can help, and if you can connect to internet, maybe you can join... the K-Team. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#234082: Subject: xbase-clients: [xkb] can't switch vt's when -compat group_led is set
Package: xbase-clients Version: 4.3.0-2 Severity: normal Tags: sid I used the following keyboard options : -compat group_led -symbols us(pc104)+il+group(shift_toggle)+group(switch) This worked just fine with 4.2. Since the upgrade to 4.3, control-alt-F$vt combinations to swithc virtual terminals have stopped working. If I set -compat to default, then they start working again. Of course, then I don't know which keyboard layout I'm using. :) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.0-grvisitor1 Locale: LANG=en_US.UTF-8, LC_CTYPE=he_IL.UTF-8 Versions of packages xbase-clients depends on: ii cpp 4:3.3.2-3 The GNU C preprocessor (cpp) ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdps1 4.3.0-2Display PostScript (DPS) client li ii libexpat1 1.95.6-6 XML parsing C library - runtime li ii libfontconfig12.2.1-14 generic font configuration library ii libfreetype6 2.1.7-2FreeType 2 font engine, shared lib ii libice6 4.3.0-2Inter-Client Exchange library ii libncurses5 5.3.20030719-5 Shared libraries for terminal hand ii libpng12-01.2.5.0-4 PNG library - runtime ii libsm64.3.0-2X Window System Session Management ii libstdc++51:3.3.3-1 The GNU Standard C++ Library v3 ii libxaw7 4.3.0-2X Athena widget set library ii libxcursor1 1.0.2-4X Cursor management library ii libxext6 4.3.0-2X Window System miscellaneous exte ii libxft2 2.1.2-5FreeType-based font drawing librar ii libxi64.3.0-2X Window System Input extension li ii libxmu6 4.3.0-2X Window System miscellaneous util ii libxmuu1 4.3.0-2lightweight X Window System miscel ii libxpm4 4.3.0-2X pixmap library ii libxrandr24.3.0-2X Window System Resize, Rotate and ii libxrender1 0.8.3-5X Rendering Extension client libra ii libxt64.3.0-2X Toolkit Intrinsics ii libxtrap6 4.3.0-2X Window System protocol-trapping ii libxtst6 4.3.0-2X Window System event recording an ii libxv14.3.0-2X Window System video extension li ii xlibmesa-gl [libgl1] 4.3.0-2Mesa 3D graphics library [XFree86] ii xlibmesa-glu [libglu1]4.3.0-2Mesa OpenGL utility library [XFree ii xlibs 4.3.0-2X Window System client libraries m ii xlibs-data4.3.0-2X Window System client data ii zlib1g1:1.2.1-4 compression library - runtime -- no debconf information
Bug#234082: workaround
OK, it appears that X 4.3 has new options (grp_led:scroll) which provide the same behaviour as I had under 4.2 and don't cause problems. It still seems like a bug that compat was accept w/o any warnings but gave bad behaviour, but at least there's a workaround. --Itai
