On Dec 7, 2007 2:10 AM, Lou Arruda wrote:
I did get the same backgrace in Xorg.0.log with the live CD as with a
regular boot of the hard drive. I also have an ATI Mobility Radeon
9600 M10 running in an IBM ThinkPad T42.
Can you please attach your log file? Preferably using the latest software.
Lou, thanks for the log files, which have this stack trace:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xe420]
2:
/usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_update_state_locked+0x7e1)
[0xb376af91]
3:
, not
necessary to spread around.
* http://lintian.debian.org/reports/mJose_Luis_Rivas.html#xscreensaver
- wrong man page section
- invalid icon/desktop sections
Looking forward to hearing your comments.
Best regards,
Tormod Volden
-- System Information:
Debian Release: lenny/sid
APT prefers
I have confirmed that this bug is not linked to the proprietary fglrx drivers
as I was able to reproduce it via live CD.
Lou, do you get the same backtrace in Xorg.0.log? What kind of card do you have?
This seems more like a bug in mesa rather than in xscreensaver.
--
To UNSUBSCRIBE, email
Package: xawtv
Version: 3.95.dfsg.1-7
Severity: normal
When I start xawtv it fails with X11 DGA errors, on ATI Mobility X700
and on an older ATI Radeon 7500. If I use -nodga it works fine.
Not sure if this is an Xorg driver bug or xawtv bug, but a similar
workaround cludge as for Nvidia cards
This is the error message. (The below message is from Ubuntu Gutsy but
that shouldn't matter).
$ xawtv
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.22-14-generic)
xinerama 0: 1680x1050+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 136
Package: portmap
Version: 6.0-4
Severity: normal
The control file (and README, watch) lists the correct upstream URL:
Homepage: http://neil.brown.name/portmap/
but the copyright file still has the old, wrong URL:
Upstream location: ftp://ftp.porcupine.org/pub/security/
-- System
Why not simply (and save a shell instance):
if [ ! $XAWTV_USE_DGA ]
- [ `xdpyinfo -queryExtensions | grep NV-GLX` ] ; then
+ xdpyinfo -queryExtensions | grep -q NV-GLX ; then
ARGS=-nodga
fi
Anyway, I need -nodga on my ATI X700 card also, but I guess I should
open a new bug for
Package: xserver-xorg-video-sis
Version: 1:0.9.3-5
Severity: normal
https://edge.launchpad.net/bugs/118325
The DDX interface is incompatible with Xorg, so it complains when
running glxinfo, and DRI is disabled:
SiS DRI driver expected DDX version 0-0.8.x but got version 0.7.1
This is fixed by
You have fglrx installed, but the log shows that you are using the
ati/radeon driver. Change to fglrx in xorg.conf and try again.
If you want to use the -ati driver, make sure you remove everything fglrx.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
According to the man page, paperconf (with no options) should return a
default size if PAPERSIZE, PAPERCONF or /etc/papersize is not found.
Currently it fails in this case.
lib/paper.h even says to use defaultpapername() if systempapername() fails.
Attaching patch from Ubuntu bug
Package: linux-wlan-ng
Version: 0.2.8+svn1832+dfsg-2
Severity: normal
Tags: patch
debian/rules uses a variable TMPDIR which is meant to be a local
variable. However if the environment variable TMPDIR has been set, its
value is consequently changed, and patch, tac and friends (which
make use of
I forgot to mention that I reported this originally in Ubuntu:
https://bugs.launchpad.net/bugs/128002
In case it would be convenient, I attach a debdiff as well.
linux-wlan-ng_0.2.8+svn1832+dfsg-3.debdiff
Description: Binary data
Package: xserver-xorg-video-savage
Version: 2.1.3-1
The src/savage_image.c was deleted from upstream git 2006-04-30
(commit 6d688c993ec7baf8f00df59764dd3e04bab24e09) but is still left
over in the Debian diff.gz.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
Third - The Debian diff for mesa-7.0.1-1 looks very strange. There
are a whole lot of files being created by it, outside of debian/,
including enormous blocks of what looks like upstream source code.
There's *also* a debian/patches directory, and logic in debian/rules
to use it. As a result
src/mesa/glapi/ and windows/VC6/mesa/ ) exist in upstream git, but not
in the upstream release. I guess they are there by mistake, maybe the
diff was made between a git-based tree and the upstream released tree?
Yes, the package is built from git, so files which are in git but not in
the
Package: linux-wlan-ng
Version: 0.2.8+svn1832+dfsg-1
Severity: minor
Tags: patch
This change is used in Ubuntu and makes the package more robust in the
case the kernel has the p80211 compiled in-kernel. It also changes the
warning to say module instead of .ko or .o.
Not essential for Debian,
I am not sure about the vanilla kernel, but for instance the Ubuntu
6.06 kernel had the p82011 built in, not as a module, and therefore
this change was needed.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I don't understand the reason you removed these bits. In which case
will my patch fail and the original version work?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
you mean the p80211 included in lwng or the ieee80211 that is part of
the kernel?
The ieee80211 has nothing to do with this, it's a different module. It
is needed as well though, and is loaded independently. Many (myself
included) were confused at one point and wrongly thought they did the
In ubuntu they used to put the interface up trough udev, and now I
figure out why, but this was preventing loading firmare. Some
devices do not need the firmware at all (like the one I own) but in
general you need it.
The current solution in Ubuntu is to call wlan-udev.sh from the udev
dependency on dmidecode
+
+ -- Tormod Volden [EMAIL PROTECTED] Mon, 09 Jul 2007 21:05:48 +0200
+
laptop-detect (0.13.1) unstable; urgency=low
* Change package priority to important to match override.
diff -Nru /tmp/vsJb0801FP/laptop-detect-0.13.1/debian/rules
/tmp/dHrfGaKKhA/laptop-detect
Package: grub
Version: 0.97-29
Followup-For: Bug #315774
I ran into the same segfaults when I compiled grub using gcc 4.1. It
turned out the handling (pointer arithmetics) of variable arguments in
char_io.c goes bad due to optimization. I replaced it with va_arg macros
and the segfaults went
Package: grub
Version: 0.97-29
Followup-For: Bug #344840
The missing error handling is also mentioned in bug #315774, which also
discusses the reasons for the segfaults.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I have filed this upstream at https://bugs.freedesktop.org/show_bug.cgi?id=11237
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: laptop-mode-tools
Version: 1.34-1
Severity: normal
Tags: patch
This was reported in https://bugs.launchpad.net/bugs/77560 by Peter
Whittaker, who also wrote the attached patch.
If laptop_mode status is run by a non-root user, some commands fails
because of insufficient permissions and
Package: laptop-mode-tools
Version: 1.34-1
Followup-For: Bug #428162
I guess it isn't useful to make a debdiff, since the debian package is handled
by
upstream. Just wanted to add that the URL in debian/copyright is wrong.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
+
+ * Make savedefault a configurable parameter (default: false)
+(Closes: #393079)
+ * Rephrase warning about using savedefault/saved
+
+ -- Tormod Volden [EMAIL PROTECTED] Sun, 10 Jun 2007 01:10:19 +0200
+
grub (0.97-28) unstable; urgency=low
* Remove second /sbin/update-grub warning
Package: xserver-xorg-video-savage
Version: 1:2.1.2-5
Severity: normal
After I log out from a X session, the virtual consoles are unusable. Either I
see coloured lines (same colours
as my desktop background) or it's all black. The same happens when I run startx
from a console and log out from
Package: xorg
Version: 1:7.2-3
Severity: minor
Tags: patch
When building any X package, quilt next is used as a probe in xsfbs.mk to see
if there are any patches. This
results in the first patch being listed, which is confusing and you might think
it applies only one patch when you look
at
Package: grub
Version: 0.97-28
Severity: important
Tags: patch
https://bugs.launchpad.net/bugs/106887
This problem was reported by Linoleum and mpwalter in Ubuntu bug #106887,
but we tested the Debian packages
as well, and they also need the patch. This was confirmed by cs224 who runs
Debian
Package: udev
Version: 0.105-4
Followup-For: Bug #427972
I had the same trouble now that I did an upgrade. My root partition was
originally a large vfat partition that I
cut in two, using gparted IIRC.
This also results in corrupted label names used to identify drives on the
desktop for
Package: login
Version: 1:4.0.18.1-8
Followup-For: Bug #385170
When I upgraded from testing to unstable today (upgrade login 1:4.0.18.1-7
1:4.0.18.1-8) I got the
question about what to do with /etc/login.defs. I have never touched that file,
so there should be no
reason for asking. See
Package: xserver-xorg-video-savage
Version: 1:2.1.2-5
Severity: normal
Trying to start an old q3demo, the X server crashed.
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c2511]
1: [0xb7fb7420]
2: /usr/lib/xorg/modules/drivers//savage_drv.so(SavageAdjustFrame+0x78)
[0xb7c16
768]
3:
Package: xserver-xorg-video-savage
Version: 1:2.1.2-5
Followup-For: Bug #423485
After installing the xserver-xorg-core-dbg, rebuilding
xserver-xorg-video-savage with nostrip debug noopt,
adding NoTrapSignals to xorg.conf,
and running ulimit -c unlimited before restarting gdm,
I got this more
I also tried launching q3demo from a console:
LIBGL_DEBUG=1 DISPLAY=:0 ./q3demo
and then the X server did not crash, only the q3demo program. See
attached console screendump.
---
- Client Initialization Complete -
--- Common Initialization Complete ---
Opening
Package: xserver-xorg-video-savage
Version: 1:2.1.2+git20070512-0.1debug
Followup-For: Bug #423485
Playing around with gdb, I see that pScrn-currentMode has been set to
NULL by xf86VidMode. If I manually set it to pScrn-modes:
(gdb) set pScrn-currentMode = pScrn-modes
the program will start and
Package: xserver-xorg-video-savage
Version: 1:2.1.2+git20070512-0.2debug
Followup-For: Bug #423485
The attached patch fixes (or works around) the problem by setting currentMode
to the new mode as
soon as the mode switching has occured, and before SavageAdjustFrame is called.
There are probably
Package: xserver-xorg-video-savage
Followup-For: Bug #276269
Thanks for the reminder. No, it doesn't crash any longer, so we can
safely close this bug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: grub
Version: 0.97-19
Followup-For: Bug #315061
It sounds like you run grub as if it had been started with the
--no-curses option, this removes the clear-screen and the line editing
facilities.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Package: octplot
Severity: normal
The files under /usr/lib/octplot are architecture-independent
and should rather be found under /usr/share.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh
Package: linux-wlan-ng
Version: 0.2.5-1
Severity: normal
Tags: patch
The linux-wlan-ng package (and the prism2 kernel modules) is very
picky about how you enter the WEP key. It is of course documented
somewhere that the format should be xx:xx:xx:xx:xx, but this is not
obvious when using the
Package: gnome-system-tools
Version: 2.14.0-2
Severity: normal
The Group tab in users-admin lists the system groups between gid 100 and
999 (at least up to 108 on my install) even if Show all users and
groups is off.
The system groups up to 100 are hidden. The hiding criteria should
probably
Package: xserver-xorg
Version: 1:7.0.22
Followup-For: Bug #386191
Christian, -latin1 should already have been stripped off, so that sg
would match. The problem is that the stripping itself is broken, see
my patch.
--- xserver-xorg.config.orig2006-06-12 05:46:03.0 +0200
+++
Package: xserver-xorg
Version: 1:7.0.22
Severity: normal
I chose English as language, Switzerland as location, and Swiss-German
as keyboard layout during the GUI debian-installer. Afterwards, the
xorg.conf had keyboard Layout us.
Here is from the installer/syslog file:
Sep 4 18:13:51
Package: linux-wlan-ng
Version: 0.2.4+svn20060808-2
Followup-For: Bug #386054
Just wanted to add that this bug is reported in Ubuntu as well:
https://launchpad.net/bugs/37451
The patch here, together with the one in bug #386057, makes
configuration of the prism2_usb devices (at least) through
Package: linux-wlan-ng-source
Version: 0.2.4+svn20060808-2
Severity: serious
I just installed the newest weekly cd, and then installed
linux-wlan-ng-source. Using module-assistant I am not able to build
the modules.
One thing is that it complains about not finding gcc-4.0 (gcc-4.1 is
Package: linux-wlan-ng-source
Followup-For: Bug #386037
Hmm, I realized the kernel had been compiled with gcc-4.0... So I
installed gcc-4.0 as well, and now it successfully built the modules.
I guess this bug should be something make sure the kernel compiler
version is installed before
Package: linux-wlan-ng
Version: 0.2.4+svn20060808-2
Severity: important
Tags: patch
Configuring the wlan0 device in the Networking applet of
gnome-system-tools sets the IF_WIRELESS_KEY variable. However,
linux-wlan-ng needs the IF_WLAN_NG_KEY0 variable set.
This little patch takes care of the
Package: linux-wlan-ng
Version: 0.2.4+svn20060808-2
Severity: important
Tags: patch
The Networking applet in gnome-system-tools have no option for network
mode and nothing gets specified on this in /etc/network/interfaces. Most
users are using a infrastructure mode network.
However,
Package: linux-wlan-ng
Version: 0.2.4+svn20060808-2
Severity: normal
Tags: patch
The check for hotplug or not inside /etc/wlan/shared uses [ -x ]
on the output from a cat command that potentially is empty.
This will return true if the cat output is empty:
[ -x ] returns false, but
[ -x ] returns
Package: udev
Version: 0.056-2
I have an external USB drive with many partitions. Since it was set up
on a mac, the (useful) partitions starts at 6, and I end up with
partition numbers up to 14. When I plug in the drive, I have access to
partitions 6-9, but not 10-14. The latter are root:disk
401 - 452 of 452 matches
Mail list logo
