Bug#879624: Similar issue, also X1 carbon
Looking into possible known issues for at-spi or gnome-terminal-server did not bring up anything useful for me. FTR: Installing xfce4 or kde both gives me a working desktop. So this might actually be a GNOME issue rather than an X issue, or an interaction of the two. On Sat, Nov 4, 2017 at 10:14 AM, Michael Hanke <michael.ha...@gmail.com> wrote: > Update: > > I stopped the gdm3 service and started a freshly installed slim login > manager. I comes right up, no issues. > > Starting the GNOME session from slim, however, results in immediate > failure. This is syslog from the last message of slim to the X server > shutdown: > > Nov 4 09:49:56 meiner slim[8940]: /usr/bin/X11/xauth: file > /home/mih/.Xauthority does not exist > Nov 4 09:49:56 meiner org.a11y.Bus[9347]: Activating service > name='org.a11y.atspi.Registry' > Nov 4 09:49:56 meiner org.a11y.Bus[9347]: Successfully activated > service 'org.a11y.atspi.Registry' > Nov 4 09:49:56 meiner org.a11y.atspi.Registry[9373]: SpiRegistry > daemon is running with well-known name - org.a11y.atspi.Registry > Nov 4 09:49:56 meiner gnome-terminal-[9379]: gnome-terminal-server: > Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. > Nov 4 09:49:56 meiner org.a11y.atspi.Registry[9373]: XIO: fatal IO > error 11 (Resource temporarily unavailable) on X server ":0.0" > Nov 4 09:49:56 meiner org.a11y.atspi.Registry[9373]: after 21 > requests (19 known processed) with 0 events remaining. > Nov 4 09:49:56 meiner org.gtk.vfs.Daemon[9347]: A connection to the > bus can't be made > Nov 4 09:49:58 meiner kernel: [ 249.268908] [drm] Reducing the > compressed framebuffer size. This may lead to less power savings than > a non-reduced-size. Try to increase stolen memory size if available in > BIOS. > Nov 4 09:49:58 meiner slim[8940]: (II) Server terminated successfully > (0). Closing log file. > > On Fri, Nov 3, 2017 at 5:02 PM, Michael Hanke <michael.ha...@gmail.com> wrote: >> Hi, >> >> same here, after upgrade to buster no X anymore. Normal start works, but >> ends at terminal login. Manual startx makes the screen flicker briefly, then >> back to terminal. X log contain no errors (EE). >> >> Downgrade to stretch didn't change the situation in any way. Going back from >> linux 4.13 to 4.8 had no effect either. >> >> During downgrade gconf2 choked (triggers hung and never completed). During >> upgrade I think I saw some gconf error message too, but I cannot find a >> trace of them anywhere. >> >> Any advice would be highly appreciated. >> >> Thanks in advance >> >> Michael >> > > > > -- > Michael Hanke > http://psychoinformatics.de -- Michael Hanke http://psychoinformatics.de
Bug#879624: Similar issue, also X1 carbon
Update: I stopped the gdm3 service and started a freshly installed slim login manager. I comes right up, no issues. Starting the GNOME session from slim, however, results in immediate failure. This is syslog from the last message of slim to the X server shutdown: Nov 4 09:49:56 meiner slim[8940]: /usr/bin/X11/xauth: file /home/mih/.Xauthority does not exist Nov 4 09:49:56 meiner org.a11y.Bus[9347]: Activating service name='org.a11y.atspi.Registry' Nov 4 09:49:56 meiner org.a11y.Bus[9347]: Successfully activated service 'org.a11y.atspi.Registry' Nov 4 09:49:56 meiner org.a11y.atspi.Registry[9373]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Nov 4 09:49:56 meiner gnome-terminal-[9379]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. Nov 4 09:49:56 meiner org.a11y.atspi.Registry[9373]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" Nov 4 09:49:56 meiner org.a11y.atspi.Registry[9373]: after 21 requests (19 known processed) with 0 events remaining. Nov 4 09:49:56 meiner org.gtk.vfs.Daemon[9347]: A connection to the bus can't be made Nov 4 09:49:58 meiner kernel: [ 249.268908] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Nov 4 09:49:58 meiner slim[8940]: (II) Server terminated successfully (0). Closing log file. On Fri, Nov 3, 2017 at 5:02 PM, Michael Hanke <michael.ha...@gmail.com> wrote: > Hi, > > same here, after upgrade to buster no X anymore. Normal start works, but > ends at terminal login. Manual startx makes the screen flicker briefly, then > back to terminal. X log contain no errors (EE). > > Downgrade to stretch didn't change the situation in any way. Going back from > linux 4.13 to 4.8 had no effect either. > > During downgrade gconf2 choked (triggers hung and never completed). During > upgrade I think I saw some gconf error message too, but I cannot find a > trace of them anywhere. > > Any advice would be highly appreciated. > > Thanks in advance > > Michael > -- Michael Hanke http://psychoinformatics.de
Bug#879624: Similar issue, also X1 carbon
Hi, same here, after upgrade to buster no X anymore. Normal start works, but ends at terminal login. Manual startx makes the screen flicker briefly, then back to terminal. X log contain no errors (EE). Downgrade to stretch didn't change the situation in any way. Going back from linux 4.13 to 4.8 had no effect either. During downgrade gconf2 choked (triggers hung and never completed). During upgrade I think I saw some gconf error message too, but I cannot find a trace of them anywhere. Any advice would be highly appreciated. Thanks in advance Michael
Bug#817195: Same observation
Hi, On Sat, Mar 19, 2016 at 01:38:51PM +0100, Julien Cristau wrote: > On Tue, Mar 15, 2016 at 15:34:18 +0100, Michael Hanke wrote: > > If this package is responsible, the most recent upgrade in my system > > happened on 2016-03-11, upgrading from 2.99.917-2 to > > 2.99.917+git20160218-1. > > > Your best bet is probably to actually check if reverting to an older > version of the intel driver fixes the issue, and if it does, to file > this upstream per > https://01.org/linuxgraphics/documentation/development/how-report-bugs A similar bugs has already been reported: https://bugs.freedesktop.org/show_bug.cgi?id=94578 Michael
Bug#817195: Duplicate
Likely duplicate: https://bugs.debian.org/818384
Bug#818384: Duplicate
This is likely a duplicate of https://bugs.debian.org/817195
Bug#817195: Same observation
Hi, I seem to observe the exact same behavior on a machine with a different chipset 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) and using a Display Port connection. Gnome shell in use also. It doesn't depend on the particular DP device connected, and the behavior was introduced by (or co-occurred with) a recent package upgrade. If this package is responsible, the most recent upgrade in my system happened on 2016-03-11, upgrading from 2.99.917-2 to 2.99.917+git20160218-1. Thanks, Michael
Bug#624156: Status?
On Wed, Jun 22, 2011 at 11:15:35AM +0200, Cyril Brulebois wrote: Well, it looks like nothing changed since http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=20;bug=624156 so you know what to do if you want to help. Cloned it and looking into configure.ac it seems like the addition of src/glw/GLwDrawA.c (that has these symbols) is conditioned upon --enable-glw, whereas debian/rules sets --disable-glw by default and doesn't change it whenever --enable-motif is set. I tried to address this by: michael@meiner ~/mesa (git)-[debian-unstable] % git diff -- debian/rules diff --git a/debian/rules b/debian/rules index cedef45..61a98ce 100755 --- a/debian/rules +++ b/debian/rules @@ -167,6 +167,7 @@ confflags-swx11+glu = \ --disable-gl-osmesa \ --disable-egl \ --disable-glut \ + --enable-glw \ --enable-motif \ CFLAGS=$(CFLAGS) \ CXXFLAGS=$(CXXFLAGS) @@ -190,6 +191,7 @@ confflags-swx11+glu-i386-i686 = \ --disable-gl-osmesa \ --disable-glut \ --disable-egl \ + --enable-glw \ --enable-motif \ --libdir=/usr/lib/$(DEB_HOST_MULTIARCH)/i686/cmov \ CFLAGS=$(CFLAGS) -march=i686 \ And got that in response: michael@meiner ~/mesa (git)-[debian-unstable] % nm build/swx11+glu-i386-i686/cmov/libGLw.so |grep glwMDrawing 36c0 d glwMDrawingAreaClassRec 3754 d glwMDrawingAreaWidgetClass michael@meiner ~/mesa (git)-[debian-unstable] % nm build/swx11+glu-i386-i686/cmov/libGLw.so |grep glwMDrawing 36c0 d glwMDrawingAreaClassRec 3754 d glwMDrawingAreaWidgetClass It looks like it worked. However, given that I am totally unfamiliar with mesa, I have little to no clue what side-effects something like this might have. Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110622131620.GA5941@meiner
Bug#631236: libglw1-mesa-dev: Please allow for libmotif-dev to satisfy lesstif2-dev dependency
Package: libglw1-mesa-dev Severity: normal Hi, since mesa 7.8.2-1 it seems to be impossible to develop MOTIF apps that also need mesa, as a dependency to lesstif2-dev was added to libglw1-mesa-dev. lesstif2-dev and libmotif-dev conflict with each other. It would be nice if libglw1-mesa-dev would allow for libmotif-dev to also satisfy this dependency. lesstif and motif should be mostly compatible. However, sometimes it needs motif: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409849#105 Thanks, Michael -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110621205753.28361.75547.reportbug@meiner
Bug#624156: Status?
Hi, what is the status of this bug? I assume this bug is also the reason why the glwDrawingAreaWidgetClass (without M) is missing in the shared library. Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110622012849.GA21873@meiner
Bug#489141: xserver-xorg: X server sometimes refuses local xclients to connect
Hi Cyril, On Fri, Feb 25, 2011 at 11:27:12PM +0100, Cyril Brulebois wrote: Michael Hanke michael.ha...@gmail.com (09/02/2009): Yes, it still happens -- less frequently then before, but since the whole thing seems to have some random element I would not put any weight on that observation. still happening with squeeze or higher? Is your $HOME on a particular (e.g. network-based) filesystem? Unfortunately, I won't have physical access to the machines that showed that behavior for the next months and I don't think they have been upgraded to squeeze yet. Sorry, Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110226004340.GA5666@meiner
Bug#489141: xserver-xorg: X server sometimes refuses local xclients to connect
Sorry, for the delay. On Mon, Feb 02, 2009 at 07:11:02AM +0100, Michael Hanke wrote: On Sun, Feb 01, 2009 at 09:37:11PM +0100, Brice Goglin wrote: On Thu, Jul 03, 2008 at 02:20:26PM +0200, Michael Hanke wrote: first I have to say that I am not sure if this is the appropriate place to report this bug. However, I have no clue what causes it, which makes it difficult for me to convince myself that it was not reported elsewhere or what place would be more appropriate. So, I'd be glad if you could forward this any other/better place. Thanks. Since a few weeks I'm experiencing the situation that from time to time local X clients cannot connect to the local X server: ha...@balin:~$ xcalc No protocol specified Error: Can't open display: :0 Does this still happen with latest packages? Yes, it still happens -- less frequently then before, but since the whole thing seems to have some random element I would not put any weight on that observation. Thanks, Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#489141: xserver-xorg: X server sometimes refuses local xclients to connect
On Sun, Feb 01, 2009 at 09:37:11PM +0100, Brice Goglin wrote: On Thu, Jul 03, 2008 at 02:20:26PM +0200, Michael Hanke wrote: first I have to say that I am not sure if this is the appropriate place to report this bug. However, I have no clue what causes it, which makes it difficult for me to convince myself that it was not reported elsewhere or what place would be more appropriate. So, I'd be glad if you could forward this any other/better place. Thanks. Since a few weeks I'm experiencing the situation that from time to time local X clients cannot connect to the local X server: ha...@balin:~$ xcalc No protocol specified Error: Can't open display: :0 Does this still happen with latest packages? I did still happen last week, but I will check again today. In the meantime I investigated whether clock differences caused this behavior, but syncronizing server and client with NTP did not help. Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#489141: xserver-xorg: X server sometimes refuses local xclients to connect
Hi, I'm still seeing this behavior occasionally. But recently I'm made another observation. During the time when no X clients can cannot I see this: [EMAIL PROTECTED]:~$ xauth list :0 xauth: /home/hanke/.Xauthority not writable, changes will be ignored balin/unix:0 MIT-MAGIC-COOKIE-1 18f7c5d44dfa751698177b1e48daab42 When looking at the permission, I have: [EMAIL PROTECTED]:~$ ll .Xauthority -rw--- 1 hanke users 2,4K 21. Aug 10:52 .Xauthority but now, the next call to xauth looks _always_ (n=10 so far) like this: [EMAIL PROTECTED]:~$ xauth list :0 balin/unix:0 MIT-MAGIC-COOKIE-1 18f7c5d44dfa751698177b1e48daab42 and after that the problem is _always_ fixed, ie. client can connect again. The timing seems to be irrelevant, as soon as I do this, no matter how quick or slow after I discovered the problem, it is fixed. HTH, Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489141: xserver-xorg: X server sometimes refuses local xclients to connect
On Thu, Jul 03, 2008 at 02:35:35PM +0200, Julien Cristau wrote: On Thu, Jul 3, 2008 at 14:20:26 +0200, Michael Hanke wrote: Since a few weeks I'm experiencing the situation that from time to time local X clients cannot connect to the local X server: [EMAIL PROTECTED]:~$ xcalc No protocol specified Error: Can't open display: :0 While at the same time foreign clients (via SSH connection) can connect without problems: [EMAIL PROTECTED]:/media/local2/working/hanke/catface2$ xcalc Warning: Cannot convert string calculator to type Pixmap Warning: Cannot convert string gray3?foreground=gray70background=gray85 to type Pixmap What's the value of $DISPLAY in both cases? If you could install libx11-6-dbg (and maybe libxcb-xlib0-dbg and libxcb1-dbg) and trace what's happening when this fails, using gdb, that would probably help a lot. Sorry for the delay, the bug only hit me a few times since I reported it and lasted only for a few seconds (at least after I discovered it). But now it happended again. I have: [EMAIL PROTECTED]:~$ apt-show-versions | grep 'libx.*-dbg' libx11-6-dbg/lenny uptodate 2:1.1.4-2 libxcb1-dbg/lenny uptodate 1.1-1.1 and here it happens: [EMAIL PROTECTED]:~$ xcalc No protocol specified Error: Can't open display: :0.0 [EMAIL PROTECTED]:~$ echo $DISPLAY :0.0 [EMAIL PROTECTED]:~$ gdb xcalc GNU gdb 6.7.1-debian Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu... (no debugging symbols found) Using host libthread_db library /lib/i686/cmov/libthread_db.so.1. (gdb) run Starting program: /usr/bin/xcalc (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) No protocol specified Error: Can't open display: :0.0 Program exited with code 01. (gdb) After a approx. a minute things are working again: [EMAIL PROTECTED]:~$ xcalc Warning: Cannot convert string calculator to type Pixmap Warning: Cannot convert string gray3?foreground=gray70background=gray85 to type Pixmap [EMAIL PROTECTED]:~$ echo $DISPLAY :0.0 Does this help? Should I do anything special with GDB? Thanks, Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489141: xserver-xorg: X server sometimes refuses local xclients to connect
failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) (II) Open ACPI successful (/var/run/acpid.socket) SetClientVersion: 0 9 SetGrabKeysState - disabled AUDIT: Thu Jul 3 12:24:53 2008: 2744 X: client 28 rejected from local host (uid 1000) AUDIT: Thu Jul 3 12:24:53 2008: 2744 X: client 28 rejected from local host (uid 1000) SetGrabKeysState - enabled SetClientVersion: 0 9 SetGrabKeysState - disabled SetGrabKeysState - enabled AUDIT: Thu Jul 3 13:29:13 2008: 2744 X: client 26 rejected from local host (uid 1000) AUDIT: Thu Jul 3 13:29:13 2008: 2744 X: client 26 rejected from local host (uid 1000) AUDIT: Thu Jul 3 13:46:17 2008: 2744 X: client 26 rejected from local host (uid 1000) AUDIT: Thu Jul 3 13:46:17 2008: 2744 X: client 26 rejected from local host (uid 1000) AUDIT: Thu Jul 3 13:46:17 2008: 2744 X: client 26 rejected from local host (uid 1000) AUDIT: Thu Jul 3 13:52:13 2008: 2744 X: client 26 rejected from local host (uid 1000) AUDIT: Thu Jul 3 13:52:24 2008: 2744 X: client 26 rejected from local host (uid 1000) AUDIT: Thu Jul 3 13:52:31 2008: 2744 X: client 26 rejected from local host (uid 1000) AUDIT: Thu Jul 3 13:52:32 2008: 2744 X: client 26 rejected from local host (uid 1000) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg depends on: ii debconf [debconf- 1.5.22 Debian configuration management sy ii x11-common1:7.3+10 X Window System (X.Org) infrastruc ii x11-xkb-utils 7.4+1 X11 XKB utilities ii xkb-data 1.3-1 X Keyboard Extension (XKB) configu ii xserver-xorg-core 2:1.4.1~git20080517-2 Xorg X server - core server ii xserver-xorg-inpu 1:7.3+10 the X.Org X server -- input driver ii xserver-xorg-inpu 1:1.2.0-1 X.Org X server -- evdev input driv ii xserver-xorg-inpu 1:1.3.1-1 X.Org X server -- keyboard input d ii xserver-xorg-inpu 1:1.3.0-1 X.Org X server -- mouse input driv ii xserver-xorg-inpu 0.14.7~git20070706-2.1 Synaptics TouchPad driver for X.Or ii xserver-xorg-inpu 0.8.0.2-2 X.Org X server -- Wacom input driv ii xserver-xorg-vide 2:2.3.2-1 X.Org X server -- Intel i8xx, i9xx ii xserver-xorg-vide 1:1.3.0-4 X.Org X server -- VESA display dri Versions of packages xserver-xorg recommends: ii dmidecode 2.9-1 Dump Desktop Management Interface ii libgl1-mesa-dri 7.0.3-4A free implementation of the OpenG ii udev 0.114-2/dev/ and hotplug management daemo -- debconf information: shared/fontpath/fontserver: * xserver-xorg/config/monitor/use_sync_ranges: true xserver-xorg/config/doublequote_in_string_error: xserver-xorg/config/device/default-identifier: shared/no_known_x-server: xserver-xorg/config/device/bus_id_error: * xserver-xorg/config/inputdevice/keyboard/options: * xserver-xorg/autodetect_keyboard: false * xserver-xorg/config/device/use_fbdev: false * xserver-xorg/config/inputdevice/keyboard/variant: nodeadkeys xserver-xorg/config/nonnumeric_string_error: * xserver-xorg/config/inputdevice/keyboard/layout: de * xserver-xorg/config/inputdevice/mouse/emulate3buttons: true * xserver-xorg/config/inputdevice/keyboard/model: pc105 * xserver-xorg/config/device/driver: xserver-xorg/config/null_string_error: shared/multiple_possible_x-servers: * xserver-xorg/config/device/bus_id: PCI:0:2:0 * xserver-xorg/config/inputdevice/keyboard/rules: xorg -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject
Bug#438850: xserver-xorg-video-nv: Unable to use native DFP resolution
Hi, I looked into an old backup of my xorg.conf and found the reason why it was working on etch. I was using the proprietary nvidia driver and had the following line added manually to the device section: Option ModeValidation NoMaxPClkCheck, NoEdidMaxPClkCheck Using this line and the 'nvidia' driver the screen works properly on a fresh etch installation and a fresh install of lenny on the same machine. It also works with the free ati driver (when connected to an ATI card) on etch and lenny. On both releases the free 'nv' driver fails to set the correct resolution and shows the behavior reported in previously. Cheers, Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 signature.asc Description: Digital signature
Bug#438850: xserver-xorg-video-nv: Unable to use native DFP resolution
On Mon, Aug 20, 2007 at 09:00:28PM +0200, Brice Goglin wrote: Michael Hanke wrote: I just upgraded from etch to lenny and my screen does not show its native resolution anymore. As you can see from the logfile dump below the native resolution of my screen is 1680x1050. This is confirmed by ddcprobe and xresprobe: [...] The whole setup worked perfectly at 1680x1050 on Debian etch. Could you try some packages between 1.2.0 (Etch) and 2.1.3 (current)? It would be good to know when the bug appeared before I report this problem to the upstream developer. snip Thanks for the URLs -- made it very convenient. But unfortunately it did not work. Even with the oldest driver the panel size is reported as 1280x1024 and the (listed) 1680x1050 mode is not considered, because it exceeds the screen size. The 'PanelSize' option also has no effect. I'm attaching the logfile for the oldest driver in your list. To me this looks like the problem might be somewhere else. Thanks, Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Linux Debian Current Operating System: Linux gloin 2.6.22-1-k7 #1 SMP Sun Jul 29 15:15:55 UTC 2007 i686 Build Date: 14 July 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Aug 21 09:27:42 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor SyncMaster (**) | |--Device nVidia Corporation NV37GL [Quadro PCI-E Series] (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81e50c0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1039,0761 card 1734,1099 rev 01 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1039,0004 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 1039,0965 card , rev 48 class 06,01,00 hdr 80 (II) PCI: 00:02:5: chip 1039,5513 card 1734,1095 rev 01 class 01,01,80 hdr 00 (II) PCI: 00:02:7: chip 1039,7012 card 1734,109c rev a0 class 04,01,00 hdr 00 (II) PCI: 00:03:0: chip 1039,7001 card 1734,1095 rev 0f class 0c,03,10 hdr 80 (II) PCI: 00:03:1: chip 1039,7001 card 1734,1095 rev 0f class 0c,03,10 hdr 00 (II) PCI: 00:03:2: chip 1039,7001 card 1734,1095 rev 0f class 0c,03,10 hdr 00 (II) PCI: 00:03:3: chip 1039,7002 card 1734,1095 rev 00 class 0c,03,20 hdr 00 (II) PCI: 00:05:0: chip 1039,0182 card 1734,1095 rev 01 class 01,01,8f hdr 00 (II) PCI: 00:06:0: chip 1039,000a card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:09:0: chip 10ec,8169 card 1734,1091 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:18:0: chip 1022,1100 card , rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:1: chip 1022,1101 card , rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:2: chip 1022,1102 card , rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:3: chip 1022,1103 card , rev 00 class 06,00,00 hdr 80 (II) PCI: 01:00:0: chip 10de,00fd card 10de,0215 rev a2 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000f (VGA_EN is set) (II) Bus 1 non
Bug#438850: xserver-xorg-video-nv: Unable to use native DFP resolution
(**) Configured Mouse: Buttons: 9 (**) Configured Mouse: Sensitivity: 1 (II) XINPUT: Adding extended input device Configured Mouse (type: MOUSE) (II) XINPUT: Adding extended input device Generic Keyboard (type: KEYBOARD) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Open ACPI successful (/var/run/acpid.socket) (II) Configured Mouse: ps2EnableDataReporting: succeeded -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (600, 'testing'), (200, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-1-k7 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-video-nv depends on: ii libc6 2.6-2 GNU C Library: Shared libraries ii xserver-xorg-core 2:1.3.0.0.dfsg-11 X.Org X server -- core server xserver-xorg-video-nv recommends no packages. -- no debconf information -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 signature.asc Description: Digital signature
Multithreaded OpenGL problem with unknown source (X11?, gcc4?, qt4?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! First, I'm not sure whether this is an appropriate message for this list. Please point me to a better place, if it is not. Some time ago I wrote a minimal example demonstrating the use of OpenGL's picking capabilities in combination with a QGLWidget where the actual rendering was performed in a separate thread (see http://apsy.gse.uni-magdeburg.de/main/index.php?page=hm_threadedcube (German language only). I simply combined an example of multithreaded OpenGL rendering in a QGLWidget from a Qt Quarterly article and another example for OpenGL picking. The source code ist here: http://apsy.gse.uni-magdeburg.de/main/files/src/threaded_cube.tar.gz This code worked (and works) great under Debian Sarge (XFree 4.3, Qt 3.3.4, gcc 3.3, i386). No warnings or errors. Recently I thought about porting this example to Qt 4 and check compatibility with gcc 4. So I tried compiling the code again. First on a system with the current Kubuntu release Breezy (Xorg 6.8.2, qt 3.4, gcc 4, i386). Compilation went fine (no errors or warnings. But starting the application results in a segfault. I tried the same (exactly the same code!) on the current Debian Etch (Xorg 6.8.2, Qt 3.3.4, gcc 4, AMD64). Linking produced a warning: - --- /usr/bin/ld: warning: libstdc++.so.5, needed by /usr/share/qt3/lib/libqt-mt.so, may conflict with libstdc++.so.6 - --- When starting the application the window appears (but grey) and then the app freezes. I had no idea where to continue. Somehow I believed the problem might be X11. Later I tried to port everything to Qt4. The result is here. http://apsy.gse.uni-magdeburg.de/main/files/src/threaded_cube-gcc4-qt4.tar.gz Compilation on the Breezy system (see above, but now with Qt 4.0.0) went fine (no warnings, no errors). But when starting the app it freezes as soon as the QApplication object is created. The behavior on the Etch-AMD64 system now with the current Qt4 version is exactly the same. I read something about freezes related to the XInitThreads() call. When I removed it (just to test) the app either crashed with segfault or Xlib: unexpected async reply. I guess that's why I included it. But it seems to causes problems now. Is this an X11 (or even Xorg) related problem at all? If so, is there some workaround for the XInitThreads() issue? Or am I doing something completely wrong? Please keep me CC'ed as I'm not subscribed to the list. Bye, Michael - -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDYKpK93+NsjFEvg8RAsqlAJ9mX4yIRW5BNXxrwRYSrJ49pAwA7QCfTyX2 oZNA8YOMPbx5N1ob0mMYpFg= =gM7e -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]