Bug#495483: xorg: Google Earth crashes X server
Julien Cristau wrote: > # might actually be a bug in libGLcore, but... > reassign 495483 xserver-xorg-video-nv > kthxbye > I don't know about the truncated backtrace but the DoSwapInterval error may be similar to #432950 on radeon (forwarded upstream at https://bugs.freedesktop.org/show_bug.cgi?id=11760) Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495483: xorg: Google Earth crashes X server
Another thing: Even though gdm respawns a new X server, something more profound breaks in the process of crashing. The new X server isn't stable anymore, for example using Ctrl-Alt-# to switch to a different VT leads to a crash most of the time. Might be related to the truncated backtrace output. Is there anything in the gdm log (it should get the stderr output from the x server)? It's the same as Xorg.log: a line "Backtrace:" and then nothing. (cf. attachment) X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-3) Current Operating System: Linux jake 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64 Build Date: 02 August 2008 10:07:22PM 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: Mon Aug 18 01:28:08 2008 (==) Using config file: "/etc/X11/xorg.conf" (II) Module "i2c" already built-in (II) Module "ddc" already built-in (II) Module "ramdac" already built-in The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Error:Section defined without a name > Definition ignored > Error:Section defined without a name > Definition ignored > Error:Section defined without a name > Definition ignored > Error:Section defined without a name > Definition ignored > Warning: Multiple doodads named "" > Using first definition > Warning: Multiple doodads named "" > Using first definition > Warning: Multiple doodads named "" > Using first definition > Warning: Multiple doodads named "" > Using first definition > Warning: Multiple doodads named "" > Using first definition > Warning: Multiple doodads named "" > Using first definition Errors from xkbcomp are not fatal to the X server (EE) Error compiling keymap (server-0) (EE) XKB: Couldn't compile keymap The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server (EE) DoSwapInterval: cx = 0x2dd7370, GLX screen = 0x2578770 Backtrace:
Processed: Re: Bug#495483: xorg: Google Earth crashes X server
Processing commands for [EMAIL PROTECTED]: > # might actually be a bug in libGLcore, but... > reassign 495483 xserver-xorg-video-nv Bug#495483: xorg: Google Earth crashes X server Bug reassigned from package `xorg' to `xserver-xorg-video-nv'. > kthxbye 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#495483: xorg: Google Earth crashes X server
# might actually be a bug in libGLcore, but... reassign 495483 xserver-xorg-video-nv kthxbye On Mon, Aug 18, 2008 at 01:53:24 +0200, Thiemo Nagel wrote: >> First thing to do would be to actually attach Xorg.0.log to this bug. > > Sure. Thanks. > Another thing: Even though gdm respawns a new X server, something more > profound breaks in the process of crashing. The new X server isn't > stable anymore, for example using Ctrl-Alt-# to switch to a different VT > leads to a crash most of the time. > Might be related to the truncated backtrace output. Is there anything in the gdm log (it should get the stderr output from the x server)? Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495367: xserver-xorg-video-radeon: Radeon and RadeonHD drivers do not allow 2560x1600
franck wrote: > Package: xserver-xorg-video-radeon > Version: 1:6.9.0-1+lenny2 > Severity: normal > > > Sat 16 Aug 2008 18:52 CEST > > Radeon and RadeonHD drivers do not allow 2560x1600 > > Hi Folks, > > I am the lucky owner of a dell 3008WFP which has a native resolution of > 2560x1600. > However my Radeon 3450 (RV620LE) does not allow more than 1920x1440 :-(. > Trying to go to higher resolutions leads to a blank (black) screen. > Can you try to build the upstream git ? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495315: marked as done (compiz: Black band on screen-right with rv200)
Your message dated Mon, 18 Aug 2008 00:12:02 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#495315: compiz: Black band on screen-right with rv200 has caused the Debian Bug report #495315, regarding compiz: Black band on screen-right with rv200 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.) -- 495315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495315 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: compiz Version: 0.7.6-5 Severity: normal When compiz is started on my rv200, at 1400x1050x32, the right side of the screen has a black, unusable area. When gdm is restarted, this problem disappears and compiz can run normally till the system is rebooted. When compiz is starting on the first X server run after boot, 'glxinfo -l | grep GL_MAX_TEXTURE_SIZE' returns 1024. After gdm has been restarted once, that line returns 2048. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages compiz depends on: ii compiz-core 0.7.6-5OpenGL window and compositing mana ii compiz-gnome 0.7.6-5OpenGL window and compositing mana ii compiz-gtk0.7.6-5OpenGL window and compositing mana ii compiz-plugins0.7.6-5OpenGL window and compositing mana compiz recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- reassign 495315 libgl1-mesa-dri found 495315 7.0.3-1 fixed 495315 7.0.3-5 thank you Marking as fixed in 7.0.3-5 as explained earlier. Brice --- End Message ---
Processed: Re: Bug#495315: compiz: Black band on screen-right with rv200
Processing commands for [EMAIL PROTECTED]: > reassign 495315 libgl1-mesa-dri Bug#495315: compiz: Black band on screen-right with rv200 Bug reassigned from package `compiz' to `libgl1-mesa-dri'. > found 495315 7.0.3-1 Bug#495315: compiz: Black band on screen-right with rv200 Bug marked as found in version 7.0.3-1. > fixed 495315 7.0.3-5 Bug#495315: compiz: Black band on screen-right with rv200 Bug marked as fixed in version 7.0.3-5. > thank you 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]
Processed: forcibly merging 372692 495264
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > forcemerge 372692 495264 Bug#372692: xserver-xorg-input-synaptics: doesn't load options from xorg.conf Bug#495264: xserver-xorg-input-synaptics: synaptics doesn't load settings at X startup Forcibly Merged 372692 495264. > 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#495483: xorg: Google Earth crashes X server
On Sun, Aug 17, 2008 at 22:09:22 +0200, Thiemo Nagel wrote: > Starting google-earth (v4.3.7284.3916, downloaded today) displays a splash > screen and then crashes X. > > Graphics card is: 05:00.0 VGA compatible controller: nVidia Corporation NV44 > [GeForce 6200 LE] (rev a1) > > It seems that something wanted to create a backtrace as the word "Backtrace:" > is the last thing > to be found in /var/log/Xorg.0.log, but that attempt seems to have failed. > > I'm willing to investigate further if I get a little guidance. > First thing to do would be to actually attach Xorg.0.log to this bug. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495483: xorg: Google Earth crashes X server
Package: xorg Version: 1:7.3+15 Severity: normal Starting google-earth (v4.3.7284.3916, downloaded today) displays a splash screen and then crashes X. Graphics card is: 05:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 LE] (rev a1) It seems that something wanted to create a backtrace as the word "Backtrace:" is the last thing to be found in /var/log/Xorg.0.log, but that attempt seems to have failed. I'm willing to investigate further if I get a little guidance. Kind regards, Thiemo Nagel -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') 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/bash Versions of packages xorg depends on: ii gnome-terminal [x-termi 2.22.3-2 The GNOME 2 terminal emulator appl ii konsole [x-terminal-emu 4:3.5.9.dfsg.1-5 X terminal emulator for KDE ii libgl1-mesa-glx [libgl1 7.0.3-5 A free implementation of the OpenG ii libglu1-mesa7.0.3-5 The OpenGL utility library (GLU) ii x11-apps7.3+3X applications ii x11-session-utils 7.3+1X session utilities ii x11-utils 7.3+2X11 utilities ii x11-xfs-utils 7.3+1X font server utilities ii x11-xkb-utils 7.4+1X11 XKB utilities ii x11-xserver-utils 7.3+4X server utilities ii xauth 1:1.0.3-2X authentication utility ii xfonts-100dpi 1:1.0.0-4100 dpi fonts for X ii xfonts-75dpi1:1.0.0-475 dpi fonts for X ii xfonts-base 1:1.0.0-5standard fonts for X ii xfonts-scalable 1:1.0.0-6scalable fonts for X ii xfonts-utils1:7.4+1 X Window System font utility progr ii xinit 1.0.9-2 X server initialisation tool ii xkb-data1.3-2X Keyboard Extension (XKB) configu ii xserver-xorg1:7.3+15 the X.Org X server ii xterm [x-terminal-emula 235-1X terminal emulator Versions of packages xorg recommends: ii xorg-docs 1:1.4-2Miscellaneous documentation for th xorg suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492919: 40custom_load-xmodmap in Xsession(5) example does not work
* Renato S. Yamane <[EMAIL PROTECTED]> [080817 19:39]: > Hardware: Lenovo Thinkpad T61 > > $ cat ~/.Xmodmap > keycode 109 = slash question > keycode 176 = XF86AudioRaiseVolume > keycode 174 = XF86AudioLowerVolume > keycode 160 = XF86AudioMute > keycode 164 = XF86AudioStop > keycode 162 = XF86AudioPlay > keycode 153 = XF86AudioNext > keycode 144 = XF86AudioPrev I think instead of using .Xmodmap you'd have better chances to use the "thinkpad60" model. (i.e. try thinkpad60 instead of pc104 (or pc105) in your xorg.conf) Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492919: 40custom_load-xmodmap in Xsession(5) example does not work
On Sun, Aug 17, 2008 at 14:06:54 -0300, Renato S. Yamane wrote: > I wating for this fix too, because essential keys don't work to me (as slash > and question keys)! > What are your xkb settings? Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492919: 40custom_load-xmodmap in Xsession(5) example does not work
On Sun, Aug 17, 2008 at 14:19:50 +0300, Peter Eisentraut wrote: > On Wednesday 30 July 2008 09:12:28 Julien Cristau wrote: > > On Tue, Jul 29, 2008 at 23:49:02 +0300, Peter Eisentraut wrote: > > > Is this example obsolete? Is there something else that might mess up the > > > keyboard configuration? Any clue? Thanks. > > > > Yes, that's a bug in the X server. As I understand it, running xmodmap > > before pressing any key modifies the virtual core keyboard map, which is > > overwritten on first key press by the settings for the actual keyboard > > device. > > Hmm, is somone working on a fix for this? Is there some other way to > customize the keyboard under X? I looked into HAL, but that appears to > operate on a different level. > There's a potential fix upstream, but I'm not sure it fixes this exact issue, and don't feel comfortable backporting it to 1.4. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492919: 40custom_load-xmodmap in Xsession(5) example does not work
I wating for this fix too, because essential keys don't work to me (as slash and question keys)! Hardware: Lenovo Thinkpad T61 $ cat ~/.Xmodmap keycode 109 = slash question keycode 176 = XF86AudioRaiseVolume keycode 174 = XF86AudioLowerVolume keycode 160 = XF86AudioMute keycode 164 = XF86AudioStop keycode 162 = XF86AudioPlay keycode 153 = XF86AudioNext keycode 144 = XF86AudioPrev Best regards, Renato S. Yamane -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495435: xterm: Window resize race condition
On Sun, Aug 17, 2008 at 09:41:39PM +0600, Alexander E. Patrakov wrote: > Looks exactly like this kernel problem: http://lkml.org/lkml/2008/8/11/538 - > please confirm my testing under different kernel versions My kernel version is older (2.6.15). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpjl3kksVC4R.pgp Description: PGP signature
xkeyboard-config 1.3-2 MIGRATED to testing
FYI: The status of the xkeyboard-config source package in Debian's testing distribution has changed. Previous version: 1.3-1 Current version: 1.3-2 -- This email is automatically generated; the Debian Release Team <[EMAIL PROTECTED]> is responsible. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#490912: VMMouse still results in mouse 'stuck' at bottom right
I still the described behavior with xserver-xorg-core 2:1.4.2-3 xserver-xorg-input-vmmouse 1:12.5.1-2 If I can provide any further information, please let me know. Ken Causey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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#495435: xterm: Window resize race condition
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. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpQa4KjDuuW9.pgp Description: PGP signature
Bug#175907: BREAKING news
Guy With Big Giant Head Laments Lifetime Of Presumed Super Brilliance http://martinharinger.xf.cz/1.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#478880: No, it's not fixed upstream
On Sun, 17 Aug 2008 09:35:43 +0200 Brice Goglin wrote: [...] > Now, it should be fixed in 7.1rc3 accordingly to the upstream bugs. > So I am marking as fixed in experimental. Thanks for your help and assistance! I will probably be able to test mesa from experimental in a couple of weeks (I hope I manage to find the time to do so...). -- http://frx.netsons.org/doc/index.html#nanodocs The nano-document series is here! . Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4 pgpb95rrhQJKO.pgp Description: PGP signature
Bug#135692: BREAKING news
Top 11 Signs Steve Jobs Is Dead http://masekl.wz.cz/1.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495435: xterm: Window resize race condition
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?) When I manually send another SIGWINCH to the program it resizes to the correct current xterm size. - -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (, 'testing'), (990, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.27-rc3 (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xterm depends on: ii libc6 2.7-13 GNU C Library: Shared libraries ii libfontconfig12.6.0-1generic font configuration library ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libncurses5 5.6+20080713-1 shared libraries for terminal hand ii libsm62:1.0.3-2 X11 Session Management library ii libx11-6 2:1.1.4-2 X11 client-side library ii libxaw7 2:1.0.4-2 X11 Athena Widget library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxft2 2.1.12-3 FreeType-based font drawing librar ii libxmu6 2:1.0.4-1 X11 miscellaneous utility library ii libxt61:1.0.5-3 X11 toolkit intrinsics library ii xbitmaps 1.0.1-2Base X bitmaps Versions of packages xterm recommends: ii x11-utils 7.3+2 X11 utilities ii xutils1:7.3+15 X Window System utility programs m Versions of packages xterm suggests: pn xfonts-cyrillic(no description available) - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFIqBUFzQZOfTz8JZwRAspLAKCfPR4e1EJvqTUfyAszBTMcfvOfWwCfULEi 0mFQE6JPlXZVnvl8LtMH7Ak= =me7G -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492919: 40custom_load-xmodmap in Xsession(5) example does not work
On Wednesday 30 July 2008 09:12:28 Julien Cristau wrote: > On Tue, Jul 29, 2008 at 23:49:02 +0300, Peter Eisentraut wrote: > > Is this example obsolete? Is there something else that might mess up the > > keyboard configuration? Any clue? Thanks. > > Yes, that's a bug in the X server. As I understand it, running xmodmap > before pressing any key modifies the virtual core keyboard map, which is > overwritten on first key press by the settings for the actual keyboard > device. Hmm, is somone working on a fix for this? Is there some other way to customize the keyboard under X? I looked into HAL, but that appears to operate on a different level. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#431326: #431326: This bug has probably never been fixed
Brice Goglin wrote: > The patch has been committed in the upstream git repo on the master and > 2.4 branch, so you can test it by building according to: > http://bgoglin.livejournal.com/10936.html > Make sure you use the 'xf86-video-intel-2.4-branch' branch since > the master branch won't compile for you. > > Brice Ok I followed the instructions at that page, and managed to build the driver and test it. I still get the same error and X does not start. Here is the xinit output : -- X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-3) Current Operating System: Linux zeus 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686 Build Date: 02 August 2008 11:27:26PM 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: Sun Aug 17 11:48:46 2008 (==) Using config file: "/etc/X11/xorg.conf" (II) Module "ddc" already built-in (II) Module "i2c" already built-in (EE) intel(0): sil164 not detected got 5: from DVOI2C_E Slave 112. (EE) intel(0): tfp410 not detected got VID 1305: from DVOI2C_E Slave 112. (EE) intel(0): No valid modes. (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found waiting for X server to begin accepting connections giving up. xinit: Connection reset by peer (errno 104): unable to connect to X server xinit: No such process (errno 3): Server error. And the full Xorg.0.log is attached. Almacha X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-3) Current Operating System: Linux zeus 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686 Build Date: 02 August 2008 11:27:26PM 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: Sun Aug 17 11:48:46 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) |-->Input Device "Configured Mouse" (==) |-->Input Device "Generic Keyboard" (==) The core pointer device wasn't specified explicitly in the layout. Using the first mouse device. (==) The core keyboard device wasn't specified explicitly in the layout. Using the first keyboard device. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (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: 0x81e3ca0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 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.4.2, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,3575 card 10cf,113b rev 04 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,3577 card 10cf,113c rev 04 class 03,00,00 hdr 80 (II) PCI: 00:02:1: chip 8086,3577 card 10cf,113c rev 00 class 03,80,00 hdr 80 (II) PCI: 00:1d:0: chip 8086,2482 card 10cf,113d rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2484 card 10cf,113d rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev 42 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,248c card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,248a card 10cf,113d rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,2483 card 10cf,113d rev 02 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2485 card 10cf,1177 rev 02 class 04,01,00 hdr 00 (II) P
Bug#431326: #431326: This bug has probably never been fixed
On Tue, Aug 05, 2008 at 11:15:20PM +0200, Raphael Champeimont (Almacha) wrote: > Julien Cristau wrote: > > On Tue, Aug 5, 2008 at 23:01:12 +0200, Raphael Champeimont (Almacha) wrote: > > > >> In fact I have no experience at all in the debian way of building > >> packages. Should I apply this patch to the debian source package > >> xserver-xorg-video-intel from lenny ? from sid ? Or should I apply it to > >> the debian xorg source package ? Or should I download the original > >> X11R7.3 source from X.org and apply the patch to it? > > > > I'll try to build some packages with that patch so you could test them, > > I guess that would be easiest. > > > > Ok, thanks :-) The patch has been committed in the upstream git repo on the master and 2.4 branch, so you can test it by building according to: http://bgoglin.livejournal.com/10936.html Make sure you use the 'xf86-video-intel-2.4-branch' branch since the master branch won't compile for you. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#478880: marked as done (mayavi2: Opacity == 1.0, but still slightly transparent)
Your message dated Sun, 17 Aug 2008 09:35:43 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: No, it's not fixed upstream has caused the Debian Bug report #478880, regarding mayavi2: Opacity == 1.0, but still slightly transparent 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.) -- 478880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478880 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: mayavi2 Version: 2.1.1-2 Severity: normal Hi! I noticed a little problem in opacity management. Please note that I've recently upgraded mayavi2 from version 2.1.1-2 to version 2.1.1-2+b1, but I've seen the same issue with version 2.1.1-2. Let's consider (one more time!) the test case I prepared for bug #400406 (see [1] and [2]). [1] http://bugs.debian.org/400406 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi/vtk-multiblockPLOT3D-bug-test.tar.gz?bug=400406;msg=5;att=1 $ tar xvzf vtk-multiblockPLOT3D-bug-test.tar.gz $ ls gen_tinyplot3d.f tiny.qvtk-multiblockPLOT3D-bug-test.tar.gz list_plot3d.pytiny.xyz $ mayavi2 The main window shows up. * from menus, select File -> Load data -> PLOT3D file * as XYZ Co-ordinate file, select `tiny.xyz' * as Q Solution file, select `tiny.q' * select PLOT3D:tiny.xyz, tiny.q in the MayaVi pane * in the PLOT3DReader tab (inside the object editor), check "Binary file", "Do not reduce number of outputs", "Has byte count", and "Multi grid"; *un*check "Force read", "I blanking", and "Two dimensional geometry"; select "little_endian" Byte order * in the Reader tab, click on the "Update Reader" button * from menus, select Visualize -> Modules -> Surface (a blue square shows up in the TVTK scene) * rotate the TVTK scene (by moving the mouse with the left button pressed) I should only see at most three cube faces (if perspective theory is my friend...). Nonetheless, I can also see the remaining faces, behind the directly visible ones. Let me check the opacity settings: * in the MayaVi pane, double-click on Surface Mmmmh, Opacity is set to 1.0. Hence I should only see directly visible faces. Yet, I seem to have Superman X-ray view! ;-) Saving the scene to a PNG image, shows that the problem will affect visualization outputs, as well. It really seems I'm getting (partial) transparency, even when I do _not_ want it... :-( I think this is bug. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-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/bash Versions of packages mayavi2 depends on: ii libc62.7-10 GNU C Library: Shared libraries ii python 2.5.2-1 An interactive high-level object-o ii python-central 0.6.6 register and build utility for Pyt ii python-enthought-traits 2.0.4-2 Manifest typing and reactive progr ii python-enthought-traits-ui 2.0.4-2 User interface related modules for ii python-numpy 1:1.0.4-7 Numerical Python adds a fast array ii python-pkg-resources 0.6c8-3 Package Discovery and Resource Acc ii python-vtk 5.0.4-1+b1 Python bindings for VTK ii python-wxgtk2.6 2.6.3.2.2-2 wxWidgets Cross-platform C++ GUI t ii python2.52.5.2-3 An interactive high-level object-o mayavi2 recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 7.1~rc3-1 On Wed, Jun 18, 2008 at 12:03:09AM +0200, Francesco Poli wrote: > tag 478880 - fixed-upstream > thanks > > Rationale: this bug has been forwarded to > http://bugs.freedesktop.org/show_bug.cgi?id=16363 > which has been closed as duplicate of id=16072, but the latter is still > open. > As a consequence, bug #478880 is not yet fixed by upstream. Now, it should be fixed in 7.1rc3 accordingly to the upstream bugs. So I am marking as fixed in experimental. Brice --- End Message ---
