Processed: retitle correctly

2013-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 692814 "X crash with gdm3 on boot and with kdm on first logout"
Bug #692814 [xserver-xorg] gdm3 is not staring normally
Changed Bug title to '"X crash with gdm3 on boot and with kdm on first logout"' 
from 'gdm3 is not staring normally'
> found 692814 1:7.7+1
Bug #692814 [xserver-xorg] "X crash with gdm3 on boot and with kdm on first 
logout"
Marked as found in versions xorg/1:7.7+1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
692814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.135832238324327.transcr...@bugs.debian.org



Processed (with 1 errors): reassigning to xorg

2013-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 692814 xserver-xorg
Bug #692814 [gdm3] gdm3 is not staring normally
Bug reassigned from package 'gdm3' to 'xserver-xorg'.
No longer marked as found in versions gdm3/3.6.1-1 and gdm3/3.6.1-2.
Ignoring request to alter fixed versions of bug #692814 to the same values 
previously set
> reassign 692814 "X crash with gdm3 on boot and with kdm on first logout"
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
692814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.135832153919238.transcr...@bugs.debian.org



Unidentified subject!

2013-01-15 Thread bounce-debian-x=archive=mail-archive . com


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/ca+cf-b9hwphguho3cenecrrobeulru8em0667vihjsh8o2l...@mail.gmail.com



Bug#698197: forwarded bug address

2013-01-15 Thread Will Set
https://bugs.freedesktop.org/show_bug.cgi?id=59436

thankyou


Bug#698229: [Intel 965G] GPU Hangs (possibly bug #608782 duplicate)

2013-01-15 Thread Julien Cristau
On Tue, Jan 15, 2013 at 16:34:25 +0100, Martin Bruset Solberg wrote:

> [  3697.419] (EE) intel(0): Detected a hung GPU, disabling acceleration.
> [  3697.435] (EE) intel(0): When reporting this, please include
> i915_error_state from debugfs and the full dmesg.
> 
See above...  Also
https://01.org/linuxgraphics/documentation/collecting-gpu-state-hangs-0

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#698229: [Intel 965G] GPU Hangs (possibly bug #608782 duplicate)

2013-01-15 Thread Martin Bruset Solberg
Package: xserver-xorg-video-intel
Version: 2:2.20.14-1

