Am Samstag, den 26.05.2012, 00:00 +0200 schrieb Julien Cristau:
> Don't disable 3d support?
I didn't disable 3D support (see attached glxinfo-output).
Cheers,
Stefan.
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
se
On Thu, May 24, 2012 at 15:06:05 +0200, Stefan Nagy wrote:
> xsession-errors contains the following lines:
> > gnome-session-is-accelerated: No hardware 3D support.
> > gnome-session-check-accelerated: Helper exited with code 256
>
> Does it make any sense to switch to GNOME shell with 'gnome-she
After installing some updates – sorry, I don't know which was the
relevant one, I assume gnome-shell – I'm forced into GNOME fallback mode
now; I suppose my graphics hardware got blacklisted.
xsession-errors contains the following lines:
> gnome-session-is-accelerated: No hardware 3D support.
> gn
Am Montag, den 30.04.2012, 23:11 +0200 schrieb Julien Cristau:
> > BTW, this bug is still present in version 1:6.14.4-2.
> >
> Is it reproducible with a newer libgl1-mesa-dri?
Yes, it is. I installed libgl1-mesa-dri 8.0.2-1 from experimental & the
bug is still reproducible.
I can reproduce the c
On Mon, Apr 30, 2012 at 23:03:07 +0200, Stefan Nagy wrote:
> Dear Maintainer,
>
> is the backtrace I attached last time of any use? Should I file this bug
> against gnome-shell? However, I'd be glad to provide more infomation.
>
> BTW, this bug is still present in version 1:6.14.4-2.
>
Is it re
Dear Maintainer,
is the backtrace I attached last time of any use? Should I file this bug
against gnome-shell? However, I'd be glad to provide more infomation.
BTW, this bug is still present in version 1:6.14.4-2.
Thanks,
Stefan.
signature.asc
Description: This is a digitally signed message pa
Am Montag, den 16.04.2012, 20:50 +0200 schrieb Julien Cristau:
> > Program received signal SIGTERM, Terminated.
>
> So X is terminating normally. If gnome-shell is crashing, you should
> run gdb against that, not the X server…
OK, I see – thanks.
I don't know if this is a useful backtrace now;
On Mon, Apr 16, 2012 at 20:32:21 +0200, Stefan Nagy wrote:
> Program received signal SIGTERM, Terminated.
So X is terminating normally. If gnome-shell is crashing, you should
run gdb against that, not the X server…
Cheers,
Julien
signature.asc
Description: Digital signature
Am Montag, den 16.04.2012, 19:58 +0200 schrieb Julien Cristau:
> > Continuing.
> >
> > Program received signal SIGPIPE, Broken pipe.
>
> SIGPIPE is not a fatal signal, you need to tell gdb to ignore it, or
> hit continue.
Thanks! I'll attach the new backtrace.
Cheers,
Stefan.
Continuing.
Progr
On Mon, Apr 16, 2012 at 13:33:56 +0200, Stefan Nagy wrote:
> Sorry – now here's the backtrace…
> Continuing.
>
> Program received signal SIGPIPE, Broken pipe.
SIGPIPE is not a fatal signal, you need to tell gdb to ignore it, or
hit continue.
Cheers,
Julien
signature.asc
Description: Digital
Sorry – now here's the backtrace…
Continuing.
Program received signal SIGPIPE, Broken pipe.
0xb75f4430 in __kernel_vsyscall ()
#0 0xb75f4430 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb736455b in writev ()
from /lib/i386-linux-gnu/i686/cmov/libc.so.6
No symbol table info ava
11 matches
Mail list logo