Bug#489959: No decorations with intel driver
Vedran Furač wrote: Could you post your xorg.conf? It is almost the default (and relies on autodetection). -- Alexander E. Patrakov # 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 Extensions Option Composite EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us,ru Option XkbOptions grp:alt_shift_toggle,grp_led:scroll,compose:rwin EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section Device Identifier Configured Video Device EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection
Bug#495435: xterm: Window resize race condition
Thomas Dickey wrote: On Sun, Aug 17, 2008 at 02:30:15PM +0200, Tobias Diedrich wrote: Package: xterm Version: 235-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When I resize xterm while vim oder mutt or some other program is running in it (probably also bash, but it's not that visible there), the program does not resize to the new window size, but to the last window size. I.e. I start xterm and it's 80x24. I then start mutt and resize to 90x24, but mutt stays at 80x24. I resize again to 100x24 and mutt goes to 90x24. Again to 60x24 and mutt goes to 100x24. And so on. Unfortunately this seems to be a rather sporadic bug. :-( It looks like when the program gets SIGWINCH and queries the new window size it still gets the old size from xterm. (race condition?) any other clues would be helpful. Usually I'm using fvwm and tcsh (and don't see any problems). Both the window manager and the shell have some influence. Looks exactly like this kernel problem: http://lkml.org/lkml/2008/8/11/538 - please confirm my testing under different kernel versions -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486158: [compiz-core] Configuration options are hardcoded in /usr/bin/compiz
retitle 486158 [compiz-core] Config files are not documented in the manpage thanks The settings can be stored in XDG-compliant locations: $HOME/.config/compiz/compiz-manager and /etc/xdg/compiz/compiz-manager. Thus, the user has a way to override the defaults, but has no way to figure this way out without reading the script. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489959: No decorations with intel driver
I have a G965 (i.e., a very similar chip) and compiz works if I start it as: mkdir -p ~/.config/compiz echo 'SKIP_CHECKS=yes' ~/.config/compiz/compiz-manager compiz --replace kconfig Note the kconfig above - without it no plugins will be loaded; GNOME users may want to run compiz --replace gconf instead. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484225: compiz-core: compiz-manager wrapper script modifies special ENV environment variable
The original patch attached to http://bugs.debian.org/484225 contains bashisms of the form export VARIABLE=VALUE. Please fix them instead of applying the patch blindly. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484225: compiz-core: compiz-manager wrapper script modifies special ENV environment variable
Julien Cristau wrote: On Mon, Jul 14, 2008 at 18:45:47 +0600, Alexander E. Patrakov wrote: The original patch attached to http://bugs.debian.org/484225 contains bashisms of the form export VARIABLE=VALUE. Please fix them instead of applying the patch blindly. Those aren't bashisms. Please give a reference (or, really, don't bother because you won't find one) instead of complaining blindly. Oops, sorry. I am after http://lists.boost.org/boost-build/2004/07/6890.php, which refers to Solaris. http://www.opengroup.org/onlinepubs/009695399/utilities/export.html does permit this syntax. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486330: xserver-xorg-video-vmware: it remaps keys in the Windows VM
reassign 486330 xserver-xorg-core found 486330 2:1.4.1~git20080517-1 retitle 486330 (EE) XKB: Couldn't compile keymap A.Lizard wrote: Package: xserver-xorg-video-vmware Version: 1:10.16.1-1 Severity: important the vm is W98SE, and the host is Linux Then xserver-xorg-video-vmware is completely irrelevant. It is a package to be installed in VMware guests as a video driver. OTOH, there is a keyboard-related error in your log: (EE) Error compiling keymap (server-0) (EE) XKB: Couldn't compile keymap Could you please update xkeyboard-config to the latest version and retest? -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: some accented chars double width
Dan Jacobson wrote: In uxterm, all these are single width and look fine, āáǎàēéěèīíǐìōóǒòūúǔùǖǘǚǜüê but in firefox and emacs, some are double width. In Emacs, that's understandable, because it uses core X font protocol, and the default XLC_LOCALE file tries Latin1, then some Japanese bitmap fonts. In firefox, this shouldn't happen. How might I remedy this? How can I tell fontcongig or whatever to first try Latin extended B before Chinese? That's not fontconfig! For Emacs, you could try downloading this file: http://chronos.nsu.ru/fantoo/wiki/gtk1_utf8/XLC_LOCALE Russians use it to work around a similar bug with GTK1 apps in the ru_RU.UTF-8 locale, but it might also work for you if you put this into /usr/X11R6/lib/X11/locale/en_US.UTF-8/XLC_LOCALE Or maybe I need to apt-get install more fonts. For Firefox, yes. Try ttf-dejavu together with fontconfig from unstable. Please report if this helps. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: some accented chars double width
I wrote: That's not fontconfig! For Emacs, you could try downloading this file: http://chronos.nsu.ru/fantoo/wiki/gtk1_utf8/XLC_LOCALE See also: https://bugs.freedesktop.org/show_bug.cgi?id=2676 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291137: /usr/X11R6/bin/luit: luit sometimes doesn't restore terminal settings or hangs
Marc Lehmann wrote: Sometimes, luit will hang completely. Attaching strace to luit in this case gives the following output: Process 14230 attached - interrupt to quit write(2, Couldn\'t copy terminal settings\n, 32) = 32 exit_group(1) = ? Process 14230 detached and exits. It looks like there is a race condition inside luit. It is likely an upstream issue because similar behaviour can be demonstrated ona fedora 3 system. Sounds suspiciously similar to this bug: http://bugs.xfree86.org/show_bug.cgi?id=1093 Does the patch from there help? -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: uxterm and no UTF-8 locale (followup to bug #246398)
Fr?d?ric Bothamy wrote: Maybe the priorities of xterm and uxterm could be reversed (or the uxterm script could be made smarter to launch xterm if no UTF-8 locale is found). For me, it's better to have the priorities reversed. Not defaulting to UTF-8 is a good idea now. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