In X (I'm using Openbox with no DM), the mouse pointer suddenly
freezes. The mouse seems to actually be moving (buttons highlight when
rolled over), but the pointer is frozen in one spot. The system is
still usable via keyboard, however, if I try to switch to any TTY, it
freezes completely. The same happens if I try to kill X via
CTRL+ALT+BACKSPACE or kill the X-process. The X.org-log says that the
GPU hangs
I'm not able to tell what triggers this hang, it appears to happen
randomly from normal use of the GUI.

I'm using LinuxBBQ (Debian Unstable), with xserver-xorg-video-intel
package from Experimental. I had the same problem with the package in
Unstable. The problem may have been more frequent in the Unstable
version.

I'll paste the Xorg-log. If there's anything else I should attach, let me know.

[58.039]
X.Org X Server 1.12.4
Release Date: 2012-08-27
[58.039] X Protocol Version 11, Revision 0
[58.039] Build Operating System: Linux 3.2.0-4.drm-amd64 x86_64 Debian
[58.039] Current Operating System: Linux lynet
3.7-2.towo-siduction-amd64 #1 SMP PREEMPT Sat Jan 12 13:52:15 UTC 2013
x86_64
[58.040] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-3.7-2.towo-siduction-amd64
root=UUID=fca240e0-3568-42c6-8a59-0c1e4c01bec1 ro quiet
init=/bin/systemd
[58.040] Build Date: 29 November 2012  07:18:16PM
[58.040] xorg-server 2:1.12.4-4 (Julien Cristau )
[58.040] Current version of pixman: 0.26.0
[58.040]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[58.040] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[58.040] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 15
15:22:37 2013
[58.078] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[58.085] (==) No Layout section.  Using the first Screen section.
[58.085] (==) No screen section available. Using defaults.
[58.086] (**) |-->Screen "Default Screen Section" (0)
[58.086] (**) |   |-->Monitor ""
[58.086] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[58.086] (==) Automatically adding devices
[58.086] (==) Automatically enabling devices
[58.151] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[58.151]Entry deleted from font path.
[58.164] (WW) The directory
"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not exist.
[58.164]Entry deleted from font path.
[58.164] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[58.164] (==) ModulePath set to "/usr/lib/xorg/modules"
[58.164] (II) The server relies on udev to provide the list of
input devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[58.164] (II) Loader magic: 0x7f5b633e4ae0
[58.164] (II) Module ABI versions:
[58.164]X.Org ANSI C Emulation: 0.4
[58.164]X.Org Video Driver: 12.1
[58.164]X.Org XInput driver : 16.0
[58.164]X.Org Server Extension : 6.0
[58.165] (--) PCI:*(0:0:2:0) 8086:29a2:a0a0:062a rev 2, Mem @
0xfd80/1048576, 0xd000/268435456, I/O @ 0xff00/8
[58.165] (II) Open ACPI successful (/var/run/acpid.socket)
[58.165] (II) LoadModule: "extmod"
[58.211] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[58.226] (II) Module extmod: vendor="X.Org Foundation"
[58.226]compiled for 1.12.4, module version = 1.0.0
[58.226]Module class: X.Org Server Extension
[58.226]ABI class: X.Org Server Extension, version 6.0
[58.226] (II) Loading extension SELinux
[58.226] (II) Loading extension MIT-SCREEN-SAVER
[58.226] (II) Loading extension XFree86-VidModeExtension
[58.226] (II) Loading extension XFree86-DGA
[58.226] (II) Loading extension DPMS
[58.226] (II) Loading extension XVideo
[58.226] (II) Loading extension XVideo-MotionCompensation
[58.226] (II) Loading extension X-Resource
[58.226] (II) LoadModule: "dbe"
[58.226] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[58.227] (II) Module dbe: vendor="X.Org Foundation"
[58.227]compiled for 1.12.4, module version = 1.0.0
[58.227]Module class: X.Org Server Extension
[58.227]ABI class: X.Org Server Extension, version 6.0
[58.227] (II) Loading extension DOUBLE-BUFFER
[58.227] (II) LoadModule: "glx"
[58.227] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[58.234] (II) Module glx: vendor="X.Org Foundation"
[58.234]compiled for 1.1

Bug#695757: xserver-xorg-video-radeon: Memory leak in Xorg when using oxygen-gtk as gtk2 theme

2013-01-15 Thread Michel Dänzer
On Mon, 2013-01-14 at 23:29 +0100, bluebubble wrote: 
> Il 13/12/12 10:46, Michel Dänzer ha scritto:
> > If yes, you'll need to investigate the leak with valgrind or some other
> > tool for this. Note that such tools may not help on X server shutdown,
> > as the X server may still clean up the memory at that point. I think you
> > can get an intermittent leak report from valgrind by sending it some
> > signal, but I don't remember the details.
> >
> >
> 
> sorry if I'm a bit late with the response.
> 
> I've run Xorg with valgrind using this command:
> /usr/bin/valgrind -v --track-origins=yes --leak-check=full 
> --show-reachable=yes --log-file=/tmp/X.log /usr/bin/Xorg $@
> 
> Attached there is the log.

[...]

> ==27767== LEAK SUMMARY:
> ==27767==definitely lost: 88,974 bytes in 367 blocks
> ==27767==indirectly lost: 68,924 bytes in 381 blocks
> ==27767==  possibly lost: 0 bytes in 0 blocks
> ==27767==still reachable: 271,956 bytes in 2,656 blocks
> ==27767== suppressed: 0 bytes in 0 blocks

As you can see, the X server hardly leaked any memory on exit. You
really need to trigger valgrind to print information about where memory
was allocated from while memory usage appears high during runtime.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast |  Debian, X and DRI developer


--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1358237775.29800.16.camel@thor.local