On Mon, 2007-02-12 at 11:41 +0100, Brice Goglin wrote:
> About 14 months ago, you reported a bug to the Debian BTS regarding a
> crash of Xemacs on a nVidia board, possibly caused by a bug in libX11.
> Did you reproduce this problem recently?
No, I haven't seen this in a while. I think it's OK
Package: gnome-vfs
Severity: normal
With a recent update, the mounts of my disks appear to have changed
names on my desktop (and in computer:///) to the volume label of the
disk. I don't appear to have any reasonable interface to change these
names. Can I have the partition name from /etc/fsta
Stephen J. Turnbull writes:
> > "Ben" == Ben Wing <[EMAIL PROTECTED]> writes:
>
> Ben> the best way to know for sure is for you to compille XEmacs
> Ben> yourself, with debugging support.
>
> Also, Debian supplies -dbg packages for the X libraries, so you would
> be able to ge
Ohura-san,
In working to figure out debian bug 343129, which involves crashes in
Xemacs, Ben Wing suggested compiling my own xemacs (21.4.18) for
debugging. When I do that, the crash goes away. I configured it with
--debug and --with-gnome. What other flags did you use to configure
the xemac
Lonni J Friedman writes:
> I have a few questions
Thanks for the quick response.
> 0) Does this reproduce if you're not using RenderAccel?
Yes. At least commenting out
#Option "RenderAccel" "true"
in the screen section of xorg.conf and restarting X doesn't fix the
problem.
Ben Wing writes:
> do the backtraces always look like this or do they vary?
They are always in XCheckIfEvent, although how they get there varies,
e.g.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912549568976 (LWP 29564)]
0x2bfb4ac0 in XCheckIfEven
Upgrading to kernel 2.6.14 solves this problem. At least inserting a
USB key creates an entry in /dev which can be mounted. The automount
stuff doesn't work in my installation, but I don't really mind.
Thanks!
Larry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscri
> can you please upgrade to linux-2.6 version 2.6.14-4 and verify
> this bug is still present?
Debian repositories are now distributing 2.6.14-2. Should I try that
or wait until 14-4 shows up?
Larry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Co
OK, I understand now that this is a udev bug. Just in case it helps,
here's version information:
Linux fast 2.6.12-1-amd64-k8 #1 Wed Sep 28 02:31:26 CEST 2005 x86_64 GNU/Linux
[EMAIL PROTECTED]:~$ apt-cache showpkg udev
Package: udev
Versions:
0.076-3(/var/lib/apt/lists/debian.csail.mit.edu_de
Package: usbutils
Version: 0.71+cvs20051029-3
Severity: important
Folks,
I just spent half an hour trying to figure out how to get a USB key to
mount on my amd64 system running the latest unstable.
When I first put in the key, dmesg showed only:
usb 3-5: new high speed USB device using ehci
Package: kernel-2.6.10-1-686-smp
Version: 2.6.10-3
Dear Ben & other developers,
When I upgraded from 2.6.9-3 to 2.6.10-3, I lost the ability to mount
firewire disks (specifically, an ipod).
Under 2.6.9 (and before), after connecting the ipod and doing a
(manual) modprobe sbp2, /proc/scsi/scsi
A++ Maks,
Just for the heck of it, I tried 2.6.8, which Philip Armstrong
reported worked. Didn't work for me, alas. Here's the dmesg from
2.6.8. Let me know if there are other diagnostics I can offer.
Larry
basement:~# dmesg
Linux version 2.6.8-1-686-smp ([EMAIL PROTECTED]) (gcc version 3.3.
12 matches
Mail list logo