Bug#451791: solved (for me) in testing
dmanye wrote: > adding the suggested > >Option "AccelMethod" "XAA" > > solved my problem but as of today, doing an apt-get upgrade to lenny > *and rebooting* made the system working without adding AccelMethod to > xorg.conf. Can you send your xorg.conf so that we check that there is no other workaround enabled? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#487689: marked as done (X apparently crashes sometimes upon login in gdm)
Your message dated Wed, 13 Aug 2008 08:34:28 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#487689: no longer reproducible has caused the Debian Bug report #487689, regarding X apparently crashes sometimes upon login in gdm 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 487689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487689 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: xserver-xorg-video-intel Severity: important Version: 2:2.3.1-1 Once GDM presents its login screen and I enter my username/password, pressing enter causes X to restart about half a second after the login starts. Then, the GDM login screen is presented again, and logging in succeeds without problems. Attached is the diff between the Xorg.0.log.old and Xorg.0.log. The old one is from the session that seems to crash and the other one from the succeeded one. According with the differences, I'm guessing this problem is in the driver. Also, this started happening *around* the time the driver was upgraded to 2:2.3.1-1, though I'm not completely sure about the date (sorry for not having paid enough attention to this at that time). Greetings, Claudio -- Claudio Saavedra <[EMAIL PROTECTED]> Igalia --- /var/log/Xorg.0.log.old 2008-06-23 11:16:54.0 -0400 +++ /var/log/Xorg.0.log 2008-06-23 11:17:13.0 -0400 @@ -12,7 +12,7 @@ Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. -(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun 23 11:16:02 2008 +(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun 23 11:16:56 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) @@ -458,39 +458,12 @@ Markers: (--) probed, (**) from config f (II) Loading sub module "ramdac" (II) LoadModule: "ramdac"(II) Module "ramdac" already built-in (II) intel(0): Comparing regs from server start up to After PreInit -(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc008 to 0xd009 +(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc008 to 0xd00a (WW) intel(0): PP_STATUS before: on, ready, sequencing idle (WW) intel(0): PP_STATUS after: on, ready, sequencing on -(WW) intel(0): Register 0x68000 (TV_CTL) changed from 0x3000 to 0x000c0c00 -(WW) intel(0): Register 0x68010 (TV_CSC_Y) changed from 0x to 0x0332012d -(WW) intel(0): Register 0x68014 (TV_CSC_Y2) changed from 0x to 0x07d30104 -(WW) intel(0): Register 0x68018 (TV_CSC_U) changed from 0x to 0x0733052d -(WW) intel(0): Register 0x6801c (TV_CSC_U2) changed from 0x to 0x05c70200 -(WW) intel(0): Register 0x68020 (TV_CSC_V) changed from 0x to 0x0340030c -(WW) intel(0): Register 0x68024 (TV_CSC_V2) changed from 0x to 0x06d00200 -(WW) intel(0): Register 0x68028 (TV_CLR_KNOBS) changed from 0x to 0x00606000 -(WW) intel(0): Register 0x6802c (TV_CLR_LEVEL) changed from 0x to 0x010b00e1 -(WW) intel(0): Register 0x68030 (TV_H_CTL_1) changed from 0x to 0x00400359 -(WW) intel(0): Register 0x68034 (TV_H_CTL_2) changed from 0x to 0x80480022 -(WW) intel(0): Register 0x68038 (TV_H_CTL_3) changed from 0x to 0x007c0344 -(WW) intel(0): Register 0x6803c (TV_V_CTL_1) changed from 0x to 0x00f01415 -(WW) intel(0): Register 0x68040 (TV_V_CTL_2) changed from 0x to 0x00060607 -(WW) intel(0): Register 0x68044 (TV_V_CTL_3) changed from 0x to 0x80120001 -(WW) intel(0): Register 0x68048 (TV_V_CTL_4) changed from 0x to 0x000900f0 -(WW) intel(0): Register 0x6804c (TV_V_CTL_5) changed from 0x to 0x000a00f0 -(WW) intel(0): Register 0x68050 (TV_V_CTL_6) changed from 0x to 0x000900f0 -(WW) intel(0): Register 0x68054 (TV_V_CTL_7) changed from 0x to 0x000a00f0 -(WW) intel(0): Register 0x68060 (TV_SC_CTL_1) changed from 0x to 0xc1710088 -(WW) intel(0): Register 0x68064 (TV_SC_CTL_2) changed from 0x to 0x4e2d1dc8 -(WW) intel(0): Register 0x68070 (TV_WIN_POS) changed from 0x to 0x00360024 -(WW) intel(0): Register 0x68074 (TV_WIN_SIZE) changed from 0x to 0x02640198 -(WW) intel(0): Register 0x68080 (TV_FILTER_CTL_1) changed from 0x to 0x800010bb -(WW) intel(0): Register 0x68084 (TV_FILTER_CTL_2) changed from 0x to 0x00028283 -(WW) intel(0): Register 0x68088 (TV_FILTER_CTL_3) changed from 0x to 0x00014141 -(WW) intel(0): Register 0x68100 (T
Bug#494923: xvfb-run: feature request: option to isolate processes from parent environment
Package: xvfb
Version: 2:1.4.2-3
Severity: wishlist
File: /usr/bin/xvfb-run
Tags: patch
For e.g. automated testing of desktop applications, it would be nice
to have an xvfb-run mode that makes an effort to isolate the processes
it spawns from the user's normal environment. Specifically, it should
provide its own, empty, $HOME and $TMPDIR, and should attempt to unset
all environment variables that identify desktop services.
I attach a patch that does just this. It's not perfect: the biggest flaw
being that it relies on a list of shell glob patterns matching environment
variables to unset, and that list is surely incomplete. I don't use
KDE, for instance, so I had to guess what environment variables might
be relevant there. It works beautifully for my purposes, though.
$PATH is left intact, as is the current directory; this is intentional.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xvfb depends on:
ii libc6 2.7-13 GNU C Library: Shared libraries
ii libdbus-1-3 1.2.1-3simple interprocess messaging syst
ii libfontenc1 1:1.0.4-3 X11 font encoding library
ii libhal1 0.5.11-2 Hardware Abstraction Layer - share
ii libpixman-1-0 0.10.0-2 pixel-manipulation library for X a
ii libxau6 1:1.0.3-3 X11 authorisation library
ii libxdmcp6 1:1.0.2-3 X11 Display Manager Control Protoc
ii libxfont1 1:1.3.3-1 X11 font rasterisation library
ii x11-common1:7.3+15 X Window System (X.Org) infrastruc
Versions of packages xvfb recommends:
ii xbase-clients 1:7.3+15 miscellaneous X clients - metapack
ii xfonts-base 1:1.0.0-5 standard fonts for X
xvfb suggests no packages.
-- no debconf information
--- /usr/bin/xvfb-run 2008-08-02 15:26:56.0 -0700
+++ src/mozilla/xvfb-run2008-08-07 18:24:21.206536935 -0700
@@ -50,6 +50,8 @@
Options:
-a--auto-servernum try to get a free server number, starting
at
--server-num
+-i--isolate try to isolate processes running under Xvfb
+from the parent environment
-e FILE --error-file=FILE file used to store xauth errors and Xvfb
output (default: $ERRORFILE)
-f FILE --auth-file=FILE file used to store auth cookie
@@ -94,9 +96,22 @@
fi
}
+# Unset environment variables which might apply to a parent session
+# rather than the virtual session. This list is undoubtedly incomplete.
+clean_env() {
+for var in $(set | cut -d= -f1); do
+case $var in
+ DBUS_* | DESKTOP_* | DISPLAY | GDM* | GNOME_* | GPG_* | GTK_* | \
+ KDE* | QT* | SESSION_* | SSH_* | SCREEN* | XAUTHORITY )
+ unset $var
+ ;;
+ esac
+done
+}
+
# Parse the command line.
-ARGS=$(getopt --options +ae:f:hn:lp:s:w: \
- --long
auto-servernum,error-file:,auth-file:,help,server-num:,listen-tcp,xauth-protocol:,server-args:,wait:
\
+ARGS=$(getopt --options +aie:f:hn:lp:s:w: \
+ --long
auto-servernum,isolate,error-file:,auth-file:,help,server-num:,listen-tcp,xauth-protocol:,server-args:,wait:
\
--name "$PROGNAME" -- "$@")
GETOPT_STATUS=$?
@@ -111,6 +126,7 @@
case "$1" in
-a|--auto-servernum) SERVERNUM=$(find_free_servernum) ;;
-e|--error-file) ERRORFILE="$2"; shift ;;
+ -i|--isolate) ISOLATE="yes" ;;
-f|--auth-file) AUTHFILE="$2"; shift ;;
-h|--help) SHOWHELP="yes" ;;
-n|--server-num) SERVERNUM="$2"; shift ;;
@@ -144,16 +160,28 @@
# tidy up after ourselves
trap clean_up EXIT
-# If the user did not specify an X authorization file to use, set up a
temporary
-# directory to house one.
-if [ -z "$AUTHFILE" ]; then
+# If the user did not specify an X authorization file to use, or requested
+# a sanitized environment, we need a temporary directory.
+if [ -z "$AUTHFILE" ] || [ "$CLEANENV" ]; then
XVFB_RUN_TMPDIR="${TMPDIR:-/tmp}/$PROGNAME.$$"
if ! mkdir -p -m 700 "$XVFB_RUN_TMPDIR"; then
-error "temporary directory $XVFB_RUN_TMPDIR already exists"
exit 4
fi
+fi
+if [ -z "$AUTHFILE" ]; then
AUTHFILE=$(tempfile -n "$XVFB_RUN_TMPDIR/Xauthority")
fi
+if [ "$ISOLATE" ]; then
+ clean_env
+ if ! mkdir -p "$XVFB_RUN_TMPDIR/home" "$XVFB_RUN_TMPDIR/tmp"; then
+ exit 4
+ fi
+ HOME="$XVFB_RUN_TMPDIR/home"
+ TMP="$XVFB_RUN_TMPDIR/tmp"
+ TEMP="$XVFB_RUN_TMPDIR/tmp"
+ TMPDIR="$XVFB_RUN_TMPDIR/tmp"
+ export HOME TMP TEMP TMPDIR
+fi
# Start Xvfb.
MCOOKIE=$(mcookie)
Bug#487689: no longer reproducible
No longer reproducible with my up to date Unstable box. Claudio -- Claudio Saavedra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#489312: xserver-xorg-video-ati: Still happening
Alex Deucher wrote: > I'm not sure if debian still has packages of the rc releases > available. No, they are not available anymore. > Pull from git: > git clone git://git.freedesktop.org/git/xorg/driver/xf86-video-ati > checkout 6.8.191 by tag name: > git checkout -f xf86-video-ati-6.8.191 > configure: > ./autogen.sh --prefix=/usr > make: > make > install (as root): > make install > And before doing this, you can get the required development packages: $ apt-get install git-core xutils-dev $ apt-get build-dep xserver-xorg-video-ati If you need help, feel free to ask. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#489312: xserver-xorg-video-ati: Still happening
On Tue, Aug 12, 2008 at 10:42 AM, Jö Fahlke <[EMAIL PROTECTED]> wrote: > Am Tue, 12. Aug 2008, 10:07:10 -0400 schrieb Alex Deucher: >> RIght, but I asked about the 6.8.191 release candidates, not 6.9.0+ :) >> There were changes during the release candidate series that may be >> related. Hence if you could test a 6.8.191 rc release, that would >> help me narrow down the problem. > > Are there packages available somewhere, or do I have to compile myself? Where > exactly would I get the original sources? I've seen things like > > git clone git://git.freedesktop.org/git/xorg/driver/xf86-video-intel > > but I'm a bit confused because of the "xf86" part, I would expect "xorg" or > similar instead. > I'm not sure if debian still has packages of the rc releases available. if not, you will have to build from source. The xf86 is a vestige of the fact that these drivers originally came from xfree86 and the API's the implement were mostly from the xfree86 days. Also, remember to backup your original /usr/lib/xorg/modules/drivers/radeon_drv.so. Pull from git: git clone git://git.freedesktop.org/git/xorg/driver/xf86-video-ati checkout 6.8.191 by tag name: git checkout -f xf86-video-ati-6.8.191 configure: ./autogen.sh --prefix=/usr make: make install (as root): make install Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: notfound 280579 in 1.0~cvs.20070721-1
Processing commands for controlbugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35 > notfound 280579 1.0~cvs.20070721-1 Bug#280579: xlibs-data: [xkb] jp106 backslash/yen issue Bug no longer marked as found in version 1.0~cvs.20070721-1. (By the way, this Bug is currently marked as done.) > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#480024: xkb-data 1.2 doesn't support swedish letters
On Wed, May 7, 2008 at 18:59:58 +0200, Magnus Berg wrote: > The Swedish letters "å", "ä", and "ö" didn't work after upgrade Xkb-data > from 1.1~cvs.20080104.1-1 to 1.2~cvs.20080501.1-1. Those letters also > disapere when I copy and paste texts. > Downgrading xkb-data from 1.2~cvs.20080501.1-1 to1.1~cvs.20080104.1-1 > make the letters work again. > Hi Magnus, as far as I know xkb-data isn't involved in copy and paste so your report is a bit surprising. Does this issue still exist with xkb-data 1.3? If it is, please send us your /var/log/Xorg.0.log and /etc/X11/xorg.conf files, as well as the output of setxkbmap -print. Thanks, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: bug 483725 is forwarded to http://bugs.freedesktop.org/show_bug.cgi?id=16872, merging 483725 490013
Processing commands for controlbugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35 > forwarded 483725 http://bugs.freedesktop.org/show_bug.cgi?id=16872 Bug#483725: want "comma" variant for the romanian layout for backwards-compat Bug#485702: layout:ro variant:standard doesn't work Bug#486891: xorg: setxkbmap fails to properly set romanian std mapping Noted your statement that Bug has been forwarded to http://bugs.freedesktop.org/show_bug.cgi?id=16872. > merge 483725 490013 Bug#483725: want "comma" variant for the romanian layout for backwards-compat Bug#490013: xfce4-xkb-plugin: Not starting when layout 'ro' with variant 'std' is used Bug#485702: layout:ro variant:standard doesn't work Bug#486891: xorg: setxkbmap fails to properly set romanian std mapping Merged 483725 485702 486891 490013. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459944: xkb-data: Broken Swedish keyboard layout
On Wed, Jan 9, 2008 at 19:13:14 +0100, Davide Mancusi wrote: > My X server is configured with a double keyboard layout, as this excerpt > from the config file shows: > > Section "InputDevice" > Identifier "Generic Keyboard" > Driver "kbd" > Option "CoreKeyboard" > Option "XkbRules" "xorg" > Option "XkbModel" "pc104" > Option "XkbLayout" "it,se" > Option "XkbOptions" > "grp:shifts_toggle,compose:menu,lv3:rwin_switch" > EndSection > > However, the Swedish (se) layout has been broken for a while now. If I > type "qwerty", for example, I obtain "@ł€rt←". A workaround consists in > running setxkbmap without arguments. > Hi Davide, if you still experience this with xkb-data 1.3, can you send us your Xorg log, and the output of 'setxkbmap -print' and 'xkbcomp :0 -' when the keymap is b0rked? Thanks, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#460269: xkb-data: layout=us + variant=nodeadkeys breaks + ...
On Fri, Jan 11, 2008 at 18:17:22 +0100, Andreas Beckmann wrote: > when I recently switched the x keyboard config from layout=de to > layout=us, this broke +, ... i.e. switching to the ttys which > didn't react at all. I checked a bit further and found this to be caused > by the > Option "XkbVariant""nodeadkeys" > which was left from the previous config. After removing this, switching > to the ttys worked again. > Hi Andreas, switching to the ttys is done with ctrl+alt+Fn, not ctrl+Fn. If that still doesn't work with xkb-data 1.3, can you please send your Xorg log (/var/log/Xorg.0.log) and config (/etc/X11/xorg.conf), as well as the output of setxkbmap -print? Thanks, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: forcibly merging 485702 483725 486891, tagging 485702
Processing commands for controlbugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35 > forcemerge 485702 483725 486891 Bug#485702: layout:ro variant:standard doesn't work Bug#483725: want "comma" variant for the romanian layout for backwards-compat Bug#486891: xorg: setxkbmap fails to properly set romanian std mapping Forcibly Merged 483725 485702 486891. > tags 485702 patch upstream fixed-upstream Bug#485702: layout:ro variant:standard doesn't work There were no tags set. Bug#483725: want "comma" variant for the romanian layout for backwards-compat Bug#486891: xorg: setxkbmap fails to properly set romanian std mapping Tags added: patch, upstream, fixed-upstream > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405940: combine key dosn't work anymore
On Sat, Jan 13, 2007 at 10:44:25 +0100, Klaus Ethgen wrote: > Ah yes, The setting from my xorg.conf is: > Section "InputDevice" >Identifier "Keyboard" >Driver "keyboard" >Option "CoreKeyboard" >Option "XkbRules" "xorg" >Option "XkbModel" "cherrybluec" >Option "XkbLayout" "de" >Option "XkbVariant" "nodeadkeys" >Option "XkbOptions" "level3:ralt_switch_multikey" >Option "XkbSymbols" > "pc(pc105)+de(nodeadkeys)+level3(ralt_switch_multikey)+inet(cherrybluec)" >#Option "XkbSymbols" "pc/pc(pc105)+pc/de(nodeadkeys)+inet(cherryblue)" >#Option "CustomKeycodes""on" > EndSection > Hi, It looks like you need to change level3:ralt_switch_multikey to lv3:ralt_switch_multikey in XkbOptions (also, try commenting out the XkbSymbols setting). Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#481364: xkb-data: Stock keyboard layout broken
On Thu, May 15, 2008 at 17:05:53 +0200, [EMAIL PROTECTED] wrote: > The stock keyboard layout loaded with xorg.conf entry > > Section "InputDevice" > Identifier "Generic Keyboard" > Driver "kbd" > Option "CoreKeyboard" > Option "XkbRules" "xorg" > Option "XkbModel" "pc105" > Option "XkbLayout" "de" > Option "XkbVariant" "nodeadkeys" > EndSection > > is completely broken. To get Mode_switch to work correctly Broken how? > and having no problems with broken modifiers, I had to load > > remove mod4 = Super_L > remove mod4 = Hyper_L > clear mod1 > clear mod5 > keycode 93 = > keycode 124 = > keycode 125 = > keycode 126 = > keycode 127 = > keycode 128 = > keycode 156 = > keycode 214 = > > keycode 113 = Mode_switch > add mod4 = Super_L > add mod3 = Super_R > add mod1 = Alt_L > > each time I start X. (.xsession does load my .Xmodmap). > > Without this I had not been able to type a \ or | in an xterm. > Can you attach your Xorg.0.log? also please send the output of "setxkbmap -print", and of "setxkbmap -v 10 -model pc105 -layout de -variant nodeadkeys". Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494846: xserver-xorg-video-tga: FTBFS on kfreebsd-amd64 (kfreebsd-amd64 is not in the architecture list)
Package: xserver-xorg-video-tga Version: 1:1.1.0-9 Severity: important Tags: patch User: [EMAIL PROTECTED] Usertags: kfreebsd Hi, the current version fails to build on kfreebsd-amd64. It is sufficient to add kfreebsd-amd64 into Architecture: line, similarly as already done for both amd64 and kfreebsd-i386. Unavailability of xserver-xorg-video-tga currently makes xserver-xorg-video-all uninstallable on kfreebsd-amd64. Petr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#489312: xserver-xorg-video-ati: Still happening
Am Tue, 12. Aug 2008, 10:07:10 -0400 schrieb Alex Deucher: > RIght, but I asked about the 6.8.191 release candidates, not 6.9.0+ :) > There were changes during the release candidate series that may be > related. Hence if you could test a 6.8.191 rc release, that would > help me narrow down the problem. Are there packages available somewhere, or do I have to compile myself? Where exactly would I get the original sources? I've seen things like git clone git://git.freedesktop.org/git/xorg/driver/xf86-video-intel but I'm a bit confused because of the "xf86" part, I would expect "xorg" or similar instead. Bye, Jö. -- This just in: "Since 2001, there has been a 300-fold rise in terror acts worldwide". Know what would be cool? If the Bush administration declared a war on jobs. -- J.L. Grant, http://flem.comicgenesis.com/d/20040726.html signature.asc Description: Digital signature
Bug#489312: xserver-xorg-video-ati: Still happening
On Mon, Aug 11, 2008 at 11:37 AM, Jö Fahlke <[EMAIL PROTECTED]> wrote: > Package: xserver-xorg-video-ati > Version: 1:6.9.0-1+lenny1 > Followup-For: Bug #489312 > > Alex Deucher <[EMAIL PROTECTED]> wrote: >> Does it still happen with the 6.8.191 rc? > > It happens for me with 1:6.9.0-1+lenny1. At least the "blackouts" of the > screen for about half a second, I haven't seen the "flickers". I can confirm > that moving a window makes the blackouts happen for sure, but they also happen > from time to time otherwise. RIght, but I asked about the 6.8.191 release candidates, not 6.9.0+ :) There were changes during the release candidate series that may be related. Hence if you could test a 6.8.191 rc release, that would help me narrow down the problem. Thanks, Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494349: libqt3-mt: throws errors and sometimes crashes X
2008/8/12 Michel Dänzer <[EMAIL PROTECTED]>: > On Mon, 2008-08-11 at 22:32 +0200, booiiing wrote: >> 2008/8/9 booiiing <[EMAIL PROTECTED]>: >> > 2008/8/9 Julien Cristau <[EMAIL PROTECTED]>: >> >> No, it's a bug in X. Are you using a compositing manager? Which one? >> > deactivating it didn't change anything, however. > Well, at least compResizeWindow() can't really be involved anymore > without a compositing manager. It would be good to get gdb backtraces > for both cases. BTW, which video driver are you using? i use the closed-source driver by nvidia, version x86_64-173.14.12-pkg2, the kernel-module is compiled by the installer using the boxed kernel 2.6.26-2 and its headers. for the first trace see the end of this mail. >> > but i'll try to restart X with composite completely disabled. >> i tried some things now, but nothing helped. the guis are still >> malformed and i still get those error, although it seems to me that >> there are less of them with composite disabled. >> what worries me, is that my Xorg.0.log says >> (**) Extension "Composite" is disabled >> and later >> (II) Initializing built-in extension COMPOSITE > No worries, the latter is a bit confusing and doesn't mean the extension > is actually enabled. You can verify it with > xdpyinfo|grep Composite ok, verified. thank you. it seems that without the composite-manager the apps don't crash x anymore, however they're still not usable. i ran qtconfig-qt3 in gdb and set a breakpoint to QTextParagraph::lineInfo. here is the trace: #0 QTextParagraph::lineInfo (this=0x1c85cb0, l=0, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]) at kernel/qrichtext_p.cpp:554 #1 0x7f4a2e77a79d in QTextParagraph::paint (this=0x1c85cb0, [EMAIL PROTECTED], [EMAIL PROTECTED], cursor=0x0, drawSelections=false, clipx=0, clipy=0, clipw=196, cliph=520) at kernel/qrichtext.cpp:4623 #2 0x7f4a2e77b2ec in QTextDocument::drawParagraph (this=0x7fff370234e0, p=0x7fff370237f0, parag=0x1c85cb0, cx=0, cy=0, cw=196, ch=520, [EMAIL PROTECTED], [EMAIL PROTECTED], drawCursor=false, cursor=0x0, resetChanged=true) at kernel/qrichtext.cpp:3240 #3 0x7f4a2e77bc4d in QTextDocument::draw (this=0x1c804f0, p=0x7fff370237f0, cx=0, cy=0, cw=196, ch=520, [EMAIL PROTECTED], onlyChanged=false, drawCursor=false, cursor=0x1d58070, resetChanged=true) at kernel/qrichtext.cpp:3300 #4 0x7f4a2e855d5c in QTextEdit::paintDocument (this=0x1c7d120, drawAll=true, p=0x7fff370237f0, cx=0, cy=0, cw=196, ch=520) at widgets/qtextedit.cpp:1059 #5 0x7f4a2e8698ee in QTextEdit::drawContents (this=0x1c85cb0, p=0x7fff370237f0, cx=0, cy=0, cw=196, ch=520) at widgets/qtextedit.cpp:1081 #6 0x7f4a2e81c8c7 in QScrollView::viewportPaintEvent (this=0x1c7d120, pe=0x7fff37023d00) at widgets/qscrollview.cpp:1709 #7 0x7f4a2e81dc33 in QScrollView::eventFilter (this=0x1c7d120, obj=0x1c7e0a0, e=0x7fff37023d00) at widgets/qscrollview.cpp:1492 #8 0x7f4a2e867295 in QTextEdit::eventFilter (this=0x1c7d120, o=0x1c7e0a0, e=0x7fff37023d00) at widgets/qtextedit.cpp:3030 #9 0x7f4a2e725972 in QObject::activate_filters (this=0x1c7e0a0, e=0x7fff37023d00) at kernel/qobject.cpp:906 #10 0x7f4a2e7259c7 in QObject::event (this=0x1c7e0a0, e=0x7fff37023d00) at kernel/qobject.cpp:738 #11 0x7f4a2e756df3 in QWidget::event (this=0x1c85cb0, e=0x0) at kernel/qwidget.cpp:4681 #12 0x7f4a2e6d0953 in QApplication::internalNotify ( this=, receiver=0x1c7e0a0, e=0x7fff37023d00) at kernel/qapplication.cpp:2638 #13 0x7f4a2e6d162e in QApplication::notify (this=0x7fff37024510, receiver=0x1c7e0a0, e=0x7fff37023d00) at kernel/qapplication.cpp:2526 #14 0x7f4a2e6a7f11 in QWidget::repaint (this=0x1c7e0a0, [EMAIL PROTECTED], erase=false) at kernel/qapplication.h:523 #15 0x7f4a2e6d20d5 in QApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qapplication.cpp:3299 #16 0x7f4a2e6869dd in QEventLoop::processEvents (this=0x1c3ff80, flags=4) at kernel/qeventloop_x11.cpp:147 #17 0x7f4a2e6e5001 in QEventLoop::enterLoop (this=0x1c85cb0) at kernel/qeventloop.cpp:201 #18 0x7f4a2e6e4eb2 in QEventLoop::exec (this=0x1c85cb0) at kernel/qeventloop.cpp:148 #19 0x0040f26d in main (argc=1, argv=) at main.cpp:44
Bug#451791: solved (for me) in testing
hi, i was hit by this bug in a lenny installation (d-i rc2 netinstall + task desktop, and no further config) some days/weeks ago (i have an i965 board). my problem was that fonts and icons were not displayed at all (fonts got visible only if set to monochrome in the gnome preferences and only for some type of fonts). adding the suggested Option "AccelMethod" "XAA" solved my problem but as of today, doing an apt-get upgrade to lenny *and rebooting* made the system working without adding AccelMethod to xorg.conf. salut. begin:vcard fn;quoted-printable:david many=C3=A9 n;quoted-printable:many=C3=A9;david org;quoted-printable:Universitat Rovira i Virgili;Departament d'Enginyeria Inform=C3=A0tica i Matem=C3=A0tiques adr;quoted-printable;dom:;;Av. dels Pa=C3=AFsos Catalans, 26;Tarragona;;43007 email;internet:[EMAIL PROTECTED] tel;work:977559706 version:2.1 end:vcard
Bug#494349: libqt3-mt: throws errors and sometimes crashes X
On Mon, 2008-08-11 at 22:32 +0200, booiiing wrote: > 2008/8/9 booiiing <[EMAIL PROTECTED]>: > > 2008/8/9 Julien Cristau <[EMAIL PROTECTED]>: > >> No, it's a bug in X. Are you using a compositing manager? Which one? > > deactivating it didn't change anything, however. Well, at least compResizeWindow() can't really be involved anymore without a compositing manager. It would be good to get gdb backtraces for both cases. BTW, which video driver are you using? > > but i'll try to restart X with composite completely disabled. > i tried some things now, but nothing helped. the guis are still > malformed and i still get those error, although it seems to me that > there are less of them with composite disabled. > > what worries me, is that my Xorg.0.log says > (**) Extension "Composite" is disabled > and later > (II) Initializing built-in extension COMPOSITE No worries, the latter is a bit confusing and doesn't mean the extension is actually enabled. You can verify it with xdpyinfo|grep Composite -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494172: searching a workaround
I have downloaded the Debian Mesa sources to try to compile Mesa and OSMesa like the standard Mesa package. I see that the Mesa make command show me some configurations like the standard package linux-* but som that not are in the standard debian-*. Now looking in the debian/rules I found debian-* configurations, I changed it for linux-* but compilation process fails. Any idea? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
