On Sunday 26 December 2010 12:34:47 Moritz Muehlenhoff wrote:
> On Mon, Aug 09, 2010 at 12:04:25PM +0200, Matthias Breier wrote:
> > > > I'm not sure how to proceed in my case. How can I test if the changes
> > > > mentioned in the upstream bug report (
>
> > I'm not sure how to proceed in my case. How can I test if the changes
> > mentioned in the upstream bug report (
> > http://bugs.freedesktop.org/show_bug.cgi?id=25510 ) have reached the
> > Squeeze's current kernel version?
>
> I'm pretty sure they are. If your issue is still present in 2.6.3
Package: linux-source-2.6.32
Version: 2.6.32-18
Severity: serious
--- Please enter the report below this line. ---
Hello everyone,
I've just realized that I still use the kernel parameter "mem=3500M" at boot
time. With
this configuration everything works fine (besides the missing 500MB of RAM
Hi Brice,
> Any improvement with intel 2.7.1 or 2.7.99.1-2 from experimental?
> You might want to use a recent kernel such as 2.6.30-rc8.
Currently everything works rather well with xserver-xorg-video-intel (2.7.1-1)
and linux-image-2.6.29-2-amd64 (2.6.29-5). Videos are finally playable as
befo
Hi,
I've just upgraded to version 2.7.0 and experience still the crashes. So no
improvement on this aspect (though other, smaller bugs seem to have been
fixed).
Bye
Matthias
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Con
Hi Apelete,
maybe you could install temporarily the following packages to obtain more
meaningful backtraces:
xserver-xorg-video-intel-dbg
libdrm-intel1-dbg
libc6-dbg
libgl1-mesa-dri-dbg
Bye
Matthias
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "un
Hello again,
I've just generated three backtraces according to
https://wiki.ubuntu.com/X/Backtracing from crashes caused by three similar
actions. Everytime I have been trying to play a video file. Whenever I have
tried to manipulate the playback of the video file or tried to access a
context
Hello,
I suppose I can confirm this bug. Everytime I try to view a video with xine,
vlc or mplayer, the XServer crashes and restarts. I attached my xorg.conf and
the log file Xorg.0.log.old, which includes the error messages after the
crash.
I suppose it's related to the bug mentioned in
https
I have just renamed ~/.kde/share/apps/kopete and suddenly I could open the
settings again. The problem seems to be related to an entry in this
directory. Since the configuration is stored in another directory you would
only loose your chat history (or rather complicate the access to it).
Maybe
Package: kopete
Version: 4:3.5.9-1
Severity: important
Everytime i try to open the settings of Kopete it crashes. Both possibilities -
open the settings via the main menu or the tray-icon menu - show the same
behaviour.
The last thing I did was adding a new Jabber account several weeks ago. Tod
Hello Julien,
interestingly I have the same mouse and the same problem. But I created
especially to prevent these problems a persistent symlink at the event device
dealing with my mouse via udev. So my xorg.conf device section looks like the
following:
Section "InputDevice"
Identifie
Hi,
as Jörg mentioned in his mail
(http://lists.debian.org/debian-devel-announce/2007/11/msg2.html), packets
uploaded in a short period around the occurence of the hardware problem might
still be missing in the repositories.
So, could you perhaps verify if your new xserver-xorg packet was
Hi,
I seem to have the same problem as Ken. Whenever I quit KPilotDeamon, it
crashes. Maybe my backtrace attached to this messages helps solving this problem.
Best regards,
Matthias
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enable
e000)
libdrm.so.2 => /lib/libdrm.so.2 (0xb7f82000)
libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7f5c000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7e19000)
/lib/ld-linux.so.2 (0x8000)
Best regards
Matthias Breier
--- Content of Xorg.0.log ---
X Window System V
14 matches
Mail list logo
