Processed: tagging 256706
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.4 # fixed in Debian X Strike Force XFree86 repository; to view, run svn diff -r 1772:1773 svn://necrotic.deadbeast.net/xfree86 tags 256706 + pending Bug#256706: xlibs: attaching multiple modifiers to the same key wreaks havoc; breaks Win+Tab switching in many window managers Tags were: patch moreinfo help upstream Bug#259740: xlibs: Windows key no longer treated as modifer, just as Super_L Bug#260232: xlibs: modifier madness breaks XTerm*metaSendsEscape Bug#263073: xlibs: Super keys now Super+Hyper Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
X Strike Force XFree86 SVN commit: r1775 - in branches/debconf-overhaul/debian: . patches
Author: branden
Date: 2004-08-30 23:43:25 -0500 (Mon, 30 Aug 2004)
New Revision: 1775
Modified:
branches/debconf-overhaul/debian/CHANGESETS
branches/debconf-overhaul/debian/TODO
branches/debconf-overhaul/debian/changelog
branches/debconf-overhaul/debian/patches/000_stolen_from_HEAD.diff
branches/debconf-overhaul/debian/patches/000_stolen_from_HEAD_xkb_data.diff
branches/debconf-overhaul/debian/patches/087_xkb_fix_altwin.diff
branches/debconf-overhaul/debian/xserver-xfree86.config.in
Log:
Merge revisions 1770 to HEAD from trunk.
Modified: branches/debconf-overhaul/debian/CHANGESETS
===
--- branches/debconf-overhaul/debian/CHANGESETS 2004-08-31 04:19:41 UTC (rev
1774)
+++ branches/debconf-overhaul/debian/CHANGESETS 2004-08-31 04:43:25 UTC (rev
1775)
@@ -14,7 +14,7 @@
Miscellaneous cosmetic fixes.
1607, 1608, 1624, 1626, 1627, 1636, 1651, 1654, 1663, 1664, 1675, 1685,
-1690, 1713, 1715, 1716, 1718, 1736, 1737, 1743, 1761, 1768
+1690, 1713, 1715, 1716, 1718, 1736, 1737, 1743, 1761, 1768, 1774
Grab latest version of XTerm (#191) from Thomas Dickey's website.
1609
@@ -492,6 +492,18 @@
Make xserver-xfree86 config script's validate_monitor_frequency_db_input()
function more strict, so it doesn't regard open-ended ranges like 40- as
valid.
-1766, 1769
+1766, 1769, 1772
+Grab from XFree86 CVS (2003-12-18) several fixes for keyboard issues:
++ Fix for XKB map 'altwin' to avoid one keysym to more than one modifier
+ mapping (Ivan Pascal). This really fixes the Alt-Tab issue.
+ (Closes: #256706)
++ Fix xmodmap's output of the modifiers map to not display BadKey when
+ the first column keysym is empty (Ivan Pascal).
++ The modifier_add none construct was introduced by Ivan Pascal some
+ times ago, but it was not documented in the changelog and a piece was
+ missing to enable this feature. No keymaps currently use this feature,
+ but users may find it useful with broken keymaps.
+1773
+
vim:set ai et sts=4 sw=4 tw=80:
Modified: branches/debconf-overhaul/debian/TODO
===
--- branches/debconf-overhaul/debian/TODO 2004-08-31 04:19:41 UTC (rev
1774)
+++ branches/debconf-overhaul/debian/TODO 2004-08-31 04:43:25 UTC (rev
1775)
@@ -50,21 +50,7 @@
+ Use /proc/hardware on m68k architecture to set a reasonable default mouse
port. See URL: http://lists.debian.org/debian-68k/2004/08/msg00392.html.
* Add FAQ entry describing Debian's plans in the X department.
-* #256706: keep swatting away at the keyboard modifer issue; Ivan Pascal told
- BR:
-There is not modifier_del instruction in 'XKB language' but ...
-I made a simple change for xkbcomp and now it understands an instruction
-like
- modifier_add none { LALT };
-It removes the modifier binding from the specified key.
-I'm sorry I forget to mention this patch in CHANGELOG but it was a part
-of 667 change made at Dec 18 14:14:37 2003 (i.e. it is included in 4.4.0).
-If your xkbcomp is later than that version it understands such instruction.
- So I'm thinking the fix is to apply the above, then modify the symbol maps
- such that (in most cases) any keys that get modifier mappings are cleared
- first. This solution will absolutely positively need testing.
-
4.3.0.dfsg.1-8
--
Modified: branches/debconf-overhaul/debian/changelog
===
--- branches/debconf-overhaul/debian/changelog 2004-08-31 04:19:41 UTC (rev
1774)
+++ branches/debconf-overhaul/debian/changelog 2004-08-31 04:43:25 UTC (rev
1775)
@@ -438,6 +438,19 @@
* Add Danish translation of Generic Video Card to
xserver-xfree86.config.in. Thanks to Anders Dybdal.
+ Changes by Denis Barbier:
+
+ * Grab from XFree86 CVS (no later than 2003-12-18) several fixes to XKB:
++ Fix for XKB map 'altwin' to avoid one keysym to more than one modifier
+ mapping (Ivan Pascal). This really fixes the Alt-Tab issue.
+ (Closes: #256706)
++ Fix xmodmap's output of the modifiers map to not display BadKey when
+ the first column keysym is empty (Ivan Pascal).
++ The modifier_add none construct was introduced by Ivan Pascal some
+ times ago, but it was not documented in the changelog and a piece was
+ missing to enable this feature. No keymaps currently use this feature,
+ but users may find it useful with broken keymaps.
+
-- Branden Robinson [EMAIL PROTECTED] Mon, 30 Aug 2004 14:22:49 -0500
xfree86 (4.3.0.dfsg.1-6) unstable; urgency=low
Modified: branches/debconf-overhaul/debian/patches/000_stolen_from_HEAD.diff
===
--- branches/debconf-overhaul/debian/patches/000_stolen_from_HEAD.diff
2004-08-31 04:19:41 UTC (rev 1774)
+++
Processed: tagging 256706
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.4 # that which is pending does not need more info or help tags 256706 - moreinfo help Bug#256706: xlibs: attaching multiple modifiers to the same key wreaks havoc; breaks Win+Tab switching in many window managers Tags were: pending patch moreinfo help upstream Bug#259740: xlibs: Windows key no longer treated as modifer, just as Super_L Bug#260232: xlibs: modifier madness breaks XTerm*metaSendsEscape Bug#263073: xlibs: Super keys now Super+Hyper Tags removed: moreinfo, help End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#237877: Patch to allow removal of -dpi 100 override
Adding this patch: --- xc/programs/Xserver/hw/xfree86/common/xf86Priv.h2004-08-31 15:50:38.0 +1000 +++ xc/programs/Xserver/hw/xfree86/common/xf86Priv.h2004-08-31 15:49:51.0 +1000 @@ -98,7 +98,7 @@ #define DEFAULT_LOG_VERBOSE3 #endif #ifndef DEFAULT_DPI -#define DEFAULT_DPI75 +#define DEFAULT_DPI100 #endif #define DEFAULT_UNRESOLVED TRUE And removing the '-dpi 100' parts from 905_debian_xdm.diff: --- debian/patches/905_debian_xdm.diff 2004-08-31 15:54:15.0 +1000 +++ debian/patches/905_debian_xdm.diff~ 2004-08-31 15:53:46.0 +1000 @@ -12,7 +12,8 @@ * config/Xres.cpp: report OS name in greeter widget * config/Xserv.ws.cpp: - add comments to help local admins -- run local server with TCP listening turned off for security +- run local server with DPI setting forced to 100 and TCP listening + turned off for security * config/Xsession: replace guts with simple call to Debian's Xsession script * config/xdm-conf.cpp: @@ -117,7 +118,7 @@ +XCOMM Examples for multiple local X displays: +XCOMM :0 local BINDIR/X :0 vt9 -depth 15 -nolisten tcp +XCOMM :1 local BINDIR/X :1 vt10 -depth 8 -nolisten tcp -+:0 local BINDIR/X DEFAULTVT -nolisten tcp ++:0 local BINDIR/X DEFAULTVT -dpi 100 -nolisten tcp diff -urN xc/programs/xdm~/config/Xsession xc/programs/xdm/config/Xsession --- xc/programs/xdm~/config/Xsession 2001-01-17 18:45:24.0 -0500 +++ xc/programs/xdm/config/Xsession2003-02-23 18:29:33.0 -0500 Should give the desired behaviour, ie: - Use -dpi arg if given by user modifying conffile - Use DisplaySize if given in XF86Config-4 - Use DCC if available - Fallback to 100dpi -- - Gus
Processed: severity of 257515 is wishlist, merging 133344 257515
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.4 severity 257515 wishlist Bug#257515: xserver-xfree86: [debconf] keyboard layout template should tell U.K. users to use 'gb' Severity set to `wishlist'. merge 133344 257515 Bug#133344: xserver-xfree86: [debconf] instruct U.K. people to use layout 'gb' in XKB configuration Bug#257515: xserver-xfree86: [debconf] keyboard layout template should tell U.K. users to use 'gb' Merged 133344 257515. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#149586: marked as done (xserver-xfree86: [debconf] errors from discover should not be fatal to config script)
Your message dated Tue, 31 Aug 2004 01:38:45 -0500 with message-id [EMAIL PROTECTED] and subject line closing old fixed bug has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 10 Jun 2002 17:27:57 + From [EMAIL PROTECTED] Mon Jun 10 12:27:57 2002 Return-path: [EMAIL PROTECTED] Received: from morimoto.progeny.com [216.37.46.163] (31010fa8bab79cb1fadec85d7181dca0) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 17HSxQ-0005z7-00; Mon, 10 Jun 2002 12:27:56 -0500 Received: from albus.progeny.com (albus.progeny.com [192.168.1.14]) by morimoto.progeny.com (Postfix) with ESMTP id 61115636A7; Mon, 10 Jun 2002 12:27:53 -0500 (EST) Received: by albus.progeny.com (Postfix, from userid 10018) id 1BE1D181E3; Mon, 10 Jun 2002 12:27:53 -0500 (EST) Subject: xserver-xfree86: discover can cause preconfigure to fail From: John R. Daily [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] X-Mailer: reportbug 1.99.37 Date: Mon, 10 Jun 2002 12:27:52 -0500 Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Package: xserver-xfree86 Version: 4.1.0-17 Severity: normal Discover failures should be handled more gracefully: Preconfiguring packages ... discover: unrecognized option `--format=%V %M\t%S\t%D\n' xserver-xfree86 failed to preconfigure, with exit status 64 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS 01:00.0 Class 0300: 1002:5046 ### 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 FontPathunix/: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 LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadpex5 Loadrecord Loadspeedo Loadtype1 Loadvbe Loadxie EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc101 Option XkbLayout us Option XkbOptionsctrl:nocaps,alt:altismeta EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section Device Identifier ATI 128 ? Driver ati EndSection Section Monitor Identifier iiyama HorizSync 30-130 VertRefresh 50-160 Option DPMS EndSection Section Screen Identifier Default Screen Device ATI 128 ? Monitor iiyama
Re: BUG?: SIGSEGV in get_rotate_fontname() in omGeneric.c
No comment?
I have tried to do some debugging and anlysis - am I on the right track?
Thanks :)
David
David Greaves wrote:
Hi
I have a problem with get_rotate_fontname() in omGeneric.c.
I think there's a bug there.
I'm using libx11-6[-dbg] 4.3.0.dfsg.1-6
Line 561:
for(field_num = 0 ; field_num CHARSET_ENCODING_FIELD ptr *ptr ;
ptr++, field_num++) {
I've stepped here with gdb and have:
#define CHARSET_ENCODING_FIELD 14
font_name=-ttf-arial-medium-i-normal-italic-16-0-ISO8859-1
field_num=9
ptr=0x0
The for condition looks to me like it shouldn't evaluate *ptr but I
think it does as I get a SIGSEGV if I step this line.
Is it possibly a gcc thing? Or is my src out of step with my library
(ie is the ' ptr' check new - in which case the bug is fixed - in
which case where can I get a good library? :) )
I looked at a disassembly but couldn't tell.
Obviously it does this in the standard library (where I first hit the
problem) and in the -dbg library too (I couldn't make XLOCALEDIR work
so I symlinked them in temporarily as you may notice in the backtrace)
note that I haven't actually built a local libX11 - I just dl'ed the
source to step through. (It's worth checking I have the right source,
I've copied the snippet at the end)
Backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x40be0829 in get_rotate_fontname (font_name=0x87dc5c8
-ttf-arial-medium-i-normal-italic-16-0-ISO8859-1) at omGeneric.c:561
/amd/willow/root/share/mirror/devel/X/xfree86-4.3.0/build-tree/xc/lib/X11/omGeneric.c:561:14833:beg:0x40be0829
(gdb) bt
#0 0x40be0829 in get_rotate_fontname (font_name=0x87dc5c8
-ttf-arial-medium-i-normal-italic-16-0-ISO8859-1) at omGeneric.c:561
#1 0x40be0f73 in parse_fontdata (oc=0x8805410, font_set=0x87fdbf0,
font_data=0x87dc5a8, font_data_count=0, name_list=0x85fc9b8,
name_list_count=2, class=C_VROTATE, font_data_return=0x0) at
omGeneric.c:1047
#2 0x40be11ea in parse_vw (oc=0x8805410, font_set=0x87fdbf0,
name_list=0x85fc9b8, count=2) at omGeneric.c:1088
#3 0x40be152f in parse_fontname (oc=0x8805410) at omGeneric.c:1226
#4 0x40be1868 in create_fontset (oc=0x8805410) at omGeneric.c:1361
#5 0x40be1e09 in create_oc (om=0x40be6960, args=0x0, num_args=0) at
omGeneric.c:1672
#6 0x4092a461 in XCreateOC (om=0x8805208) at OCWrap.c:50
#7 0x409297f5 in XCreateFontSet (dpy=0x0, base_font_name_list=0x0,
missing_charset_list=0xbfffec20, missing_charset_count=0xbfffec24,
def_string=0x0) at FSWrap.c:192
#8 0x4027b849 in getFontSet ([EMAIL PROTECTED]) at
kernel/qinputcontext_x11.cpp:93
#9 0x4027cc4d in QInputContext::setXFontSet (this=0x877d770,
[EMAIL PROTECTED]) at kernel/qinputcontext_x11.cpp:522
#10 0x4029b033 in QWidget::setMicroFocusHint (this=0x87dbcc8, x=14,
y=4, width=0, height=21, text=true, f=0xbfffed40) at
kernel/qwidget_x11.cpp:972
#11 0x404aab35 in QTextEdit::updateMicroFocusHint (this=0x87dbcc8) at
widgets/qtextedit.cpp:2819
#12 0x404ab8db in QTextEdit::insert (this=0x87dbcc8, [EMAIL PROTECTED],
insertionFlags=5) at widgets/qtextedit.cpp:3033
#13 0x404ab2be in QTextEdit::insert (this=0x87dbcc8, [EMAIL PROTECTED],
indent=true, checkNewLine=false, removeSelected=true) at
widgets/qtextedit.cpp:2941
#14 0x404a5124 in QTextEdit::keyPressEvent (this=0x87dbcc8,
e=0xb2c0) at widgets/qtextedit.cpp:1460
#15 0x40b9338e in Editor::keyPressEvent (this=0x87dbcc8, e=0xb2c0)
at editor.cpp:211
#16 0x4036dfb9 in QWidget::event (this=0x87dbcc8, e=0xb2c0) at
kernel/qwidget.cpp:4719
#17 0x404a3fba in QTextEdit::event (this=0x87dbcc8, e=0xb2c0) at
widgets/qtextedit.cpp:1208
#18 0x402d2485 in QApplication::internalNotify (this=0xb890,
receiver=0x87dbcc8, e=0xb2c0) at kernel/qapplication.cpp:2635
#19 0x402d1b15 in QApplication::notify (this=0xb890,
receiver=0x87dbcc8, e=0xb2c0) at kernel/qapplication.cpp:2392
#20 0x40266472 in QApplication::sendSpontaneousEvent
(receiver=0x87dbcc8, event=0xb2c0) at qapplication.h:494
#21 0x40261228 in QETWidget::translateKeyEvent (this=0x87dbcc8,
event=0xb6b0, grab=false) at kernel/qapplication_x11.cpp:5488
#22 0x4025d173 in QApplication::x11ProcessEvent (this=0xb890,
event=0xb6b0) at kernel/qapplication_x11.cpp:3479
#23 0x40277997 in QEventLoop::processEvents (this=0x8322ae8, flags=4)
at kernel/qeventloop_x11.cpp:192
#24 0x402e6a65 in QEventLoop::enterLoop (this=0x8322ae8) at
kernel/qeventloop.cpp:198
#25 0x402e697e in QEventLoop::exec (this=0x8322ae8) at
kernel/qeventloop.cpp:145
#26 0x402d25f1 in QApplication::exec (this=0xb890) at
kernel/qapplication.cpp:2758
#27 0x08097d62 in main (argc=1, argv=0xb974) at main.cpp:220
#
// src extract to make sure I'm not out of step:
static char *
get_rotate_fontname(font_name)
char *font_name;
{
char *pattern = NULL, *ptr = NULL;
char *fields[CHARSET_ENCODING_FIELD];
char str_pixel[32], str_point[4];
char *rotate_font_ptr = NULL;
int pixel_size = 0;
Bug#259740: Windows key no longer treated as modifer, just as Super_L
I'm still seeing this bug with XFree86 4.3.0.dfsg.1-6ubuntu11 (synced to SVN trunk @ r1777). Fabio M. Di Nitto told me to follow up as this should have been fixed. I have a normal British Windows keyboard with the Windows/Menu keys, configured like this: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout gb EndSection xmodmap says this: $ xmodmap xmodmap: up to 3 keys per modifier, (keycodes in parentheses): 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) Not totally understanding the X keyboard model, I'll try and explain what happens. My Metacity is configured to switch workspaces on super-arrows. When I let go of the super/Windows key I'd expect the workspace switching popup to go, but it persists until I press it again, as if it wasn't a modifier key. The magic xmodmap line: xmodmap -e 'clear mod4' -e 'add mod4 = Super_L' fixes this temporarily. My GNOME keyboard settings applet says that super is mapped to the Windows key is the default setting. Pressing and releasing the left Windows key in xev produces these: KeyPress event, serial 26, synthetic NO, window 0x301, root 0x8e, subw 0x0, time 1593258, (104,3), root:(108,539), state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 bytes: KeyRelease event, serial 26, synthetic NO, window 0x301, root 0x8e, subw 0x0, time 1593375, (104,3), root:(108,539), state 0x40, keycode 115 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 bytes: When I go to the GNOME keybindings applet to configure a super-key combination, when I press the super key it doesn't wait for a key along with the modifier, but stops at Super_L. If I use Meta it waits for me to hit another key and will display something like Alt5. Anything else I can do to help debug this? Ross -- Ross Burton mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF
Re: Bug#240351: xserver-xfree86: Alt-Gr does not work anymore
The most interesting information from your log file /var/log/XFree86.0.log is Couldn't load XKB keymap, falling back to pre-XKB keymap I had the same problem and could solve it by installing the xlibs package. Though the description of xlibs says that you don't need that package for Debian 3.1 (sarge), it contains configuration data used by the X Keyboard Extension. I think this configuration data should be included in the standard installation for X, because every user with a non-english keyboard layout needs it.
new lspci support -X for XF86Config style output
Hello X Strike Force, Pursuing to a previous thread, I reported a wishlist item against pciutils asking for an option for lspci for XF86Config style output: Remco van de Meent has implemented it in 1:2.1.11-13. Now lspci -X output: PCI:0:20:0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M The idea was that dexconf could use it. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here.
X Strike Force XFree86 SVN commit: r1778 - branches/debconf-overhaul/debian
Author: branden Date: 2004-08-31 14:02:35 -0500 (Tue, 31 Aug 2004) New Revision: 1778 Modified: branches/debconf-overhaul/debian/changelog Log: Add bug-closer. Modified: branches/debconf-overhaul/debian/changelog === --- branches/debconf-overhaul/debian/changelog 2004-08-31 07:00:06 UTC (rev 1777) +++ branches/debconf-overhaul/debian/changelog 2004-08-31 19:02:35 UTC (rev 1778) @@ -381,6 +381,7 @@ behavior in the xserver-xfree86/config/monitor/mode-list template description. (This default is later overridden if and only if the selected display driver doesn't support that resolution.) + (Closes: #221570) + Make the medium monitor configuration interface the default, since LCD flat panel displays are so much more common relative to four years ago. Also ask this question at medium debconf priority. Thanks to Joey Hess
Processed: Re: #253607: xserver-xfree86: (debconf) X 4.3.0 is perfectly capable of detecting monitor resolutions, debconf should ask only if needed
Processing commands for [EMAIL PROTECTED]: retitle 253607 xserver-xfree86: [debconf] don't set monitor sync ranges in config file at all; just rely on DDC/EDID to work Bug#253607: xserver-xfree86: (debconf) X 4.3.0 is perfectly capable of detecting monitor resolutions, debconf should ask only if needed Changed Bug title. severity 253607 wishlist Bug#253607: xserver-xfree86: [debconf] don't set monitor sync ranges in config file at all; just rely on DDC/EDID to work Severity set to `wishlist'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#130191: marked as done (xserver-xfree86: [debconf] BusID question could have better default and explanation)
Your message dated Tue, 31 Aug 2004 14:38:54 -0500 with message-id [EMAIL PROTECTED] and subject line Processed: Re: Bug#130191: xserver-xfree86: debconf BusID question could have better default and explanation has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at maintonly) by bugs.debian.org; 21 Jan 2002 00:42:48 + From [EMAIL PROTECTED] Sun Jan 20 18:42:48 2002 Return-path: [EMAIL PROTECTED] Received: from cepheus.azstarnet.com [169.197.56.195] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 16SSXw-0002KI-00; Sun, 20 Jan 2002 18:42:48 -0600 Received: from Obsession.azstarnet.com ([EMAIL PROTECTED] [169.197.10.30]) by cepheus.azstarnet.com (8.9.3/8.9.3) with SMTP id RAA25813; Sun, 20 Jan 2002 17:42:45 -0700 (MST) Message-Id: [EMAIL PROTECTED] X-Sent-via: StarNet http://www.azstarnet.com/ Received: by Obsession.azstarnet.com (sSMTP sendmail emulation); Sun, 20 Jan 2002 17:43:22 -0700 From: Chris Tillman [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: xserver-xfree86: [debconf] please try harder to display default (none displayed) X-Reportbug-Version: 1.41.1421 X-Mailer: reportbug 1.41.1421 Date: Sun, 20 Jan 2002 17:43:22 -0700 Reply-To: Chris Tillman [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Package: xserver-xfree86 Version: 4.1.0-9 Severity: wishlist I think the new dialog explaining how to enter a Bus ID is very good. The only thing I think won't work is expecting users to be able to convert hex to decimal. So if a default isn't being displayed, that's a real issue. Or, put another entry box for people to enter the ID in lspci (hex) format, and then you can validate that and convert it to decimal for the Config. Also, please change the reference to lspci in the dialog to /sbin/lspci so people that run it as non-root will succeed. Here is a small perl script that works on my system to get the display bus id in decimal from lspci: #!/usr/bin/perl `/sbin/lspci | grep Display | sed 's/ Display.*//'`; # lspci gives something like 00:10.0 ($bus,$slot,$func) = /^(\d*)\:(\d*)\.(\d*).*/ ; $bus=hex $bus; $slot=hex $slot; $func=hex $func; printf PCI:%02d:%02d:%02d\n, $bus, $slot, $func; Even if this fails to find a Display device, it gives PCI:00:00:00, which at least tells the user what pattern needs to appear. It doesn't find multiple display cards, only the first one. -- System Information Debian Release: 3.0 Architecture: powerpc Kernel: Linux Obsession 2.2.19 #1 Sat Apr 14 23:20:24 CDT 2001 ppc Locale: LANG=C, LC_CTYPE=C Versions of packages xserver-xfree86 depends on: ii debconf 1.0.22 Debian configuration management sy ii libc6 2.2.4-7GNU C Library: Shared libraries an ii xserver-common4.1.0-9files and utilities common to all ii zlib1g1:1.1.3-18 compression library - runtime --- Received: (at 130191-done) by bugs.debian.org; 31 Aug 2004 19:38:55 + From [EMAIL PROTECTED] Tue Aug 31 12:38:55 2004 Return-path: [EMAIL PROTECTED] Received: from dhcp065-026-182-085.indy.rr.com (sisyphus.deadbeast.net) [65.26.182.85] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C2ET1-0004Qs-00; Tue, 31 Aug 2004 12:38:55 -0700 Received: by sisyphus.deadbeast.net (Postfix, from userid 1000) id 518BC68C002; Tue, 31 Aug 2004 14:38:54 -0500 (EST) Date: Tue, 31 Aug 2004 14:38:54 -0500 From: Branden Robinson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Processed: Re: Bug#130191: xserver-xfree86: debconf BusID question could have better default and explanation Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=CblX+4bnyfN0pR09 Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. User-Agent: Mutt/1.5.6+20040818i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: --CblX+4bnyfN0pR09 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline
Bug#253607: #253607: xserver-xfree86: (debconf) X 4.3.0 is perfectly capable of detecting monitor resolutions, debconf should ask only if needed
retitle 253607 xserver-xfree86: [debconf] don't set monitor sync ranges in config file at all; just rely on DDC/EDID to work severity 253607 wishlist thanks Like said, since XFree 4.3.0, Xfree, at least on the graphic drivers that support it, is capable to run without monitor timings, and able to ask the monitor this over the ddc protocol. ...except you don't always get an answer back. Ideally, the configuration stuff should somehow interogate the graphic card/monitor, and see if it is able to use the ddc protocol to get the datas, tell the user that this values were detected, and ask if he want to use the default values, autodetect each time, or provide some values himself, the default being autodetecting stuff. Yes, somehow. You don't provide any code, or anything beyond the barest sketch of a design really, so this is going to have to wait until after sarge. By letting these entries absent of the config file, at worst X will revert to some VGA standard mode, so there is no danger, but you may get reports about why are the icons so big from people without monitor attached, or using broken monitor switches or such. VGA standard mode is far too crude for most purposes today. Modern desktops expect to have a ton of real estate, which is why I have added 1152x768 and 1024x768 to the fallback default mode list in the current debconf overhaul work being done in XSF SVN. I guess read-edid can be used for just this, but then maybe it is x86 only, is that possible ? Actually, Colin Watson has done some work to make read-edid operate on PowerPC as well[1]. I hope to get that patch applied in time for sarge; I have authorized an NMU for someone else to do so if people don't think I will get to it in time. On a more general note, now that the licensing of the X-Oz autoconfig stuff has been clarified (it did exist under traditional MIT/X11 terms when it was first checked into XFree86 CVS), it may be that in sarge + 1 when we migrate to X.Org we will use X -autoconfig instead of (or as an alternative to) the combination of discover, mdetect, and read-edid. My only concern about that approach is we'd better be damn sure starting X doesn't lock up people's machines, especially on our more exotic architectures. discover and mdetect don't, and read-edid only seems to hurt x86 users with buggy hardware. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=262102 -- G. Branden Robinson|If you wish to strive for peace of Debian GNU/Linux |soul, then believe; if you wish to [EMAIL PROTECTED] |be a devotee of truth, then http://people.debian.org/~branden/ |inquire. -- Friedrich Nietzsche signature.asc Description: Digital signature
Bug#259740: Windows key no longer treated as modifer, just as Super_L
On Tue, Aug 31, 2004 at 02:39:45PM +0100, Ross Burton wrote: [...] When I go to the GNOME keybindings applet to configure a super-key combination, when I press the super key it doesn't wait for a key along with the modifier, but stops at Super_L. If I use Meta it waits for me to hit another key and will display something like Alt5. Anything else I can do to help debug this? Ivan Pascal explains in http://bugzilla.xfree86.org/show_bug.cgi?id=580 why he had to make changes to modifier keys, and that applications have to be updated if they are broken by these changes because he cannot fix XKB without breaking other stuff. The problem with -6 is that a patch had not been applied, so these changes were incomplete and Meta keys were broken in Debian packages. So IMO this bug should be cloned and reassigned to metacity, but I let Debian maintainers decide what to do. Your output contains mod4Super_L (0x7f), Hyper_L (0x80) Those 0x7f and 0x80 keycodes are the fake keys introduced by Ivan Pascal. As explained in the URL above, no events are associated with fake keys, so WM may have trouble when trying to intercept such events. Maybe altwin:super_win XKB option could help in this case, since real keys are then also mapped to mod4. Denis
X Strike Force XFree86 SVN commit: r1779 - branches/debconf-overhaul/debian
Author: branden Date: 2004-08-31 16:39:08 -0500 (Tue, 31 Aug 2004) New Revision: 1779 Modified: branches/debconf-overhaul/debian/TODO Log: Add sub-items. Modified: branches/debconf-overhaul/debian/TODO === --- branches/debconf-overhaul/debian/TODO 2004-08-31 19:02:35 UTC (rev 1778) +++ branches/debconf-overhaul/debian/TODO 2004-08-31 21:39:08 UTC (rev 1779) @@ -35,6 +35,10 @@ port. See URL: http://lists.debian.org/debian-68k/2004/08/msg00392.html. + Where applicable, use present perfect tense in trace messages so they are not confused with being in the imperative voice. + + Migrate users of 4.3.0.dfsg.1-6 and previous to automatically add v4l +to module list. + + Accept comma-delimited list of values and/or ranges when validating monitor +frequencies. * Add FAQ entry describing Debian's plans in the X department. 4.3.0.dfsg.1-8
Bug#258399: xlibs: dvorak keyboard layout is missing right alt key
On Mon, Aug 30, 2004 at 12:08:07PM -0400, Adam C Powell IV wrote: [...] Interestingly, I had thought that the absence of Alt_R in mod2 was the problem with the Dvorak/switched layout. But it's also missing in the default US/no switch layout, in which right Alt works just fine... FYI, in the case of Dvorak/no switch, right Alt does nothing; with US/switch, right Alt works fine. So Dvorak seems to be the problem. Great, thank you for your detailed report. Your analysis is right, swapcaps and mod2 are not causing this bug. Since xmodmap output is similar in both cases, one could believe that their modifiers are the same, but this is wrong. The difference is more subtle, it becomes visible when running $ xmodmap -pke | grep 113 (because 113 is the keycode of right Alt key in your case) with both layouts (do not swap caps/ctrl to make less changes) and compare their output: keycode 113 = Alt_R Meta_R keycode 113 = ISO_Level3_Shift Multi_key With pc/us, right Alt key is bound to Alt_R Meta_R. Unfortunately xmodmap does not tell why Alt_R is bound to mod1, this is because XKB is much more powerful and xmodmap is unable to display all details. The reason can be found by running $ xkbcomp :0 and searching for Alt_R in the generated server-0.xkb file. OTOH right Alt key is bound to ISO_Level3_Shift (and thus mod5) with dvorak layout, so pressing this key grabs the 3rd column found in /etc/X11/xkb/symbols/pc/dvorak (ie. dead keys). This event is intercepted by XKB and not sent to your window manager. So in fact, your right Alt key works as expected, but not as you want. This bug should either be fixed by providing a pure ASCII dvorak variant, or you have to bind your right Alt key to mod1. I believe that selecting altwin:meta_alt option does the trick. In such a case, can this bugreport be closed, or do you really need another variant? Denis
X Strike Force XFree86 SVN commit: r1780 - branches/debconf-overhaul/debian
Author: branden Date: 2004-08-31 17:26:23 -0500 (Tue, 31 Aug 2004) New Revision: 1780 Modified: branches/debconf-overhaul/debian/CHANGESETS branches/debconf-overhaul/debian/changelog branches/debconf-overhaul/debian/xserver-xfree86.config.in branches/debconf-overhaul/debian/xserver-xfree86.templates Log: + Add several video modes supported by XFree86 4.3.0 to the available options in xserver-xfree86/config/monitor/mode-list: - 832x624 @ 75Hz - 1152x864 @ 75Hz (Closes: #130274) - 1400x1050 @ 60Hz - 1400x1050 @ 75Hz (Closes: #144040) - 1600x1024 @ 60Hz - 1920x1440 @ 85Hz - 2048x1536 @ 60Hz - 2048x1536 @ 75Hz - 2048x1536 @ 85Hz Make the new template default for this question 1152x864 @ 75Hz. Modified: branches/debconf-overhaul/debian/CHANGESETS === --- branches/debconf-overhaul/debian/CHANGESETS 2004-08-31 21:39:08 UTC (rev 1779) +++ branches/debconf-overhaul/debian/CHANGESETS 2004-08-31 22:26:23 UTC (rev 1780) @@ -549,6 +549,18 @@ flat panel displays are so much more common relative to four years ago. Also ask this question at medium debconf priority. Thanks to Joey Hess for the suggestions. (Closes: #226365, #242216) ++ Add several video modes supported by XFree86 4.3.0 to the available + options in xserver-xfree86/config/monitor/mode-list: + - 832x624 @ 75Hz + - 1152x864 @ 75Hz (Closes: #130274) + - 1400x1050 @ 60Hz + - 1400x1050 @ 75Hz (Closes: #144040) + - 1600x1024 @ 60Hz + - 1920x1440 @ 85Hz + - 2048x1536 @ 60Hz + - 2048x1536 @ 75Hz + - 2048x1536 @ 85Hz + Make the new template default for this question 1152x864 @ 75Hz. + Add 1152x864 and 1024x768 to the final fallback list of default modes, if we don't already know what the user wants. + Remove kludge that omitted the dri XFree86 server module from the Modified: branches/debconf-overhaul/debian/changelog === --- branches/debconf-overhaul/debian/changelog 2004-08-31 21:39:08 UTC (rev 1779) +++ branches/debconf-overhaul/debian/changelog 2004-08-31 22:26:23 UTC (rev 1780) @@ -386,6 +386,18 @@ flat panel displays are so much more common relative to four years ago. Also ask this question at medium debconf priority. Thanks to Joey Hess for the suggestions. (Closes: #226365, #242216) ++ Add several video modes supported by XFree86 4.3.0 to the available + options in xserver-xfree86/config/monitor/mode-list: + - 832x624 @ 75Hz + - 1152x864 @ 75Hz (Closes: #130274) + - 1400x1050 @ 60Hz + - 1400x1050 @ 75Hz (Closes: #144040) + - 1600x1024 @ 60Hz + - 1920x1440 @ 85Hz + - 2048x1536 @ 60Hz + - 2048x1536 @ 75Hz + - 2048x1536 @ 85Hz + Make the new template default for this question 1152x864 @ 75Hz. + Add 1152x864 and 1024x768 to the final fallback list of default modes, if we don't already know what the user wants. + Remove kludge that omitted the dri XFree86 server module from the @@ -515,7 +527,7 @@ missing to enable this feature. No keymaps currently use this feature, but users may find it useful with broken keymaps. - -- Branden Robinson [EMAIL PROTECTED] Tue, 31 Aug 2004 01:25:05 -0500 + -- Branden Robinson [EMAIL PROTECTED] Tue, 31 Aug 2004 17:21:40 -0500 xfree86 (4.3.0.dfsg.1-6) unstable; urgency=low Modified: branches/debconf-overhaul/debian/xserver-xfree86.config.in === --- branches/debconf-overhaul/debian/xserver-xfree86.config.in 2004-08-31 21:39:08 UTC (rev 1779) +++ branches/debconf-overhaul/debian/xserver-xfree86.config.in 2004-08-31 22:26:23 UTC (rev 1780) @@ -1176,6 +1176,15 @@ xserver-xfree86/config/monitor/mode-list db_go db_get xserver-xfree86/config/monitor/mode-list + # The mode and range information below is adapted from the built-in + # modeline definitions in the XFree86 source tree; specifically + # xc/programs/Xserver/hw/xfree86/etc/vesamodes and + # xc/programs/Xserver/hw/xfree86/etc/extramodes. The rule of thumb is to + # set the sync ranges based on the hsync and vrefresh values used by the + # selected mode, plus a little bit of headroom to allow other modes to + # be used (as long as they don't push the hardware much harder than the + # selected one) and a margin of error (e.g., if the video driver or video + # card overdrives the monitor just a little bit). case $RET in 640x480 @ 60Hz) db_set xserver-xfree86/config/monitor/horiz-sync 28-33 @@ -1202,6 +1211,12 @@ db_set xserver-xfree86/config/monitor/vert-refresh 50-85 DEFAULT_MODES=800x600 ;; +832x624 @ 75Hz) + # This is a Macintosh (m68k and OldWorld PowerPC) mode. + db_set xserver-xfree86/config/monitor/horiz-sync 30-50 + db_set
Bug#234082: marked as done (Subject: xbase-clients: [xkb] can't switch vt's when -compat group_led is set)
Your message dated Wed, 1 Sep 2004 00:48:38 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#234082: xbase-clients: [xkb] can't switch vt's when -compat group_led is set has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 21 Feb 2004 18:48:52 + From [EMAIL PROTECTED] Sat Feb 21 10:48:52 2004 Return-path: [EMAIL PROTECTED] Received: from midway.uchicago.edu [128.135.12.12] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1AucBI-0001s9-00; Sat, 21 Feb 2004 10:48:52 -0800 Received: from gr-visitor.uchicago.edu (nsit-s245-217.uchicago.edu [128.135.245.217]) by midway.uchicago.edu (8.12.10/8.12.9) with ESMTP id i1LImmYF014433; Sat, 21 Feb 2004 12:48:49 -0600 (CST) From: Itai Seggev [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Subject: xbase-clients: [xkb] can't switch vt's when -compat group_led is set Date: Sat, 21 Feb 2004 12:47:18 -0600 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_18 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_02_18 X-Spam-Level: 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 -
Bug#116507: Nwenfqohtc reply asap improves vision
Believe it or not, I have tried several sites to b-uy presription medication. I should say that currently you are still be the best amony them. Gary M. --PA Cqd http://vrnu.o.gait1492pinn.com/f74m/ d^r'ugs from u,s.a 0v^ernight d-e-liver `Have you found Heathcliff, you ass?' interru`pted Catherine. `Have you be'en looking for him, as I ordered?' `Aw sud mo~re likker look for th' horse,' he replied. `It 'ud be tuh more sense. Bud, Aw can look for norther horse nur man uf a neeght loike this--as black as t' chimbley! und Hathecliff's noan t' chap to coom at maw whistle--happen he'll be less hard uh hearing wi' ye!' -Original Message- From: Kenisha Harrison [mailto:[EMAIL PROTECTED] To: abraham baugher; devin leithoff Sent: Sunday, September, 2004 6:13 AM Subject: reply asap improves vision 'Mr. Brocklehurst, I believe I intimated in the letter which I wrote to you three weeks ago, that this little girl has not quite the character and disposition I could wish: should you admit her into Lowood school, I should be glad if the su,perintendent and teachers were requested to keep a strict eye on her, and, above all, to guard against her worst fault, a tendency to deceit. I mention this in your hearing, Jane, that you may not attempt to impose on Mr. Brocklehurst.' The massive towers, the donjon keep, srodowiskamatb 10 smrodu 91 wyodrebnialrolluleganie
Bug#234530: marked as done (setxkbmap -layout us,lt assigns Alt_R to modifiers Mod1 and Mod5)
Your message dated Wed, 1 Sep 2004 00:53:26 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#234530: setxkbmap -layout us,lt assigns Alt_R to
modifiers Mod1 and Mod5
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
Received: (at submit) by bugs.debian.org; 24 Feb 2004 13:14:33 +
From [EMAIL PROTECTED] Tue Feb 24 05:14:33 2004
Return-path: [EMAIL PROTECTED]
Received: from master.debian.org [146.82.138.7]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AvcOP-0006Su-00; Tue, 24 Feb 2004 05:14:33 -0800
Received: from lan-70-53.skynet.lt (mpiktas.skynet.vl) [212.122.70.53]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AvcOM-000649-00; Tue, 24 Feb 2004 07:14:31 -0600
Received: from debian (localhost [127.0.0.1])
by mpiktas.skynet.vl (Postfix) with ESMTP id 49EE7518DC
for [EMAIL PROTECTED]; Tue, 24 Feb 2004 15:14:30 +0200 (EET)
Date: Tue, 24 Feb 2004 15:14:29 +0200
From: Mpiktas [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: setxkbmap -layout us,lt assigns Alt_R to modifiers Mod1 and Mod5
Message-ID: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1;
protocol=application/pgp-signature; boundary=fWddYNRDgTk9wQGZ
Content-Disposition: inline
X-Mailer: Balsa 2.0.16
Lines: 127
Delivered-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_22
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.9 required=4.0 tests=FROM_ENDS_IN_NUMS,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_02_22
X-Spam-Level:
--fWddYNRDgTk9wQGZ
Content-Type: text/plain; Format=Flowed; DelSp=Yes; charset=ISO-8859-13
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Package: xbase-clients
Version: 4.3.0-2
If you put in XF86Config4
XkbOption XkbLayout us,lt
or change the keyboard layout directly with
setxkbmap -layout us,lt -option grp:ctrl_shift_toggle
xmodmap -pm prints
shift Shift_L (0x32), Shift_R (0x3e)
lockCaps_Lock (0x42)
control Control_L (0x25), Control_R (0x6d)
mod1Alt_L (0x40), Alt_R (0x71)
mod2Num_Lock (0x4d)
mod3
mod4Super_L (0x73), Super_R (0x74)
mod5Alt_R (0x71)
Thus Alt_R is modifier mod1 and mod5. Such situation renders xemacs21 prett=
y =20
unusuable. When pressing Alt it the issues warning
(1) (key-mapping/warning) XEmacs: Alt_R (0x71) generates both Mod1 and Mod=
5, =20
which is nonsensical.
so you practically can't use any meta key shortcuts in xemacs21 and that me=
ans =20
that you can't practicaly use xemacs.
With such configuration setxkbmap -print produces
xkb_keymap {
xkb_keycodes { include xfree86+aliases(qwerty) };
xkb_types { include complete };
xkb_compat{ include complete };
xkb_symbols { include pc/pc(pc105)+pc/us+pc/lt:2+group=20
(ctrl_shift_toggle) };
xkb_geometry { include pc(pc105) };
};
Looking at the file /etc/X11/xkb/symbols/pc you can find lines
default
xkb_symbols pc104 {
include pc/pc(basic)
key LALT {[ Alt_L, Meta_L ] };
key RALT {[ Alt_R, Meta_R ] };
key LWIN {[ Super_L ] };
key RWIN {[ Super_R ] };
key MENU {[ Menu] };
// modifier mappings
modifier_map Mod1 { Alt_L, Alt_R, Meta_L, Meta_R };
modifier_map Mod4 { Super_L, Super_R };
};
xkb_symbols pc105 {
include pc/pc(pc104)
key LSGT { type[Group1] =3D FOUR_LEVEL,
[ less,greater, bar,brokenbar ] };
};
In the file /etc/X11/xkb/symbols/lt there are lines
...skipped
partial default alphanumeric_keys modifier_keys
xkb_symbols basic {
...skipped
key RALT { type[Group1]=3DTWO_LEVEL,
[ ISO_Level3_Shift, Multi_key ] };
modifier_map Mod5 { RALT };
};
...skipped
Thus key RALT or Alt_R in lt layout is assigned to modifier Mod5 and thus t=
he =20
confusion is created.
I am pointing out the problem with lt layout, yet this problem may occur us=
ing =20
other layouts.
Solutions to the problem:
1. Use setxkbmap -layout lt,us (us and lt interchanged places, this fixes=
=20
the problem)
2. Comment lines
key RALT { type[Group1]=3DTWO_LEVEL,
[ ISO_Level3_Shift,
X Strike Force XFree86 SVN commit: r1781 - branches/debconf-overhaul/debian
Author: branden
Date: 2004-08-31 18:45:40 -0500 (Tue, 31 Aug 2004)
New Revision: 1781
Modified:
branches/debconf-overhaul/debian/CHANGESETS
branches/debconf-overhaul/debian/TODO
branches/debconf-overhaul/debian/changelog
branches/debconf-overhaul/debian/xserver-xfree86.config.in
Log:
Accept comma-delimited list of values and/or ranges when validating monitor
frequencies (fixes regression on trunk).
Accept (optional) units (Hz, kHz, MHz) per the XF86Config-4(5x) manual page
when validating monitor frequencies, which we never did before.
Modified: branches/debconf-overhaul/debian/CHANGESETS
===
--- branches/debconf-overhaul/debian/CHANGESETS 2004-08-31 22:26:23 UTC (rev
1780)
+++ branches/debconf-overhaul/debian/CHANGESETS 2004-08-31 23:45:40 UTC (rev
1781)
@@ -491,8 +491,9 @@
Make xserver-xfree86 config script's validate_monitor_frequency_db_input()
function more strict, so it doesn't regard open-ended ranges like 40- as
-valid.
-1766, 1769, 1772
+valid. Also accept (optional) units (Hz, kHz, MHz) per the
+XF86Config-4(5x) manual page, which we never did before.
+1766, 1769, 1772, [XXX: ADD REVISION NUMBER WHEN MERGED TO TRUNK]
Grab from XFree86 CVS (2003-12-18) several fixes for keyboard issues:
+ Fix for XKB map 'altwin' to avoid one keysym to more than one modifier
@@ -580,6 +581,6 @@
modules to load. Add description of this module to
xserver-xfree86/config/modules template description. Refer to XVideo
extension as such instead of Xv. (Closes: #135768)
- [XXX: REPLACE WITH REVISION NUMBER WHEN MERGED TO TRUNK]
+[XXX: REPLACE WITH REVISION NUMBER WHEN MERGED TO TRUNK]
vim:set ai et sts=4 sw=4 tw=80:
Modified: branches/debconf-overhaul/debian/TODO
===
--- branches/debconf-overhaul/debian/TODO 2004-08-31 22:26:23 UTC (rev
1780)
+++ branches/debconf-overhaul/debian/TODO 2004-08-31 23:45:40 UTC (rev
1781)
@@ -37,8 +37,6 @@
not confused with being in the imperative voice.
+ Migrate users of 4.3.0.dfsg.1-6 and previous to automatically add v4l
to module list.
- + Accept comma-delimited list of values and/or ranges when validating monitor
-frequencies.
* Add FAQ entry describing Debian's plans in the X department.
4.3.0.dfsg.1-8
Modified: branches/debconf-overhaul/debian/changelog
===
--- branches/debconf-overhaul/debian/changelog 2004-08-31 22:26:23 UTC (rev
1780)
+++ branches/debconf-overhaul/debian/changelog 2004-08-31 23:45:40 UTC (rev
1781)
@@ -493,7 +493,8 @@
* Make xserver-xfree86 config script's validate_monitor_frequency_db_input()
function more strict, so it doesn't regard open-ended ranges like 40- as
-valid.
+valid. Also accept (optional) units (Hz, kHz, MHz) per the
+XF86Config-4(5x) manual page, which we never did before.
Changes by Robert Millan:
@@ -527,7 +528,7 @@
missing to enable this feature. No keymaps currently use this feature,
but users may find it useful with broken keymaps.
- -- Branden Robinson [EMAIL PROTECTED] Tue, 31 Aug 2004 17:21:40 -0500
+ -- Branden Robinson [EMAIL PROTECTED] Tue, 31 Aug 2004 18:40:15 -0500
xfree86 (4.3.0.dfsg.1-6) unstable; urgency=low
Modified: branches/debconf-overhaul/debian/xserver-xfree86.config.in
===
--- branches/debconf-overhaul/debian/xserver-xfree86.config.in 2004-08-31
22:26:23 UTC (rev 1780)
+++ branches/debconf-overhaul/debian/xserver-xfree86.config.in 2004-08-31
23:45:40 UTC (rev 1781)
@@ -252,10 +252,44 @@
set -e
}
+validate_monitor_frequency_expr () {
+ # Syntax: validate_monitor_frequency_expr expression
+ #
+ # Confirm that the given expression is a valid monitor frequency expression
+ # per XF86Config-4(5x). Note that this does *not* handle (comma-delimited)
+ # tuples. We expect a single value or range with an optional unit suffix.
+ #
+ # Note: We don't check to see if the latter value in a range is actually
+ # greater than the former, and we don't check to see if any of the numeric
+ # values actually make sense. I.e., 0 Hz may not actually be valid as far as
+ # the X server is concerned, but 1 Hz might be okay whereas 1 kHz
+ # might not be. It would take quite a bit of code to sort all that out. We
+ # only take some of the bullets out of the user's gun -- not all of them.
+ #
+ # Return true (0) if the expression is valid, and false (1) if it is not.
+
+ local regex
+
regex='^[[:space:]]*0*[0-9]+(\.[0-9]+)?(-0*[0-9]+(\.[0-9]+)?)?([[:space:]]*[kM]?Hz)?$'
+
+ if [ $# -ne 1 ]; then
+internal_error validate_monitor_frequency_expr() called with wrong \
+ number of arguments: $*
+ fi
+
+ if echo $1 | grep -Eiq $regex; then
+return 0
+ else
+return 1
+ fi
+}
+
Bug#258399: xlibs: dvorak keyboard layout is missing right alt key
On Tue, 2004-08-31 at 18:08, Denis Barbier wrote: On Mon, Aug 30, 2004 at 12:08:07PM -0400, Adam C Powell IV wrote: [...] Interestingly, I had thought that the absence of Alt_R in mod2 was the problem with the Dvorak/switched layout. But it's also missing in the default US/no switch layout, in which right Alt works just fine... FYI, in the case of Dvorak/no switch, right Alt does nothing; with US/switch, right Alt works fine. So Dvorak seems to be the problem. Great, thank you for your detailed report. Your analysis is right, swapcaps and mod2 are not causing this bug. Since xmodmap output is similar in both cases, one could believe that their modifiers are the same, but this is wrong. The difference is more subtle, it becomes visible when running $ xmodmap -pke | grep 113 (because 113 is the keycode of right Alt key in your case) with both layouts (do not swap caps/ctrl to make less changes) and compare their output: keycode 113 = Alt_R Meta_R keycode 113 = ISO_Level3_Shift Multi_key With pc/us, right Alt key is bound to Alt_R Meta_R. Unfortunately xmodmap does not tell why Alt_R is bound to mod1, this is because XKB is much more powerful and xmodmap is unable to display all details. The reason can be found by running $ xkbcomp :0 and searching for Alt_R in the generated server-0.xkb file. OTOH right Alt key is bound to ISO_Level3_Shift (and thus mod5) with dvorak layout, so pressing this key grabs the 3rd column found in /etc/X11/xkb/symbols/pc/dvorak (ie. dead keys). This event is intercepted by XKB and not sent to your window manager. So in fact, your right Alt key works as expected, but not as you want. I see, so dvorak has different right alt behavior from pc/us. Thank you for the detailed explanation. This bug should either be fixed by providing a pure ASCII dvorak variant, or you have to bind your right Alt key to mod1. I believe that selecting altwin:meta_alt option does the trick. In such a case, can this bugreport be closed, or do you really need another variant? Hmm... I am satisfied, but the next guy to come along using dvorak might not be, so it's good enough for me, but not necessarily good enough for Debian. Let's leave it open, I don't want to take any more of your time, so I'll try to create another variant myself and send it to this bug as a patch. I should be able to get to it in the next day or two. Thanks, -Adam P. GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Welcome to the best software in the world today cafe! http://lyre.mit.edu/~powell/The_Best_Stuff_In_The_World_Today_Cafe.ogg
X Strike Force XFree86 SVN commit: r1782 - branches/debconf-overhaul/debian
Author: branden
Date: 2004-08-31 19:03:28 -0500 (Tue, 31 Aug 2004)
New Revision: 1782
Modified:
branches/debconf-overhaul/debian/CHANGESETS
branches/debconf-overhaul/debian/TODO
branches/debconf-overhaul/debian/changelog
branches/debconf-overhaul/debian/xserver-xfree86.config.in
Log:
Migrate upgraders from previous package versions by automatically adding
v4l to xserver-xfree86/config/modules list.
Modified: branches/debconf-overhaul/debian/CHANGESETS
===
--- branches/debconf-overhaul/debian/CHANGESETS 2004-08-31 23:45:40 UTC (rev
1781)
+++ branches/debconf-overhaul/debian/CHANGESETS 2004-09-01 00:03:28 UTC (rev
1782)
@@ -580,7 +580,9 @@
+ Include the v4l server module in the list of available (and default)
modules to load. Add description of this module to
xserver-xfree86/config/modules template description. Refer to XVideo
- extension as such instead of Xv. (Closes: #135768)
+ extension as such instead of Xv. Migrate upgraders from previous
+ package versions by automatically adding v4l to module list.
+ (Closes: #135768)
[XXX: REPLACE WITH REVISION NUMBER WHEN MERGED TO TRUNK]
vim:set ai et sts=4 sw=4 tw=80:
Modified: branches/debconf-overhaul/debian/TODO
===
--- branches/debconf-overhaul/debian/TODO 2004-08-31 23:45:40 UTC (rev
1781)
+++ branches/debconf-overhaul/debian/TODO 2004-09-01 00:03:28 UTC (rev
1782)
@@ -35,8 +35,6 @@
port. See URL: http://lists.debian.org/debian-68k/2004/08/msg00392.html.
+ Where applicable, use present perfect tense in trace messages so they are
not confused with being in the imperative voice.
- + Migrate users of 4.3.0.dfsg.1-6 and previous to automatically add v4l
-to module list.
* Add FAQ entry describing Debian's plans in the X department.
4.3.0.dfsg.1-8
Modified: branches/debconf-overhaul/debian/changelog
===
--- branches/debconf-overhaul/debian/changelog 2004-08-31 23:45:40 UTC (rev
1781)
+++ branches/debconf-overhaul/debian/changelog 2004-09-01 00:03:28 UTC (rev
1782)
@@ -416,7 +416,9 @@
+ Include the v4l server module in the list of available (and default)
modules to load. Add description of this module to
xserver-xfree86/config/modules template description. Refer to XVideo
- extension as such instead of Xv. (Closes: #135768)
+ extension as such instead of Xv. Migrate upgraders from previous
+ package versions by automatically adding v4l to module list.
+ (Closes: #135768)
Changes by Fabio M. Di Nitto and Branden Robinson:
@@ -528,7 +530,7 @@
missing to enable this feature. No keymaps currently use this feature,
but users may find it useful with broken keymaps.
- -- Branden Robinson [EMAIL PROTECTED] Tue, 31 Aug 2004 18:40:15 -0500
+ -- Branden Robinson [EMAIL PROTECTED] Tue, 31 Aug 2004 19:02:00 -0500
xfree86 (4.3.0.dfsg.1-6) unstable; urgency=low
Modified: branches/debconf-overhaul/debian/xserver-xfree86.config.in
===
--- branches/debconf-overhaul/debian/xserver-xfree86.config.in 2004-08-31
23:45:40 UTC (rev 1781)
+++ branches/debconf-overhaul/debian/xserver-xfree86.config.in 2004-09-01
00:03:28 UTC (rev 1782)
@@ -1572,6 +1572,24 @@
trace new value of template \xserver-xfree86/config/modules\: \$RET\
fi
+# Add automatic loading of the v4l (Video4Linux) support module if upgrading
+# from a package version that didn't support it.
+if [ -n $2 ] dpkg --compare-versions $2 lt 4.3.0.dfsg.1-7; then
+ db_get xserver-xfree86/config/modules
+ # Only add the module if it's not already there.
+ if ! expr $RET : .*v4l.* /dev/null 21; then
+trace upgrading from package version $2; adding v4l to list of selected \
+ modules
+trace old value of template \xserver-xfree86/config/modules\: \$RET\
+# Add it to the end with a comma and space prepended if there are already
+# some selected modules. Otherwise, make v4l the only selected module.
+SELECTED_MODULES=${RET:+$RET, }v4l
+db_set xserver-xfree86/config/modules $SELECTED_MODULES
+db_get xserver-xfree86/config/modules
+trace new value of template \xserver-xfree86/config/modules\: \$RET\
+ fi
+fi
+
# migrate from ATI driver sub-modules to ATI driver
db_get xserver-xfree86/config/device/driver
case $RET in
Bug#253607: #253607: xserver-xfree86: (debconf) X 4.3.0 is perfectly capable of detecting monitor resolutions, debconf should ask only if needed
On Tue, Aug 31, 2004 at 02:32:49PM -0500, Branden Robinson wrote: retitle 253607 xserver-xfree86: [debconf] don't set monitor sync ranges in config file at all; just rely on DDC/EDID to work severity 253607 wishlist thanks Like said, since XFree 4.3.0, Xfree, at least on the graphic drivers that support it, is capable to run without monitor timings, and able to ask the monitor this over the ddc protocol. ...except you don't always get an answer back. Sure, but the choice of setting a empty monitor timing line should be possible, and it is not currently. Ideally, the configuration stuff should somehow interogate the graphic card/monitor, and see if it is able to use the ddc protocol to get the datas, tell the user that this values were detected, and ask if he want to use the default values, autodetect each time, or provide some values himself, the default being autodetecting stuff. Yes, somehow. You don't provide any code, or anything beyond the barest sketch of a design really, so this is going to have to wait until after sarge. Fine with me. It would be nice if at least for sarge it would be possible to set an empty monitor timing entry. By letting these entries absent of the config file, at worst X will revert to some VGA standard mode, so there is no danger, but you may get reports about why are the icons so big from people without monitor attached, or using broken monitor switches or such. VGA standard mode is far too crude for most purposes today. Modern desktops expect to have a ton of real estate, which is why I have added 1152x768 and 1024x768 to the fallback default mode list in the current debconf overhaul work being done in XSF SVN. Yeah sure, VGA standard mode is too crude, but it is better than not having any output at all, which is what i get when i accept the default choice on my LCD panel. I guess read-edid can be used for just this, but then maybe it is x86 only, is that possible ? Actually, Colin Watson has done some work to make read-edid operate on PowerPC as well[1]. I hope to get that patch applied in time for sarge; I have authorized an NMU for someone else to do so if people don't think I will get to it in time. Cool. On a more general note, now that the licensing of the X-Oz autoconfig stuff has been clarified (it did exist under traditional MIT/X11 terms when it was first checked into XFree86 CVS), it may be that in sarge + 1 when we migrate to X.Org we will use X -autoconfig instead of (or as an alternative to) the combination of discover, mdetect, and read-edid. Yeah, nice. I had some hope with the configuration-file-less solution David was working on, but with the licence mess, i guess that is lost to the free world forever, oh well ... My only concern about that approach is we'd better be damn sure starting X doesn't lock up people's machines, especially on our more exotic architectures. discover and mdetect don't, and read-edid only seems to hurt x86 users with buggy hardware. He. That said, there is one problem with the read-edid thingy, namely when you use a monitor switcher which is not relaying the DDC lines, or you start X while the monitor is off - you are screwed. Thanks for taking care of my bug report. Friendly, Sven Luther
