Re: problem mounting a floppy disk
On Wed, Sep 07, 2005 at 11:45:57PM -0300, Roberto Fabbrin wrote: i just move to debian, like couple weeks ago, i just can't mount a simple floppy, because there is no /dev/fd0, i wish someone could help me. Thanks, Roberto. Hi roberto, ... Please try debian-user@lists.debian.org, as your question is highly off-topic here, debian-x is the X windows related mailing list. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318660: Provides: libgl1 virtual package?
Package: nvidia-glx Version: 1.0.7676-1 Followup-For: Bug #318660 nvidia-glx (non-free) has a strage header: $ dpkg -I /var/cache/apt/archives/nvidia-glx_1.0.7676-1_i386.deb Conflicts: nvidia-glx-src Replaces: nvidia-glx-src Provides: xserver nvidia-glx does NOT provide an xserver itself, it only provides a new module/driver. Here's a list of all packages providing xserver: $ grep-available -F Provides xserver -s Package Package: vncserver Package: xserver-xorg Package: nvidia-glx Package: xserver-xorg-dbg Package: tightvncserver It instead provides an alternative libgl1: $ dpkg -c nvidia-glx_1.0.7676-1_i386.deb ... -rw-r--r-- root/root515012 2005-09-07 22:30:01 ./usr/lib/libGL.so.1.0.7676 lrwxrwxrwx root/root 0 2005-09-07 22:30:00 ./usr/lib/libGL.so.1 - libGL.so.1.0.7676 ... libgl1 is also provided by the following packages: $ grep-available -F Provides libgl1 -s Package Package: xlibmesa-gl Package: mesag3 Package: libgl1-mesa-glide3 There's also nvidia-glx and libgl1-mesa-dri according to http://packages.debian.org/cgi-bin/search_contents.pl?word=libGL.so.1searchmode=searchfilescase=sensitiveversion=unstablearch=i386 $ apt-cache show xlibmesa-gl mesag3 libgl1-mesa-glide3 libgl1-mesa-dri nvidia-glx|grep ^[PRC] Package: xlibmesa-gl Replaces: libgl1, libutahglx1, xlibmesa3 ( 4.2.1-5), xlibmesa3-gl Provides: libgl1 Conflicts: libgl1, libutahglx1, xlibmesa3 ( 4.2.1-5), xlibmesa3-gl Package: mesag3 Replaces: libgl1 Provides: libgl1 Conflicts: mesag3-glide, mesag3-glide2, mesag3+ggi, libgl1, nvidia-glx Package: libgl1-mesa-glide3 Replaces: mesag3, libgl1 Provides: mesag3, libgl1 Conflicts: mesag3-glide, mesag3, mesag3+ggi, libgl1, nvidia-glx Package: libgl1-mesa-dri Package: nvidia-glx Should libgl1 be a virtual package? Dependent on that, should the headers of nvidia-glx should look like: Conflicts: nvidia-glx-src, libgl1 Replaces: nvidia-glx-src, libgl1 Provides: libgl1 Similar for libgl1-mesa-dri: Conflicts: libgl1 Replaces: libgl1 Provides: libgl1 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (989, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-walker Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327179: replace i830 with i915 in xorg.conf upon upgrading.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: xserver-xorg Version: 6.8.2.dfsg.1-6 Severity: wishlist I guess this'd be nice, Maybe when etch is released and people do a dist-upgrade. Not sure. Best wishes, - -- - - -- Katoob Main Developer, Arabbix Maintainer. GNU/Linux registered user #224950 Proud Egyptian GNU/Linux User Group www.eglug.org Admin. Life powered by Debian, Homepage: www.foolab.org - -- Don't send me any attachment in Micro$oft (.DOC, .PPT) format please Read http://www.gnu.org/philosophy/no-word-attachments.html Preferable attachments: .PDF, .HTML, .TXT Thanx for adding this text to Your signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDH+5ny2aOKaP9DfcRAtPbAKCMDPo/H8+ocq7Ei5f0ABKqPxdClQCgi0XA Cph5ZKWEBhHrmnnJR1XzU5M= =TzsE -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bug administratif... (administrativ bug found...)
On Thu, Sep 08, 2005 at 01:52:47AM -0500, Branden Robinson / Debian Project Leader wrote: On Fri, Sep 02, 2005 at 12:39:16AM -0500, kristian david wrote: Hi =o) I'm administratively a NONAME guy (homeless because of a Microcephaleous Gates that is a kind of New-Digital-Nazi of the world... with his friend Ballmy-the-monkey-dancer), and I love realy this new Sarge release of your Debian, but I've found a real BAD BIG BUG... I tryed many time to install alternatively Debian/Sarge and Ubuntu Hoary (based on your Debian) In facts: I install Debian on a iMac/G3, and try... (only in mode console X11 does'nt work), and I trash all and install Ubuntu Hoary on the same Hardware (only the Network is not detected), and i re-trash all (because I use Ubuntu just to understand how X11 is configured... LOL), and i re-re-trash all Ubuntu, and re-install Debian etc... and so on (ad lib) (like a Whitehouse lyrics - Peter Sotos, Philip Best, and William Bennet...) So, I've finally found the BUG... Ubuntu recognize all my iMac G3 except the Network, but easy to fix with GNOME/interface... and your EXCELLENT Debian (I mean it) dont recognize my Hardware (specialy the screen ATY Rage 128MB...) but Network is good, and all the Server Parts (applications) are OK... So the bug is ADMINISTRATIVE: WHY, You dont collaborate between the staff of Ubuntu (and reciprocally) to complete the EXCELLENT Debian i love so ? That's a big question. A old man, homeless (this is true) in french we tell a man like me: Un Clochard or Un Clodo in a familiar way... best regards, and apologize for my bad english. (i'm in the french part of Switzerland) Realy I love your system !!! I mean it. Thank you very much for your positive feedback and reasoned criticism. The simple fact is that Ubuntu and Debian do tend to cooperate closely on most technical issues. But each distribution does some things better than the other, as is generally true when comparing any two GNU/Linux distributions. The Debian Sarge release uses a program called discover1 to discern what hardware is on the system, so I would encourage you to file a bug report against that package describing your problem. Ubuntu and Debian both use the same installer (debian-installer), which in turn uses discover1, so I am not sure why your hardware was detected on one but not the other. Perhaps Ubuntu has made additions to the discover hardware database (in the discover-data package) that they haven't contributed back yet, or which Debian did not get included in the package in time for a sarge release. Hi Branden, ... I think from past experience, that this has nothing to do with the installer, since the only time the graphic card is of interest is during the xfree86 configuration, and i have had similar experience with the ati wrapper not recognizing my radeon 9200SE cards due to them matching the second head. I don't rememebr the bug report about this out of hand, but it is over a year old or so, and was never fixed. It is well possible that a similar detection problem is present in the XFree86 package, and the fact that it works fine in ubuntu is probably due to them using X.org, where this bug is absent. So, the bug is an xfree86 bug, and thus CCing debian-x. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327099: Xserver-xorg radeon dual head monitor detection problem
Michel Dänzer wrote: merge 327098 327099 thanks Sorry about that On Wed, 2005-09-07 at 18:08 +0200, Jan Nielsen wrote: Package: xserver-xorg Version: 6.8.2.dfsg.1-6 Upgrading from XFree86 to Xorg broke my dual head xinerama setup. This same setup worked perfectly well with XFree86 4.3 [...] The following is the relevant info from Xorg.0.log: It isn't always immediately obvious which parts are relevant. Please consider using the reportbug tool, which will include pretty much all the information that could be relevant. Well, if there was something you were missing to diagnose the problem I apologize. However, it seems to me that you understood it pretty well anyway based on the response below. (II) RADEON(0): Primary: Monitor -- CRT Connector -- VGA DAC Type -- Primary TMDS Type -- NONE DDC Type -- VGA_DDC (II) RADEON(0): Secondary: Monitor -- NONE Connector -- DVI-I DAC Type -- TVDAC/ExtDAC TMDS Type -- Internal DDC Type -- DVI_DDC ... (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled ... (WW) RADEON(1): Only one monitor detected, Second screen will NOT be created FWIW, you should be able to work around this using something like Option MonitorLayout CRT,CRT See the radeon(4x) manpage. Doesn't work. I have tried all possible combinations of CRT, TDMS and LDVS and none of them works. I have two Benq FP731 LCD monitors. Jan
Re: Processing of xorg-x11_6.9.0.dfsg.1-0pre1+SVN_i386.changes and powerpc build error.
On Wed, Sep 07, 2005 at 05:51:41PM +0200, Sven Luther wrote: On Wed, Sep 07, 2005 at 11:25:55AM -0400, David Nusinow wrote: On Wed, Sep 07, 2005 at 08:01:59AM -0700, Archive Administrator wrote: xorg-x11_6.9.0.dfsg.1-0pre1+SVN_i386.changes uploaded successfully to localhost Grr... my first upload got processed before I had time to upload the .orig.tar.gz. I re-uploaded just now, but that got rejected as well, saying that the .orig.tar.gz is still missing, even though it's in the uploadqueue. I already replied to that mail asking for help, but if anyone has any clues as to what's going on, it'd be much appreciated. Just upload the .orig.tar.gz by hand ? It it already accepted, or only in the incoming queue ? If the later is the case, you can erase it with dcut for example. I think the best thing is to ask the ftp-masters to reject the upload, and make another one. On a side note, in my quest for powerpc builds, i was now hit by that : make[6]: Leaving directory `/extra/sven/debian/xorg-6.9/xorg-x11-6.9.0.dfsg.1/build-tree/xc/programs/Xserver/hw/dmx' gcc -o Xorg -g -O2 -fno-strict-aliasing -L../../exports/lib xkb/xf86KillSrv.o xkb/xf86VT.o xkb/xf86Private.o ../../programs/Xserver/hw/xfree86/common/xf86Init.o ../../programs/Xserver/hw/xfree86/common/xf86IniExt.o ../../programs/Xserver/hw/xfree86/common/libxf86.a ../../programs/Xserver/hw/xfree86/parser/libxf86config.a ../../programs/Xserver/hw/xfree86/os-support/libxf86_os.a ../../programs/Xserver/hw/xfree86/loader/libloader.a ../../programs/Xserver/hw/xfree86/common/libxf86.a dix/libdix.a os/libos.a ../../lib/font/fontbase.o ../../lib/font/libfontbase.a Xext/libexts.a xkb/libxkb.a os/libos.a Xi/libxinput.a lbx/liblbx.a ../../lib/lbxutil/liblbxutil.a ../../programs/Xserver/hw/xfree86/common/libxf86.a composite/libcomposite.a damageext/libdamage.a miext/damage/libdamage.a xfixes/libxfixes.a miext/cw/libcw.a Xext/libexts.a xkb/libxkb.a os/libos.a Xi/libxinput.a lbx/liblbx.a ../../lib/lbxutil/liblbxutil.a randr/librandr.a render/librender.a dix/libxpstubs.a mi/libmi.a composite/libcomposite.a damageext/libdamage.a miext/damage/libdamage.a xfixes/libxfixes.a miext/cw/libcw.a Xext/libexts.a xkb/libxkb.a os/libos.a Xi/libxinput.a lbx/liblbx.a ../../lib/lbxutil/liblbxutil.a randr/librandr.a render/librender.a ../../programs/Xserver/hw/xfree86/os-support/libxf86_os.a -lz -lm -lXau -lXdmcp -rdynamic -ldl -Wl,-rpath-link,../../exports/lib /usr/bin/ld: ../../programs/Xserver/hw/xfree86/common/libxf86.a(xf86DoProbe.o): unknown relocation type 225 for symbol xf86DriverList /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status Any ideas ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X Strike Force X.Org X11 SVN commit: r595 - trunk/debian
Author: ender Date: 2005-09-08 04:28:22 -0500 (Thu, 08 Sep 2005) New Revision: 595 Modified: trunk/debian/control Log: A typo remained from the thinko by =. Modified: trunk/debian/control === --- trunk/debian/control2005-09-07 21:48:43 UTC (rev 594) +++ trunk/debian/control2005-09-08 09:28:22 UTC (rev 595) @@ -290,7 +290,7 @@ # cpp-3.3 ( 1:3.3.3-0pre1) # Previous versions of cpp 3.3 had broken support for the -traditional # flag. -# linux-kernel-headers ( 2.6.13+0rc3-1.1) +# linux-kernel-headers (= 2.6.13+0rc3-1.1) # Previous versions had a busted joystick.h file (see Debian #320515). Package: lbxproxy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318413: xlibs: Backslash Key is broken on Japanese Keyboards
Hi, Just to report that I also suffer from this bug on my Hitachi Prius laptop under xfree86 (but not under xorg; however I cannot get the 1200x800 mode working under xorg - I need to use 855resolution to get it working under xfree86, but I digress). The patch posted above (to /etc/X11/xkb/symbols/pc/jp) does not fix the bug for me; however, the patch (to /etc/X11/xkb/keycodes/xfree86) posted at http://www.vergenet.net/~horms/ does fix the problem. Cheers Tim Tim Gershon http://belle.kek.jp/~gershon/contact.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327000: Regression: suspend with radeon doesn't work any more
Hi, Did you upgrade from -5 to -6? There shouldn't have been anything that touched this sort of thing between those two revisions. I'm pretty sure I had -5 running before that. I tried downgrading the xserver-xorg package, but that didn't help. Any of the lib packages I could try? I have the impression that it is maybe related to the xscreensaver or opengl. But that might be just a timing coincidence. best regards, Erich Schubert -- erich@(vitavonni.de|debian.org)--GPG Key ID: 4B3A135C(o_ There was never a good war or a bad peace. - Benjamin Franklin//\ Wenn zwei gute Freunde sind, die einander kennen, Sonn' und Mond V_/_ begegnen sich, ehe sie sich trennen. --- Clemens von Brentano -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327179: replace i830 with i915 in xorg.conf upon upgrading.
On Thu, 2005-09-08 at 10:55 +0300, Mohammed Sameer wrote: [please replace i830 with i915 in xorg.conf] Where? Why? It's not even listed in xorg.conf anywhere. The DDX driver is i810. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bug administratif... (administrativ bug found...)
On Thu, 2005-09-08 at 10:22 +0200, Sven Luther wrote:
On Thu, Sep 08, 2005 at 01:52:47AM -0500, Branden Robinson / Debian Project
Leader wrote:
The Debian Sarge release uses a program called discover1 to discern what
hardware is on the system, so I would encourage you to file a bug report
against that package describing your problem.
Ubuntu and Debian both use the same installer (debian-installer), which in
turn uses discover1, so I am not sure why your hardware was detected on one
but not the other. Perhaps Ubuntu has made additions to the discover
hardware database (in the discover-data package) that they haven't
contributed back yet, or which Debian did not get included in the package
in time for a sarge release.
debian-installer does not use any version of discover in any way, shape
or form. Perhaps you were thinking of hotplug?
In any case, the maintainer scripts, which you authored originally
(xserver-xorg.{config,postinst}), do call discover if they can. In
Ubuntu's case, they call discover1, which uses the dataset from
discover1-data (as distinct from discover-data, which is only used by
version 2 of discover -- which is not used in either Ubuntu or Debian by
default, to my knowledge). Ubuntu's version of discover1-data has
indeed been pretty heavily augmented to properly deal with new video
cards. But the original database was reasonably solid as regards old
entries, so we haven't really changed anything there.
I think you've sent the submitter chasing a red herring on this one.
I think from past experience, that this has nothing to do with the installer,
since the only time the graphic card is of interest is during the xfree86
configuration, and i have had similar experience with the ati wrapper not
recognizing my radeon 9200SE cards due to them matching the second head. I
don't rememebr the bug report about this out of hand, but it is over a year
old or so, and was never fixed.
It is well possible that a similar detection problem is present in the XFree86
package, and the fact that it works fine in ubuntu is probably due to them
using X.org, where this bug is absent.
So, the bug is an xfree86 bug, and thus CCing debian-x.
Yes, Sven is mostly right here.
If you're using a Mach64/atimisc card, then there are no problems with
the ati module handing off properly, despite the similar problems that
continue to plague Radeon/radeon users with the ati module being forced
upon them.
Likely, the problem stems from myriad other problems with the X
configuration that have been fixed in Ubuntu, to the point where it is
extremely rare to see a site with custom X configurations for Ubuntu,
because it almost always works out of the box. I dare suggest that,
with the import of Ubuntu's xorg packages into Debian, that this problem
is resolved within Debian already (also with Otavio Salvador's import of
the Ubuntu 'xresprobe' tool, which does a pretty sterling job of working
things out).
So, in summary:
* not discover1, nor discover(1)-data;
* not the ati wrapper in the XFree86/Xorg DDX, problematic though it
is;
* but the configuration from the server's maintainer scripts.
Hope that helps,
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bug administratif... (administrativ bug found...)
On Thursday 08 September 2005 10:22, Sven Luther wrote: It is well possible that a similar detection problem is present in the XFree86 package, and the fact that it works fine in ubuntu is probably due to them using X.org, where this bug is absent. Another possible reason for differences is that Ubuntu Hoary uses a different kernel (2.6.10 IIRC) than Sarge (2.6.8). pgprwZQCARd31.pgp Description: PGP signature
Bug#327179: replace i830 with i915 in xorg.conf upon upgrading.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Sep 08, 2005 at 08:13:54PM +1000, Daniel Stone wrote: On Thu, 2005-09-08 at 10:55 +0300, Mohammed Sameer wrote: [please replace i830 with i915 in xorg.conf] Where? Why? It's not even listed in xorg.conf anywhere. The DDX driver is i810. ops, I meant i810 I think it'll be nice to replace i810 with 1915 when the debconf configuration is being migrated. - -- - - -- Katoob Main Developer, Arabbix Maintainer. GNU/Linux registered user #224950 Proud Egyptian GNU/Linux User Group www.eglug.org Admin. Life powered by Debian, Homepage: www.foolab.org - -- Don't send me any attachment in Micro$oft (.DOC, .PPT) format please Read http://www.gnu.org/philosophy/no-word-attachments.html Preferable attachments: .PDF, .HTML, .TXT Thanx for adding this text to Your signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDIBRHy2aOKaP9DfcRArMCAJ0Zp5d5WhlzCF1KcBE7nPiAoqNBvQCfZCV6 Bh854Nm6klDp+gP6HuX3W4U= =MYZ6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bug administratif... (administrativ bug found...)
On Thursday 08 September 2005 12:22, Daniel Stone wrote: debian-installer does not use any version of discover in any way, shape or form. Perhaps you were thinking of hotplug? Hmm. D-I most certainly _does_ use discover1 and not hotplug. AFAIK, the Ubuntu installer does not use discover during the 1st stage of installation, but Debian's d-i does. pgpGtdoQgZ8Ii.pgp Description: PGP signature
Re: bug administratif... (administrativ bug found...)
On Thu, 2005-09-08 at 13:14 +0200, Frans Pop wrote: On Thursday 08 September 2005 12:22, Daniel Stone wrote: debian-installer does not use any version of discover in any way, shape or form. Perhaps you were thinking of hotplug? Hmm. D-I most certainly _does_ use discover1 and not hotplug. AFAIK, the Ubuntu installer does not use discover during the 1st stage of installation, but Debian's d-i does. Okay, I thought this wa sa change that had gone up to Debian, too. Sorry for the fuss. Cheers, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327179: replace i830 with i915 in xorg.conf upon upgrading.
On Thu, 2005-09-08 at 13:36 +0300, Mohammed Sameer wrote: [replace i810 with i915] There is no 'i915' driver. The driver is still called i810, even though it supports all i8xx and i9xx chipsets. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327179: replace i830 with i915 in xorg.conf upon upgrading.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Sep 08, 2005 at 09:28:50PM +1000, Daniel Stone wrote: On Thu, 2005-09-08 at 13:36 +0300, Mohammed Sameer wrote: [replace i810 with i915] There is no 'i915' driver. The driver is still called i810, even though it supports all i8xx and i9xx chipsets. Hm, Then the NEWS.Debian file should be corrected I guess ? * i830 and ffb DRI modules removed by upstream. i915 and sis DRI modules added. - -- - - -- Katoob Main Developer, Arabbix Maintainer. GNU/Linux registered user #224950 Proud Egyptian GNU/Linux User Group www.eglug.org Admin. Life powered by Debian, Homepage: www.foolab.org - -- Don't send me any attachment in Micro$oft (.DOC, .PPT) format please Read http://www.gnu.org/philosophy/no-word-attachments.html Preferable attachments: .PDF, .HTML, .TXT Thanx for adding this text to Your signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDICccy2aOKaP9DfcRAtrfAJ9wu4eDQBP/LoXjXD84lowmeObRRQCfTZtj xNM7/fQbsdIBAgxXuMYx/k4= =oBSl -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bug administratif... (administrativ bug found...)
On Thu, Sep 08, 2005 at 12:43:31PM +0200, Frans Pop wrote: On Thursday 08 September 2005 10:22, Sven Luther wrote: It is well possible that a similar detection problem is present in the XFree86 package, and the fact that it works fine in ubuntu is probably due to them using X.org, where this bug is absent. Another possible reason for differences is that Ubuntu Hoary uses a different kernel (2.6.10 IIRC) than Sarge (2.6.8). No chance it could affect X and the graphic card detection though. Just terminally broken X configuration stuff, and we all knew this was the case well in advance of the release and chose to do nothing about it. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327179: marked as done (replace i830 with i915 in xorg.conf upon upgrading.)
Your message dated Thu, 08 Sep 2005 23:22:48 +1000 with message-id [EMAIL PROTECTED] and subject line Bug#327179: replace i830 with i915 in xorg.conf upon upgrading. has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 8 Sep 2005 07:55:20 + From [EMAIL PROTECTED] Thu Sep 08 00:55:20 2005 Return-path: [EMAIL PROTECTED] Received: from foolab.org [67.18.92.211] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1EDHFg-0002Op-00; Thu, 08 Sep 2005 00:55:20 -0700 Received: from uniball (unknown [212.103.170.135]) by foolab.org (Postfix) with ESMTP id C4AF77D832; Thu, 8 Sep 2005 10:55:18 +0300 (EEST) Received: by uniball (Postfix, from userid 1000) id 9DDBF9732C; Thu, 8 Sep 2005 10:55:19 +0300 (EEST) Date: Thu, 8 Sep 2005 10:55:19 +0300 From: Mohammed Sameer [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: replace i830 with i915 in xorg.conf upon upgrading. Message-ID: [EMAIL PROTECTED] Reply-To: Mohammed Sameer [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed Content-Disposition: inline X-Reportbug-Version: 3.15 User-Agent: Mutt/1.5.9i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: xserver-xorg Version: 6.8.2.dfsg.1-6 Severity: wishlist I guess this'd be nice, Maybe when etch is released and people do a dist-upgrade. Not sure. Best wishes, - -- - - -- Katoob Main Developer, Arabbix Maintainer. GNU/Linux registered user #224950 Proud Egyptian GNU/Linux User Group www.eglug.org Admin. Life powered by Debian, Homepage: www.foolab.org - -- Don't send me any attachment in Micro$oft (.DOC, .PPT) format please Read http://www.gnu.org/philosophy/no-word-attachments.html Preferable attachments: .PDF, .HTML, .TXT Thanx for adding this text to Your signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDH+5ny2aOKaP9DfcRAtPbAKCMDPo/H8+ocq7Ei5f0ABKqPxdClQCgi0XA Cph5ZKWEBhHrmnnJR1XzU5M= =TzsE -END PGP SIGNATURE- --- Received: (at 327179-done) by bugs.debian.org; 8 Sep 2005 13:21:13 + From [EMAIL PROTECTED] Thu Sep 08 06:21:13 2005 Return-path: [EMAIL PROTECTED] Received: from visp.inabox.net (ephemera.fooishbar.org) [203.49.196.168] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1EDML2-0002g1-00; Thu, 08 Sep 2005 06:21:13 -0700 Received: from ephemera.fooishbar.org (localhost.localdomain [127.0.0.1]) by ephemera.fooishbar.org (Postfix) with ESMTP id D1C0927C11A; Thu, 8 Sep 2005 23:22:48 +1000 (EST) Subject: Re: Bug#327179: replace i830 with i915 in xorg.conf upon upgrading. From: Daniel Stone [EMAIL PROTECTED] To: Mohammed Sameer [EMAIL PROTECTED], [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Content-Type: text/plain Date: Thu, 08 Sep 2005 23:22:48 +1000 Message-Id: [EMAIL PROTECTED] Mime-Version: 1.0 X-Mailer: Evolution 2.3.8 Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 On Thu, 2005-09-08 at 14:57 +0300, Mohammed Sameer wrote: [it's not DDX, but really DRI] DRI modules are loaded as a result of what the driver tells libGL to load (as a rather simplified overview), rather than anything in the configuration file. So, things will just work. No configuration file messing needed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bug administratif... (administrativ bug found...)
On Thu, Sep 08, 2005 at 12:43:31PM +0200, Frans Pop wrote: On Thursday 08 September 2005 10:22, Sven Luther wrote: It is well possible that a similar detection problem is present in the XFree86 package, and the fact that it works fine in ubuntu is probably due to them using X.org, where this bug is absent. Another possible reason for differences is that Ubuntu Hoary uses a different kernel (2.6.10 IIRC) than Sarge (2.6.8). Also hotplug in the installer rather than discover, which could easily make a difference to hardware detection (and shifts more of the burden to the kernel, so kernel versions are more likely to make a difference to what hardware is detected). I've contributed that code from Ubuntu back to d-i so that it can be enabled by building the initrd in a different way, but I can't make the decision for Debian on whether to use discover or hotplug. This makes it quite difficult for me to deal with mails that say Ubuntu can detect this but Debian can't; why haven't you contributed these improvements?, because in many cases there's little more I can do. (It's true that I didn't manage to get the hotplug stuff into d-i before sarge released, though. Mea culpa.) Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327097: Problem fixed
It used to work with the initial configuration, but something happened in the latest upgrade that broke it. I fixed it but maybe IPV6 should not be enabled by default, it is not compiled in thy kernel :) (if it's the problem) Today I tried to connect remotely to Wolfe and Colborne xdm servers but my Exceed client has never been able to connect to one of these. Looking throught the megabytes of logfiles, I found that interesting log part: Wed Sep 7 13:05:22 2005 xdm info (pid 31630): starting Wed Sep 7 13:05:22 2005 xdm error (pid 31630): XDMCP socket creation failed: Address family not supported by protocol Wed Sep 7 13:05:22 2005 xdm info (pid 31630): starting X server on :0 The first thing I did was creating a bug report. Then I increased the log level of the xdm daemon by adding DisplayManager.debugLevel: 10 to "/etc/X11/xdm/xdm-config". Then I restarted the xdm daemon. DisplayManager.errorLogFile/DisplayManager.ErrorLogFile value /var/log/xdm.log DisplayManager.daemonMode/DisplayManager.DaemonMode value true DisplayManager.pidFile/DisplayManager.PidFile value /var/run/xdm.pid DisplayManager.lockPidFile/DisplayManager.LockPidFile value true DisplayManager.authDir/DisplayManager.authDir value /var/lib/xdm DisplayManager.autoRescan/DisplayManager.AutoRescan value true DisplayManager.removeDomainname/DisplayManager.RemoveDomainname value true DisplayManager.keyFile/DisplayManager.KeyFile value /usr/X11R6/lib/X11/xdm/xdm-keys DisplayManager.accessFile/DisplayManager.AccessFile value /usr/X11R6/lib/X11/xdm/Xaccess DisplayManager.exportList/DisplayManager.ExportList value DisplayManager.randomFile/DisplayManager.RandomFile value /dev/mem DisplayManager.prngdSocket/DisplayManager.PrngdSocket value /tmp/entropy DisplayManager.prngdPort/DisplayManager.PrngdPort value 0 DisplayManager.randomDevice/DisplayManager.RandomDevice value /dev/random DisplayManager.greeterLib/DisplayManager.GreeterLib value /usr/X11R6/lib/libXdmGreet.so DisplayManager.choiceTimeout/DisplayManager.ChoiceTimeout value 15 DisplayManager.sourceAddress/DisplayManager.SourceAddress value false DisplayManager.willing/DisplayManager.Willing value su nobody -c /usr/X11R6/lib/X11/xdm/Xwilling storing process ID in /var/run/xdm.pid Wed Sep 7 15:15:56 2005 xdm info (pid 693): starting created chooser socket 3 creating socket to listen on port 177 of address :: Wed Sep 7 15:15:56 2005 xdm error (pid 693): XDMCP socket creation failed: Address family not supported by protocol found new display: :0 local /usr/X11R6/bin/X vt7 -dpi 100 StartDisplay :0 Wed Sep 7 15:15:56 2005 xdm info (pid 693): starting X server on :0 DisplayManager._0.serverAttempts/DisplayManager._0.ServerAttempts value 1 DisplayManager._0.openDelay/DisplayManager._0.OpenDelay value 15 DisplayManager._0.openRepeat/DisplayManager._0.OpenRepeat value 5 DisplayManager._0.openTimeout/DisplayManager._0.OpenTimeout value 120 DisplayManager._0.startAttempts/DisplayManager._0.StartAttempts value 4 DisplayManager._0.pingInterval/DisplayManager._0.PingInterval value 5 DisplayManager._0.pingTimeout/DisplayManager._0.PingTimeout value 5 DisplayManager._0.terminateServer/DisplayManager._0.TerminateServer value false DisplayManager._0.grabServer/DisplayManager._0.GrabServer value false DisplayManager._0.grabTimeout/DisplayManager._0.GrabTimeout value 3 DisplayManager._0.resetSignal/DisplayManager._0.Signal value 1 DisplayManager._0.termSignal/DisplayManager._0.Signal value 15 DisplayManager._0.resetForAuth/DisplayManager._0.ResetForAuth value false DisplayManager._0.authorize/DisplayManager._0.Authorize value true DisplayManager._0.authComplain/DisplayManager._0.AuthComplain value true DisplayManager._0.authName/DisplayManager._0.AuthName value XDM-AUTHORIZATION-1 MIT-MAGIC-COOKIE-1 DisplayManager._0.authFile/DisplayManager._0.AuthFile value SetLocalAuthorization :0, auth XDM-AUTHORIZATION-1 GenerateAuthorization XDM-AUTHORIZATION-1 Local server auth 7d 85 ba 17 28 b3 4f fa 00 fa fd 3a a3 d3 20 67 got 0x806dec8 (19 XDM-AUTHORIZATION-1) 7d 85 ba 17 28 b3 4f fa 00 fa fd 3a a3 d3 20 67 GenerateAuthorization MIT-MAGIC-COOKIE-1 got 0x806e8d0 (18 MIT-MAGIC-COOKIE-1) 94 e8 64 d2 a3 4f 5e b4 6d 09 97 71 31 d3 82 af file: /var/lib/xdm/authdir/authfiles/A:0-VDrgbm auth: 0x806deb8 StartServerOnce for :0 '/usr/X11R6/bin/X' 'vt7' '-dpi' '100' '-auth' '/var/lib/xdm/authdir/authfiles/A:0-VDrgbm' server started (pid 698) display manager paused til SIGUSR1 XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-14 20050601051219 [EMAIL PROTECTED]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.29-pre2 i686 [ELF] DisplayManager._0.resources/DisplayManager._0.Resources value /usr/X11R6/lib/X11/xdm/Xresources Build Date: 01 June 2005 This version of XFree86 has been extensively modified by the Debian Project, and is not supported by the XFree86 Project, Inc., in any way. Bugs should be reported to the Debian Bug Tracking System; see .
Bug#327000: Regression: suspend with radeon doesn't work any more
Hi, Just a minute ago, Xorg locked up for no reason with the very same behaviour... I could ssh to the box; Xorg was at 100%, killing Xorg and restarting it (well, gdm did so) got me a working new Xserver. So maybe it's just triggering a different bug on suspend... btw, your provider, verizon, doesn't accept my emails. Without pointing me to a reason why he does so. But I checked 35 dnsbl, and I'm listed in none of them (and there better shouldn't be a reason to list me...) best regards, Erich Schubert -- erich@(vitavonni.de|debian.org)--GPG Key ID: 4B3A135C(o_ To understand recursion you first need to understand recursion. //\ Ein Freund ist ein Geschenk, das man sich selbst macht. V_/_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327000: Regression: suspend with radeon doesn't work any more
On Thu, Sep 08, 2005 at 04:54:25PM +0200, Erich Schubert wrote: Hi, Just a minute ago, Xorg locked up for no reason with the very same behaviour... I could ssh to the box; Xorg was at 100%, killing Xorg and restarting it (well, gdm did so) got me a working new Xserver. So maybe it's just triggering a different bug on suspend... If you upgraded from -5, there's nothing that could freshly trigger this sort of problem in a non-savage card. I have to admit, I'm fairly perplexed. btw, your provider, verizon, doesn't accept my emails. Without pointing me to a reason why he does so. But I checked 35 dnsbl, and I'm listed in none of them (and there better shouldn't be a reason to list me...) Sorry about that. Just keep sending replies to the bug, since I'm subscribed to debian-x and I can see what you write there. I really need to find a better provider... - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327099: Xserver-xorg radeon dual head monitor detection problem
On Thu, 2005-09-08 at 10:39 +0200, Jan Nielsen wrote: (II) RADEON(0): Primary: Monitor -- CRT Connector -- VGA DAC Type -- Primary TMDS Type -- NONE DDC Type -- VGA_DDC (II) RADEON(0): Secondary: Monitor -- NONE Connector -- DVI-I DAC Type -- TVDAC/ExtDAC TMDS Type -- Internal DDC Type -- DVI_DDC ... (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled ... (WW) RADEON(1): Only one monitor detected, Second screen will NOT be created FWIW, you should be able to work around this using something like Option MonitorLayout CRT,CRT See the radeon(4x) manpage. Doesn't work. I have tried all possible combinations of CRT, TDMS and LDVS and none of them works. Does the logfile show that the option is honoured though? I have two Benq FP731 LCD monitors. How do you connect them? Two digital connections isn't supported ATM, for example. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#326956: xserver-xorg: Memory leak
El miércoles, 7 de septiembre de 2005 19:27, Michel Dänzer escribió: Such behavior would be acceptable if X.org forgot old background images. But it doesn't. Try to successively load a series of background images, e.g. from the KDE wallpaper collection, and the memory occupied by Xorg will keep growing. First of all, verify using something like xrestop that it's not actually a client leaking references to the wallpaper pixmaps. Even if that's ruled out, freeing memory that was allocated from the heap can't always be returned to the system immediately because the heap can only shrink down to the highest allocation still in use. If that's the case, it should still be able to re-use a gap sometimes, especially when you switch to a smaller wallpaper, in which case the memory usage reported for the X server shouldn't increase. I'm curious as to which of these might apply to your situation, if any. Hello, Siep. I have been testing with xrestop and Michel is right. My machine runs KDE 3.4.2 and X.Org 6.8.2.dfsg.1-6, and I cannot see any increment in the memory usage in X. When I use a background, I see KDE Desktop process going up in the comsumption list, but it does not surpass 5917 KB in any case, even when I changed about twenty times my background desktop image. I even saw Xorg process in a common 'top' with 115 MB of resident memory. Another round of image switching did not changed Xorg's memory, until my default setting: no background image. In this moment, Xorg even give me back 5 MB of memory, falling to 110 MB. Is this true for you? If so, I would like to close this bug. Best regards, Ender. -- So much to do, so little time... -- Joker (Batman). -- Debian developer pgpFbFpguGHLC.pgp Description: PGP signature
Bug#327248: xserver-xorg: X applications start slowly after [fonts] upgrade
Package: xserver-xorg Version: 6.8.2.dfsg.1-6 Severity: normal Every time I upgrade xserver (this also happened in xfre886 times) X applications' startup slows tremendously (I'm using KDE if it has any meaning). This effect disappears after I run fc-cache -f manually. I'm not familiar enough with xserver's packages to say what might be the reason, and if running fc-cache in postinst is a workaround or a fix :) [or if it's some kind of misconfiguration on my side] -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 17 2005-09-04 10:50 /etc/X11/X - /usr/bin/X11/Xorg -rwxr-xr-x 1 root root 1838940 2005-08-31 18:03 /usr/bin/X11/Xorg Contents of /var/lib/xfree86/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: :01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 00f3 (rev a2) /etc/X11/xorg.conf does not match checksum in /var/lib/xfree86/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 2969 2005-08-15 22:08 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (Xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cp /etc/X11/xorg.conf /etc/X11/xorg.conf.custom # md5sum /etc/X11/xorg.conf /var/lib/xfree86/xorg.conf.md5sum # dpkg-reconfigure xserver-xorg Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/CID FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section Module Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadtype1 Loadv4l Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout pl Option XkbVariantpl EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons false Option ZAxisMapping 4 5 EndSection Section Device Identifier GeForce 6200 Driver nvidia BusID PCI:1:0:0 EndSection Section Monitor Identifier SyncMaster 753dfx Option DPMS HorizSync 30-65 VertRefresh 50-75 EndSection Section Screen Identifier Default Screen Device GeForce 6200 Monitor SyncMaster 753dfx DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice
Bug#325867: Additional info
After reloading X, it uses ~28mb of memory. When it uses ~250mb - system is becoming too slow. So, what do you say? What should I do to test it?
Bug#326956: xserver-xorg: Memory leak
On Thu, Sep 08, 2005 at 06:13:49PM +0200, David Mart?nez Moreno wrote: El miércoles, 7 de septiembre de 2005 19:27, Michel Dänzer escribió: Such behavior would be acceptable if X.org forgot old background images. But it doesn't. Try to successively load a series of background images, e.g. from the KDE wallpaper collection, and the memory occupied by Xorg will keep growing. First of all, verify using something like xrestop that it's not actually a client leaking references to the wallpaper pixmaps. Even if that's ruled out, freeing memory that was allocated from the heap can't always be returned to the system immediately because the heap can only shrink down to the highest allocation still in use. If that's the case, it should still be able to re-use a gap sometimes, especially when you switch to a smaller wallpaper, in which case the memory usage reported for the X server shouldn't increase. I'm curious as to which of these might apply to your situation, if any. Hello, Siep. I have been testing with xrestop and Michel is right. My machine runs KDE 3.4.2 and X.Org 6.8.2.dfsg.1-6, and I cannot see any increment in the memory usage in X. When I use a background, I see KDE Desktop process going up in the comsumption list, but it does not surpass 5917 KB in any case, even when I changed about twenty times my background desktop image. I even saw Xorg process in a common 'top' with 115 MB of resident memory. Another round of image switching did not changed Xorg's memory, until my default setting: no background image. In this moment, Xorg even give me back 5 MB of memory, falling to 110 MB. Is this true for you? If so, I would like to close this bug. Best regards, Ender. I believe there is still a memory leak. After startup, on my system Xorg takes up about 10mb of memory. This increases to 30mb and more after one or two days even after closing all applications. However, today memory use could no longer be increased without limit just by loading different background images: the memory sometimes goes up and sometimes down and doesn't go up further than about 3mb total amount. I don't know what caused the change. Now that I no longer have a simple way to trigger a memory leak you are probably right to close this bug. xserver-xorg is version 6.8.2.dfsg.1-5, and the window manager a hand-compiled fvwm 2.4.18. Regards, -- Siep Kroonenberg
Bug#318688: Modifies conffile?
Package: x11-common
Version: 6.8.2.dfsg.1-6
Severity: normal
File: /etc/Xsession
File: /etc/Xsession.options
I was prompted with the following 2 diffs today while dist-upgrading
to current testing; I made none of the listed changes.
--- /etc/X11/Xsession.options 2002-04-16 08:29:11.0 -0400
+++ /etc/X11/Xsession.options.dpkg-new 2005-08-31 11:57:20.0 -0400
@@ -1,4 +1,4 @@
-# /etc/X11/Xsession.options
+# $Id: Xsession.options 189 2005-06-11 00:04:27Z branden $
#
# configuration options for /etc/X11/Xsession
# See Xsession.options(5) for an explanation of the available options.
@@ -6,3 +6,4 @@
allow-user-resources
allow-user-xsession
use-ssh-agent
+use-session-dbus
--- /etc/X11/Xsession 2005-02-18 16:32:40.0 -0500
+++ /etc/X11/Xsession.dpkg-new 2005-08-31 11:57:20.0 -0400
@@ -4,7 +4,7 @@
#
# global Xsession file -- used by display managers and xinit (startx)
-# $Id: Xsession 2186 2005-02-11 07:11:05Z branden $
+# $Id: Xsession 405 2005-07-24 04:46:38Z dnusinow $
set -e
@@ -42,11 +42,29 @@
# the user would have dismissed the error we want reported before seeing the
# request to report it.
errormsg $* \
- Please report the installed version of the \xfree86-common\ \
+ Please report the installed version of the \x11-common\ \
package and the complete text of this error message to \
debian-x@lists.debian.org.
}
+run_parts () {
+ # until run-parts --noexec is implemented
+ if [ -z $1 ]; then
+internal_errormsg run_parts() called without an argument.
+ fi
+ if [ ! -d $1 ]; then
+internal_errormsg run_parts() called, but \$1\ does not exist or is \
+ not a directory.
+ fi
+ for F in $(ls $1); do
+if expr $F : '[[:alnum:]_-]\+$' /dev/null 21; then
+ if [ -f $1/$F ]; then
+echo $1/$F
+ fi
+fi
+ done
+}
+
# initialize variables for use by all session scripts
OPTIONFILE=/etc/X11/Xsession.options
@@ -94,11 +112,11 @@
fi
rm -f $WRITE_TEST
-# Use run-parts to source every file in the session directory; we source
+# use run-parts to source every file in the session directory; we source
# instead of executing so that the variables and functions defined above
# are available to the scripts, and so that they can pass variables to each
-# other.
-SESSIONFILES=$(run-parts --list $SYSSESSIONDIR)
+# other
+SESSIONFILES=$(run_parts $SYSSESSIONDIR)
if [ -n $SESSIONFILES ]; then
for SESSIONFILE in $SESSIONFILES; do
. $SESSIONFILE
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327282: xserver-xorg: can't switch to virtual console with alt-ctl-f1
Package: xserver-xorg Version: 6.8.2.dfsg.1-6 Severity: important xserver-xfree86 allowed one to exit the xserver to a virtual console using the alt-ctl-f1...f6 combinations. The new xserver-xorg does not appear to allow this; this is very important should a window manager get stuck, for example. Any suggestions on how to fix? Julian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327282: xserver-xorg: can't switch to virtual console with alt-ctl-f1
On Fri, 2005-09-09 at 00:26 +0100, Julian Gilbey wrote: xserver-xfree86 allowed one to exit the xserver to a virtual console using the alt-ctl-f1...f6 combinations. The new xserver-xorg does not appear to allow this; this is very important should a window manager get stuck, for example. Any suggestions on how to fix? It, um, does. This is usually an indication of XKB problems. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327000: Regression: suspend with radeon doesn't work any more
On Thu, 2005-09-08 at 12:03 +0200, Erich Schubert wrote: Hi, Did you upgrade from -5 to -6? There shouldn't have been anything that touched this sort of thing between those two revisions. I'm pretty sure I had -5 running before that. I tried downgrading the xserver-xorg package, but that didn't help. Any of the lib packages I could try? I can't think of any that would be relevant for suspend/resume. Could it be that the upgrade modified the configuration file or something though? I have the impression that it is maybe related to the xscreensaver or opengl. But that might be just a timing coincidence. I think it's more likely related to the kernel, or another component that's directly involved in suspend/resume. Have you upgraded any of these recently? -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
