Bug#372077: Scary message on new installations
On Mon, Jul 03, 2006 at 10:03:25AM +0200, Wouter Verhelst wrote: On Sun, Jul 02, 2006 at 11:43:27PM -0700, Steve Langasek wrote: appropriate here than in other cases. Is there some concern about apt-listchanges not listing NEWS files for newly-installed packages? IME, it only lists NEWS.Debian files on upgrades... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372077: Scary message on new installations
On Sun, Jul 02, 2006 at 11:43:27PM -0700, Steve Langasek wrote: On Sat, Jul 01, 2006 at 04:53:56PM -0400, David Nusinow wrote: Right, but it might be a sufficient hint so that aptitude, and maybe apt, will do the right thing. This change *will* be sufficient to allow aptitude and apt to do the right thing *in a greater number of cases*. Just how large a coverage this will give, I can't say -- the only good way to find out is to try it and see what upgrade testers have to say about it. Ok... I'll lower the priority of the note to medium and add the xserver-xfree86 dummy package. Hopefully that'll be sufficient. As discussed elsewhere, I'd prefer to use NEWS.Debian, but it won't be shown to the user in this case, so a medium priority debconf abusing note should suffice. What do you mean, in this case? I don't see why NEWS.Debian is any less appropriate here than in other cases. Is there some concern about apt-listchanges not listing NEWS files for newly-installed packages? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372077: Scary message on new installations
On Mon, Jul 03, 2006 at 01:19:59PM -0400, David Nusinow wrote: On Mon, Jul 03, 2006 at 10:03:25AM +0200, Wouter Verhelst wrote: IME, it only lists NEWS.Debian files on upgrades... Mine as well. I had a ton of clueless users early on in the transition to 7.0 because I had documented things in NEWS.Debian, which they were never shown because the package was new. I don't want to go down that road again. - David Nusinow Now in #372077 also. hth gst -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Scary message on new installations
On Sat, Jul 01, 2006 at 12:06:16AM -0700, Steve Langasek wrote: On Fri, Jun 30, 2006 at 08:48:31AM -0400, David Nusinow wrote: Would putting back xserver-xfree86 as a transitional package suffice? Since I don't know how to reproduce this problem locally, my best guess is that the server gets removed due to the conflict with x11-common and then nothing is able to install the new one because xserver-xorg doesn't exist to be marked for upgrade. Putting back an empty xserver-xfree86 that pulls in xserver-xorg should suffice in this corner case, letting us remove the note all together. It is still valid for aptitude to remove xserver-xfree86, even as a transitional package, if the old version is conflicted with. There's nothing in our packaging system that lets you mark a particular package as not to be removed on upgrade. A dummy xserver-xfree86 package may fix this for most users, though. Bugreport #372077 has now this information also. I hope this helps, Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#286135: hardware info from the submitter
Hello X-server maintainers. Here hardware information from the bug submitter. [EMAIL PROTECTED]:~ $ cat /proc/cpuinfo processor : 0 cpu : 745/755 temperature : 15-17 C (uncalibrated) clock : 600MHz revision: 51.17 (pvr 0008 3311) bogomips: 1196.03 machine : PowerBook4,1 motherboard : PowerBook4,1 MacRISC2 MacRISC Power Macintosh board revision : 0003 detected as : 257 (iBook 2) pmac flags : 000b L2 cache: 256K unified memory : 640MB pmac-generation : NewWorld [EMAIL PROTECTED]:~ $ (lspci ; lspci -n ) | sort :00:0b.0 0600: 106b:0027 :00:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea AGP :00:10.0 0300: 1002:4c46 (rev 02) :00:10.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02) :10:0b.0 0600: 106b:0028 :10:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea PCI :10:17.0 ff00: 106b:0025 :10:17.0 ff00: Apple Computer Inc. KeyLargo/Pangea Mac I/O :10:18.0 0c03: 106b:0026 :10:18.0 USB Controller: Apple Computer Inc. KeyLargo/Pangea USB :10:19.0 0c03: 106b:0026 :10:19.0 USB Controller: Apple Computer Inc. KeyLargo/Pangea USB :20:0b.0 0600: 106b:0029 :20:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea Internal PCI :20:0e.0 0c00: 106b:0030 :20:0e.0 FireWire (IEEE 1394): Apple Computer Inc. UniNorth/Pangea FireWire :20:0f.0 0200: 106b:0024 :20:0f.0 Ethernet controller: Apple Computer Inc. UniNorth/Pangea GMAC (Sun GEM) [EMAIL PROTECTED]:~ $ lspci -vvs 0:10.0 :00:10.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02) (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Rage Mobility M3 AGP 2x Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 255 (2000ns min), Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 48 Region 0: Memory at 9400 (32-bit, prefetchable) [size=64M] Region 1: I/O ports at 802400 [size=256] Region 2: Memory at 9000 (32-bit, non-prefetchable) [size=16K] Expansion ROM at 9002 [disabled] [size=128K] Capabilities: available only to root [EMAIL PROTECTED]:~ $ lspci -nvvs 0:10.0 :00:10.0 0300: 1002:4c46 (rev 02) Subsystem: 1002:4c46 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 255 (2000ns min), Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 48 Region 0: Memory at 9400 (32-bit, prefetchable) [size=64M] Region 1: I/O ports at 802400 [size=256] Region 2: Memory at 9000 (32-bit, non-prefetchable) [size=16K] Expansion ROM at 9002 [disabled] [size=128K] Capabilities: available only to root [EMAIL PROTECTED]:~ $ Cheers Geert Stappers (next info is from the X-server) signature.asc Description: Digital signature
Bug#286135: x-server information
Hello, Attachment xserver information Cheers Geert This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to XFree86@XFree86.Org and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs). XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-6 20040709050738 [EMAIL PROTECTED]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.25-powerpc-smp ppc [ELF] Build Date: 09 July 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.25-powerpc ([EMAIL PROTECTED]) (version gcc 3.3.3 (Debian 20040401)) #1 mer avr 14 15:38:38 CEST 2004 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/XFree86.0.log, Time: Thu Jan 13 23:10:16 2005 (==) Using config file: /etc/X11/XF86Config-4 Skipping /usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_clip.o: No symbols found Skipping /usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_norm.o: No symbols found Skipping /usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_xform.o: No symbols found Skipping /usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_vertex.o: No symbols found Skipping /usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o: No symbols found Warning: font renderer for .pcf already registered at priority 0 Warning: font renderer for .pcf.Z already registered at priority 0 Warning: font renderer for .pcf.gz already registered at priority 0 Warning: font renderer for .snf already registered at priority 0 Warning: font renderer for .snf.Z already registered at priority 0 Warning: font renderer for .snf.gz already registered at priority 0 Warning: font renderer for .bdf already registered at priority 0 Warning: font renderer for .bdf.Z already registered at priority 0 Warning: font renderer for .bdf.gz already registered at priority 0 Warning: font renderer for .pmf already registered at priority 0 SESSION_MANAGER=local/bahrain:/tmp/.ICE-unix/6300 GetModeLine - scrn: 0 clock: 65000 GetModeLine - hdsp: 1024 hbeg: 1048 hend: 1184 httl: 1344 vdsp: 768 vbeg: 771 vend: 777 vttl: 806 flags: 10 *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] The application 'gnome-session' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. ICE default IO error handler doing an exit(), pid = 6314, errno = 0 The application 'gnome-panel' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. ICE default IO error handler doing an exit(), pid = 6353, errno = 0 The application 'nautilus' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. The application 'gnome-cups-icon' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. The application 'gnome-terminal' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. xinit: connection to X server lost.
Bug#286135: Are you sure it's not a mesa related bug?
On Thu, Jan 13, 2005 at 01:31:05PM -0300, Maximiliano Curia wrote: I tried setting the RADEON_NO_VTXFMT environment variable, as mentioned in #273651, and it worked. Try executing: RADEON_NO_VTXFMT=1 blender And hopefully this should work. There is also a mention of the LIBGL_ALWAYS_INDIRECT environment variable in that report too. You could try this if the other variable does not help you. LIBGL_DEBUG=1 LIBGL_ALWAYS_INDIRECT=1 RADEON_NO_VTXFMT=1 blender does also crash the X-server. I'm not sure if also did get the grey screen (blender background?) without any environment variable setting. So it could be an improvement. Cheers Geert Stappers signature.asc Description: Digital signature
