stem"
> An: "Sten Heinze"
> Betreff: Bug#815630: Acknowledgement (2.4.67-1 causes black screen after
> login on plasma desktop)
>
> Thank you for filing a new Bug report with Debian.
>
> This is an automatically generated reply to let you know your message
Package: libdrm-intel1
Version: 2.4.67-1
Severity: important
Dear Maintainer,
Updating libdrm-intel1 from 2.4.66-2 to 2.4.67-1 causes a black screen after
logging into the
plasma desktop. Only the mouse is still visible and the blue glow around the
start menu
whenever the mouse moves over it.
Package: xserver-xorg-video-intel
Version: 2:2.21.15-2+b2
Severity: normal
Dear Maintainer,
on my last update/upgrade of my Debian/testing desktop,
xserver-xorg-video-intel was removed.
This does not lead to an unusable desktop, because it falls back using
llvmpipe, however, some
programs like
> - Ursprüngliche Nachricht -
> Von: Julien Cristau
> Gesendet: 18.08.12 11:33 Uhr
> An: Sten Heinze, 684...@bugs.debian.org
> Betreff: Re: Bug#684634: xserver-xorg-video-intel: viewing pic in browser
> reboots laptop
>
> On Sun, Aug 12, 2012 at 02:20:58
Hi,
Some more information:
--The external monitor is not necessary. The crash occurs just with the
internal screen.
--Zooming the picture is not enough, it seems. I only get reliable crashes (and
reboots)
if I move the mouse while clicking i.e. start dragging the image in the
browser.
--T
On Tuesday 29 June 2010 16:41:29 Julien Cristau wrote:
> On Fri, Jun 27, 2008 at 17:10:07 +0200, Sten Heinze wrote:
> > Package: libgl1-mesa-glx
> > Version: 7.0.3-1
> > Severity: important
> >
> > Since my last update I noticed a immense slowdown in the graphic
Reading through the commit log for the mesa_7_2_branch I found that
freedesktop.org bug #17766 [1] is exactly my bug and the patch at [2] fixes it.
I attached the patch.
Thanks and regards,
Sten
[1] http://bugs.freedesktop.org/show_bug.cgi?id=17766
[2]
http://cgit.freedesktop.org/mesa/mesa/com
With the help of jcristau I got the attached gdb log by doing the following:
--on terminal tty1
$ X
--ssh session 1
$ pidof X
3872
$ gdb -p 3872
--ssh session 2
$ export DISPLAY=:0; startkde
Thanks and regards,
Sten
# gdb -p 3871
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, In
I attached the xorg.0.log containing the crash.
Regards,
Sten
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27.10-sh-pentiumm i686 Debian
Current Operating System: Linux brasilia 2.6.27.10-sh-pentiumm #1 PREEMPT Tue
Dec 23
Package: xserver-xorg-core
Version: 2:1.5.3-1
Severity: important
After upgrade to xorg 7.4/xserver 1.5.3, the xserver crashes on startx
if DRI is enabled. Disabling it in xorg.conf (and disabling compositing
in kwin) make the xserver start again. This was working with xserver
1.4/testing.
Th
Am Tuesday 28 October 2008 06:54:05 schrieben Sie:
> Handle yes, allocate no. Allocating room for a 2048x2048 virtual screen
> requires a lot of available memory.
I cannot imagine that it needs more memory that I have. According to [1] on
system with more than 256MB of ram (i have more) 64MB shoul
Am Mittwoch 22 Oktober 2008 17:41:35 schrieb Julien Cristau:
> The 2048 log shows that the driver isn't able to allocate enough memory
> for direct rendering from the GART. This explains why indirect
> rendering is used instead. I think we should close this as not a bug.
Hi Julien,
But shouldn'
Hi,
I am using the vesa driver since yesterday, and it is stable so far. But it
only has limited number of colors and no 3d acceleration.
After searching again I found very similar bug reports:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/244817
https://bugs.launchpad
Hi,
I got a little further in investigating the problem. What I did:
--boot, stop kdm, login on tty1, 'startx';
--ssh into the system, attach gdb to the x process;
--from this session you can only logout and return to tty1.
On logging out I got hit by the bug again (blank screen, no reaction to
Hi,
I was not able to attach gdb successfully in case of a crash. Trying to attach
after a crash is not possible (ssh: connect to host 160.129.138.82 port 22: No
route to host). Everytime I attached gdb before shutting down, it did not
crash.
So I tried to change kernel version (vanilla 2.6.2
Am Saturday 30 August 2008 08:51:50 schrieben Sie:
> Is the machine pingable after the crash? Can you restart X without any
> problem?
No ping after a crash. trying to ssh into the system (it works before a crash)
results in:
$ ssh [EMAIL PROTECTED]
ssh: connect to host 160.129.138.82 port 22: No
Package: xorg
Version: 1:7.3+15
Severity: grave
Justification: causes data loss
xorg crashes randomly on shutdown, i.e. after the desktop environment
shut down (closing programs and playing shutdown sound). The screen does
not return to the normal console (tty1) but stays black instead and
fre
Found http://bugs.freedesktop.org/show_bug.cgi?id=16151 today and removed the
following line which I added in order to use external monitors:
Virtual 2048 2048
Afterwards the error message was not displayed anymore, and also 'glxinfo |
grep rendering' returns now 'direct renderin
I tried to find more information. It looks like the bugs has a similar reason
as #393266 for xserver-xorg-video-savage, see also
http://bugzilla.kernel.org/show_bug.cgi?id=7767.
I installed debian's linux-image-2.6.25-2-686 from testing, and compiled
vanilla 2.6.25.10 (+patches for tp-smapi, hd
Am Freitag, 27. Juni 2008 19:19:06 schrieb Brice Goglin:
> Sten Heinze wrote:
> > Package: libgl1-mesa-glx
> > Version: 7.0.3-1
> > Severity: important
> >
> > Since my last update I noticed a immense slowdown in the graphics
> > performance. Even switchi
Package: libgl1-mesa-glx
Version: 7.0.3-1
Severity: important
Since my last update I noticed a immense slowdown in the graphics
performance. Even switching desktops needs up to several seconds.
Looking into Xorg.0.log I found:
(EE) AIGLX error: drmMap of framebuffer failed (Invalid argument)(EE
21 matches
Mail list logo
