(SOLVED) Re: logging out fails in KDE4 (debian testing)

[Γιώργος Πάλλας]

Γιώργος Πάλλας wrote:

Justin Piszcz wrote:
  

Yeah, it looks good, looks like it is an Xorg/Intel problem from the
trace, adding x...@lists.freedesktop.org to the cc list to see if this
report is sufficient or if they would like you to submit the bug
somewhere specific (bug tracker, etc).




OK, thanks for all your help!
I submitted it also at debian bugs, as extra info to bug: 539064.


Giorgos

  


They informed me that in version 2.9.0 the bug has been resolved...




smime.p7s
Description: S/MIME Cryptographic Signature

Re: logging out fails in KDE4 (debian testing)

[Γιώργος Πάλλας]

Justin Piszcz wrote:
> Yeah, it looks good, looks like it is an Xorg/Intel problem from the
> trace, adding x...@lists.freedesktop.org to the cc list to see if this
> report is sufficient or if they would like you to submit the bug
> somewhere specific (bug tracker, etc).
>

OK, thanks for all your help!
I submitted it also at debian bugs, as extra info to bug: 539064.


Giorgos



smime.p7s
Description: S/MIME Cryptographic Signature

Re: logging out fails in KDE4 (debian testing)

[Justin Piszcz]

Yeah, it looks good, looks like it is an Xorg/Intel problem from the 
trace, adding x...@lists.freedesktop.org to the cc list to see if this 
report is sufficient or if they would like you to submit the bug somewhere 
specific (bug tracker, etc).


On Thu, 1 Oct 2009, ??? ?? wrote:


Justin Piszcz wrote:



On Thu, 1 Oct 2009, ??? ?? wrote:


Justin Piszcz wrote:



On Thu, 1 Oct 2009, ??? ?? wrote:


Justin Piszcz wrote:

I installed xserver-xorg-video-intel-dbg but I don't know what to do
now. I reproduced it, and both at dmesg and /var/log/Xorg.log I get
exactly the same things that I posted earlier. With dbg, should I do
something different? Where does it write its trace?

Giorgos




Run ulimit -a and see if you have core files set to 0 or unlimited.

You want to run gdb against the core and run bt full for a full
backtrace and include that along with the logs for your report.

$ gdb application core.Xorg

gdb> bt full

Send this & logs in the bug report.





ulimit -a gives me:
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 16382
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 1024
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) unlimited
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Other than that, I do not understand your instructions... For my
case where the 'application' crashing is the Xserver, how will I
run gdb on it?




You need to enable core files.

In a console:
1. ulimit -c unlimited
2. then reproduce the problem in that console (it should generate a
core file)
3. find / -type f | grep -i core  (it is normally in the directory
where you run the program)
4. gdb /usr/bin/Xorg /path/to/core
5. bt full
6. Send that in a bug report.

Justin.




Sorry to bother you again (maybe this advanced stuff should be left
to the advanced users but I would like to help with this bug...), but
the second step troubles me.

This thread goes about the xserver crashing when the user is logging
out of X. So, how should I do it? How should I start the xserver from
a console (not in X), so that when it crashes it leaves a core file?

sorry for my ignorance...
G.



Either enable global core files and reboot or run startx from the
command line, then logout of KDE and you should have a core file.

Justin.


Thanks for the help!
Does this look like it should? Is it useful for a bugreport?

mordor:~/tmp/xcrash# gdb /usr/bin/Xorg ./core
GNU gdb (GDB) 6.8.50.20090628-cvs-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute
it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for
details.
This GDB was configured as
"x86_64-linux-gnu".
For bug reporting instructions, please
see:
...

(no debugging symbols
found)

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/libpciaccess.so.0...(no debugging symbols
found)...done.
Loaded symbols for
/usr/lib/libpciaccess.so.0
Reading symbols from /lib/libdl.so.2...(no debugging symbols
found)...done.
Loaded symbols for
/lib/libdl.so.2
Reading symbols from /usr/lib/libXfont.so.1...(no debugging symbols
found)...done.
Loaded symbols for
/usr/lib/libXfont.so.1
Reading symbols from /usr/lib/libXau.so.6...(no debugging symbols
found)...done.
Loaded symbols for
/usr/lib/libXau.so.6
Reading symbols from /usr/lib/libfontenc.so.1...(no debugging symbols
found)...done.
Loaded symbols for
/usr/lib/libfontenc.so.1
Reading symbols from /usr/lib/libpixman-1.so.0...(no debugging symbols
found)...done.
Loaded symbols for
/usr/lib/libpixman-1.so.0
Reading symbols from /usr/lib/libhal.so.1...(no debugging symbols
found)...done.
Loaded symbols for
/usr/lib/libhal.so.1
Reading symbols from /lib/libdbus-1.so.3...(no debugging symbols
found)...done.
Loaded symbols for
/lib/libdbus-1.so.3
Reading symbols from /lib/libpthread.so.0...(no debugging symbols
found)...done.
Loaded symbols for
/lib/libpthread.so.0
Reading symbols from /usr/lib/libXdmcp.so.6...(no debugging symbols
found)...done.
Loaded symbols for
/usr/lib/libXdmcp.so.6
Reading symbols from /usr/lib/libgcrypt.so.11...(no debugging symbols
found)...done.
Loaded symbols for
/usr/lib/libgcrypt.so.11
Reading symbols from /lib/libaudit.so.0...(no debugging symbols
found)...done.
Loaded symbols for
/lib/libaudit.so.0
Reading symbols from /lib/libselinux.so.1...(no debugging symbo

Re: logging out fails in KDE4 (debian testing)

[Γιώργος Πάλλας]

Justin Piszcz wrote:
>
>
> On Thu, 1 Oct 2009, ??? ?? wrote:
>
>> Justin Piszcz wrote:
>>>
>>>
>>> On Thu, 1 Oct 2009, ??? ?? wrote:
>>>
 Justin Piszcz wrote:
>> I installed xserver-xorg-video-intel-dbg but I don't know what to do
>> now. I reproduced it, and both at dmesg and /var/log/Xorg.log I get
>> exactly the same things that I posted earlier. With dbg, should I do
>> something different? Where does it write its trace?
>>
>> Giorgos
>>
>>
>
> Run ulimit -a and see if you have core files set to 0 or unlimited.
>
> You want to run gdb against the core and run bt full for a full
> backtrace and include that along with the logs for your report.
>
> $ gdb application core.Xorg
>
> gdb> bt full
>
> Send this & logs in the bug report.
>
>


 ulimit -a gives me:
 core file size  (blocks, -c) 0
 data seg size   (kbytes, -d) unlimited
 scheduling priority (-e) 0
 file size   (blocks, -f) unlimited
 pending signals (-i) 16382
 max locked memory   (kbytes, -l) 64
 max memory size (kbytes, -m) unlimited
 open files  (-n) 1024
 pipe size(512 bytes, -p) 8
 POSIX message queues (bytes, -q) 819200
 real-time priority  (-r) 0
 stack size  (kbytes, -s) 8192
 cpu time   (seconds, -t) unlimited
 max user processes  (-u) unlimited
 virtual memory  (kbytes, -v) unlimited
 file locks  (-x) unlimited

 Other than that, I do not understand your instructions... For my
 case where the 'application' crashing is the Xserver, how will I
 run gdb on it?


>>>
>>> You need to enable core files.
>>>
>>> In a console:
>>> 1. ulimit -c unlimited
>>> 2. then reproduce the problem in that console (it should generate a
>>> core file)
>>> 3. find / -type f | grep -i core  (it is normally in the directory
>>> where you run the program)
>>> 4. gdb /usr/bin/Xorg /path/to/core
>>> 5. bt full
>>> 6. Send that in a bug report.
>>>
>>> Justin.
>>>
>>>
>>
>> Sorry to bother you again (maybe this advanced stuff should be left
>> to the advanced users but I would like to help with this bug...), but
>> the second step troubles me.
>>
>> This thread goes about the xserver crashing when the user is logging
>> out of X. So, how should I do it? How should I start the xserver from
>> a console (not in X), so that when it crashes it leaves a core file?
>>
>> sorry for my ignorance...
>> G.
>>
>
> Either enable global core files and reboot or run startx from the
> command line, then logout of KDE and you should have a core file.
>
> Justin.

Thanks for the help!
Does this look like it should? Is it useful for a bugreport?

mordor:~/tmp/xcrash# gdb /usr/bin/Xorg ./core
GNU gdb (GDB) 6.8.50.20090628-cvs-debian
Copyright (C) 2009 Free Software Foundation, Inc.   
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute
it.  
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"  
and "show warranty" for
details.
This GDB was configured as
"x86_64-linux-gnu".  
For bug reporting instructions, please
see: 
...  

(no debugging symbols
found)

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/libpciaccess.so.0...(no debugging symbols
found)...done.
Loaded symbols for
/usr/lib/libpciaccess.so.0
Reading symbols from /lib/libdl.so.2...(no debugging symbols
found)...done.  
Loaded symbols for
/lib/libdl.so.2   
Reading symbols from /usr/lib/libXfont.so.1...(no debugging symbols
found)...done.   
Loaded symbols for
/usr/lib/libXfont.so.1
Reading symbols from /usr/lib/libXau.so.6...(no debugging symbols
found)...done. 
Loaded symbols for
/usr/lib/libXau.so.6  
Reading symbols from /usr/lib/libfontenc.so.1...(no debugging symbols
found)...done. 
Loaded symbols for
/usr/lib/libfontenc.so.1  
Reading symbols from /usr/lib/libpixman-1.so.0...(no debugging symbols
found)...done.
Loaded symbols for
/usr/lib/libpixman-1.so.0 
Reading symbols from /usr/lib/libhal.so.1...(no debugging symbols
found)...done. 
Loaded symbols for
/usr/lib/libhal.so.1  
Reading symbols from /lib/libdbus-1.so.3...(no debugging sy

Re: logging out fails in KDE4 (debian testing)

[Justin Piszcz]

On Thu, 1 Oct 2009, ??? ?? wrote:


Justin Piszcz wrote:



On Thu, 1 Oct 2009, ??? ?? wrote:


Justin Piszcz wrote:

I installed xserver-xorg-video-intel-dbg but I don't know what to do
now. I reproduced it, and both at dmesg and /var/log/Xorg.log I get
exactly the same things that I posted earlier. With dbg, should I do
something different? Where does it write its trace?

Giorgos




Run ulimit -a and see if you have core files set to 0 or unlimited.

You want to run gdb against the core and run bt full for a full backtrace 
and include that along with the logs for your report.


$ gdb application core.Xorg

gdb> bt full

Send this & logs in the bug report.





ulimit -a gives me:
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 16382
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 1024
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) unlimited
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Other than that, I do not understand your instructions... For my case 
where the 'application' crashing is the Xserver, how will I run gdb on it?





You need to enable core files.

In a console:
1. ulimit -c unlimited
2. then reproduce the problem in that console (it should generate a core 
file)
3. find / -type f | grep -i core  (it is normally in the directory where 
you run the program)

4. gdb /usr/bin/Xorg /path/to/core
5. bt full
6. Send that in a bug report.

Justin.




Sorry to bother you again (maybe this advanced stuff should be left to the 
advanced users but I would like to help with this bug...), but the second 
step troubles me.


This thread goes about the xserver crashing when the user is logging out of 
X. So, how should I do it? How should I start the xserver from a console (not 
in X), so that when it crashes it leaves a core file?


sorry for my ignorance...
G.



Either enable global core files and reboot or run startx from the command 
line, then logout of KDE and you should have a core file.


Justin.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: logging out fails in KDE4 (debian testing)

[Γιώργος Πάλλας]

Justin Piszcz wrote:



On Thu, 1 Oct 2009, ??? ?? wrote:


Justin Piszcz wrote:

I installed xserver-xorg-video-intel-dbg but I don't know what to do
now. I reproduced it, and both at dmesg and /var/log/Xorg.log I get
exactly the same things that I posted earlier. With dbg, should I do
something different? Where does it write its trace?

Giorgos




Run ulimit -a and see if you have core files set to 0 or unlimited.

You want to run gdb against the core and run bt full for a full 
backtrace and include that along with the logs for your report.


$ gdb application core.Xorg

gdb> bt full

Send this & logs in the bug report.





ulimit -a gives me:
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 16382
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 1024
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) unlimited
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Other than that, I do not understand your instructions... For my case 
where the 'application' crashing is the Xserver, how will I run gdb 
on it?





You need to enable core files.

In a console:
1. ulimit -c unlimited
2. then reproduce the problem in that console (it should generate a 
core file)
3. find / -type f | grep -i core  (it is normally in the directory 
where you run the program)

4. gdb /usr/bin/Xorg /path/to/core
5. bt full
6. Send that in a bug report.

Justin.




Sorry to bother you again (maybe this advanced stuff should be left to 
the advanced users but I would like to help with this bug...), but the 
second step troubles me.


This thread goes about the xserver crashing when the user is logging out 
of X. So, how should I do it? How should I start the xserver from a 
console (not in X), so that when it crashes it leaves a core file?


sorry for my ignorance...
G.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: logging out fails in KDE4 (debian testing)

[Justin Piszcz]

On Thu, 1 Oct 2009, ??? ?? wrote:


Justin Piszcz wrote:

I installed xserver-xorg-video-intel-dbg but I don't know what to do
now. I reproduced it, and both at dmesg and /var/log/Xorg.log I get
exactly the same things that I posted earlier. With dbg, should I do
something different? Where does it write its trace?

Giorgos




Run ulimit -a and see if you have core files set to 0 or unlimited.

You want to run gdb against the core and run bt full for a full backtrace 
and include that along with the logs for your report.


$ gdb application core.Xorg

gdb> bt full

Send this & logs in the bug report.





ulimit -a gives me:
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 16382
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 1024
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) unlimited
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Other than that, I do not understand your instructions... For my case where 
the 'application' crashing is the Xserver, how will I run gdb on it?





You need to enable core files.

In a console:
1. ulimit -c unlimited
2. then reproduce the problem in that console (it should generate a core file)
3. find / -type f | grep -i core  (it is normally in the directory where you 
run the program)
4. gdb /usr/bin/Xorg /path/to/core
5. bt full
6. Send that in a bug report.

Justin.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: logging out fails in KDE4 (debian testing)

[Γιώργος Πάλλας]

Justin Piszcz wrote:

I installed xserver-xorg-video-intel-dbg but I don't know what to do
now. I reproduced it, and both at dmesg and /var/log/Xorg.log I get
exactly the same things that I posted earlier. With dbg, should I do
something different? Where does it write its trace?

Giorgos




Run ulimit -a and see if you have core files set to 0 or unlimited.

You want to run gdb against the core and run bt full for a full 
backtrace and include that along with the logs for your report.


$ gdb application core.Xorg

gdb> bt full

Send this & logs in the bug report.





ulimit -a gives me:
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 16382
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 1024
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) unlimited
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Other than that, I do not understand your instructions... For my case 
where the 'application' crashing is the Xserver, how will I run gdb on it?




smime.p7s
Description: S/MIME Cryptographic Signature

Re: logging out fails in KDE4 (debian testing)

[Justin Piszcz]

On Wed, 30 Sep 2009, ??? ?? wrote:


Sjoerd Hardeman wrote:

??? ?? schreef:

Matthew Moore wrote:

On Saturday September 26 2009 9:39:43 am ??? ?? wrote:


Does this happen to anybody else? Should I report it as a bug?
I googled it and found several references of the problem, although old
(around April 2009).


Are you using an intel graphics chip? This was happening on my
laptop about 6 months ago, and I finally tracked it down to the
intel driver crashing on logout. I use kdm, so a workaround for me
was to add the line

TerminateServer=true

to the [X-:*-Core] section of the file /etc/kde4/kdm/kdmrc.


Thanks for the tip, that worked!

I have indeed an intel chip and I wonder which package has the bug, in
order to report it.
(EE) intel(0): Failed to initialize kernel memory manager

That must be the xserver-xorg-video-intel. First install the
xserver-xorg-video-intel-dbg, then reproduce. That will probably give
a more helpful backtrace for the people who have to fix this problem.

Sjoerd



I installed xserver-xorg-video-intel-dbg but I don't know what to do
now. I reproduced it, and both at dmesg and /var/log/Xorg.log I get
exactly the same things that I posted earlier. With dbg, should I do
something different? Where does it write its trace?

Giorgos




Run ulimit -a and see if you have core files set to 0 or unlimited.

You want to run gdb against the core and run bt full for a full backtrace 
and include that along with the logs for your report.


$ gdb application core.Xorg

gdb> bt full

Send this & logs in the bug report.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: logging out fails in KDE4 (debian testing)

[Γιώργος Πάλλας]

Sjoerd Hardeman wrote:
> Γιώργος Πάλλας schreef:
>> Matthew Moore wrote:
>>> On Saturday September 26 2009 9:39:43 am Γιώργος Πάλλας wrote:
>>>  
 Does this happen to anybody else? Should I report it as a bug?
 I googled it and found several references of the problem, although old
 (around April 2009).
 
>>> Are you using an intel graphics chip? This was happening on my
>>> laptop about 6 months ago, and I finally tracked it down to the
>>> intel driver crashing on logout. I use kdm, so a workaround for me
>>> was to add the line
>>>
>>> TerminateServer=true
>>>
>>> to the [X-:*-Core] section of the file /etc/kde4/kdm/kdmrc.
>>>
>> Thanks for the tip, that worked!
>>
>> I have indeed an intel chip and I wonder which package has the bug, in
>> order to report it.
>> (EE) intel(0): Failed to initialize kernel memory manager
> That must be the xserver-xorg-video-intel. First install the
> xserver-xorg-video-intel-dbg, then reproduce. That will probably give
> a more helpful backtrace for the people who have to fix this problem.
>
> Sjoerd
>

I installed xserver-xorg-video-intel-dbg but I don't know what to do
now. I reproduced it, and both at dmesg and /var/log/Xorg.log I get
exactly the same things that I posted earlier. With dbg, should I do
something different? Where does it write its trace?

Giorgos



smime.p7s
Description: S/MIME Cryptographic Signature

Re: logging out fails in KDE4 (debian testing)

[Matthew Moore]

On Wednesday September 30 2009 9:45:19 am Γιώργος Πάλλας wrote:
> Matthew Moore wrote:
> > On Saturday September 26 2009 9:39:43 am Γιώργος Πάλλας wrote:
> >> Does this happen to anybody else? Should I report it as a bug?
> >> I googled it and found several references of the problem, although old
> >> (around April 2009).
> >
> > Are you using an intel graphics chip? This was happening on my laptop
> > about 6 months ago, and I finally tracked it down to the intel driver
> > crashing on logout. I use kdm, so a workaround for me was to add the line
> >
> > TerminateServer=true
> >
> > to the [X-:*-Core] section of the file /etc/kde4/kdm/kdmrc.
> >
> > Hope that helps,
> > MM
> 
> Thanks for the tip, that worked!
> 
> I have indeed an intel chip and I wonder which package has the bug, in
> order to report it.

I filed a bug report a few months ago and someone replied to the report with 
that suggestion. There has been no activity since then. I filed the report 
against the package xserver-xorg-video-intel.

MM


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: logging out fails in KDE4 (debian testing)

[Sjoerd Hardeman]

Γιώργος Πάλλας schreef:

Matthew Moore wrote:

On Saturday September 26 2009 9:39:43 am Γιώργος Πάλλας wrote:
  

Does this happen to anybody else? Should I report it as a bug?
I googled it and found several references of the problem, although old
(around April 2009).

Are you using an intel graphics chip? This was happening on my laptop about 6 
months ago, and I finally tracked it down to the intel driver crashing on 
logout. I use kdm, so a workaround for me was to add the line


TerminateServer=true

to the [X-:*-Core] section of the file /etc/kde4/kdm/kdmrc.


Thanks for the tip, that worked!

I have indeed an intel chip and I wonder which package has the bug, in
order to report it.
(EE) intel(0): Failed to initialize kernel memory manager
That must be the xserver-xorg-video-intel. First install the 
xserver-xorg-video-intel-dbg, then reproduce. That will probably give a 
more helpful backtrace for the people who have to fix this problem.


Sjoerd



signature.asc
Description: OpenPGP digital signature

Re: logging out fails in KDE4 (debian testing)

[Γιώργος Πάλλας]

Matthew Moore wrote:
> On Saturday September 26 2009 9:39:43 am Γιώργος Πάλλας wrote:
>   
>> Does this happen to anybody else? Should I report it as a bug?
>> I googled it and found several references of the problem, although old
>> (around April 2009).
>> 
>
> Are you using an intel graphics chip? This was happening on my laptop about 6 
> months ago, and I finally tracked it down to the intel driver crashing on 
> logout. I use kdm, so a workaround for me was to add the line
>
> TerminateServer=true
>
> to the [X-:*-Core] section of the file /etc/kde4/kdm/kdmrc.
>
> Hope that helps,
> MM
>
>
>   

Thanks for the tip, that worked!

I have indeed an intel chip and I wonder which package has the bug, in
order to report it.

Any ideas?

When logging out, the xserver crashes with these messages (from Xorg.log)
...
...
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Macintosh mouse button emulation: Close
(II) UnloadModule: "evdev"
(II) UnloadModule: "synaptics"
(II) PS/2 Mouse: Close
(II) UnloadModule: "evdev"
(II) Microsoft Microsoft 3-Button Mouse with IntelliEye(TM): Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Open ACPI successful (/var/run/acpid.socket)
(II) APM registered successfully
(II) intel(0): Kernel reported 1264128 total, 1 used
(II) intel(0): I830CheckAvailableMemory: 5056508 kB available
(II) intel(0): [DRI2] Setup complete
(**) intel(0): Framebuffer compression enabled
(**) intel(0): Tiling enabled
(**) intel(0): SwapBuffers wait enabled
(EE) intel(0): Failed to initialize kernel memory manager
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers.

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x26) [0x4ee256]
1: /usr/bin/X(xf86SigHandler+0x39) [0x4840b9]
2: /lib/libc.so.6 [0x7f4952243db0]
3: /usr/lib/libdrm_intel.so.1(drm_intel_bo_alloc+0x3) [0x7f49508129d3]
4:
/usr/lib/xorg/modules/drivers//intel_drv.so(i830_allocate_memory+0x2c6)
[0x7f4950a4f846]
5:
/usr/lib/xorg/modules/drivers//intel_drv.so(i830_allocate_2d_memory+0xb4)
[0x7f4950a50144]
6: /usr/lib/xorg/modules/drivers//intel_drv.so [0x7f4950a45d57]
7: /usr/lib/xorg/modules/drivers//intel_drv.so [0x7f4950a4a3b8]
8: /usr/bin/X(AddScreen+0x1c6) [0x432ac6]
9: /usr/bin/X(InitOutput+0x241) [0x46d2a1]
10: /usr/bin/X(main+0x200) [0x4331d0]
11: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f49522305c6]
12: /usr/bin/X [0x432819]

Fatal server error:
Caught signal 11.  Server aborting



and last messages from dmesg have:

[ 1191.247689] [drm:gm45_get_vblank_counter] *ERROR* trying to get
vblank count for disabled pipe 0
[ 1216.201891] [drm:gm45_get_vblank_counter] *ERROR* trying to get
vblank count for disabled pipe 0
[ 1216.216624] mtrr: no MTRR for d000,1000 found
[ 1223.554842] [drm:gm45_get_vblank_counter] *ERROR* trying to get
vblank count for disabled pipe 0
[ 1223.567989] mtrr: no MTRR for d000,1000 found
[ 1588.000274] CE: hpet increasing min_delta_ns to 15000 nsec
[ 1598.308035] [drm:gm45_get_vblank_counter] *ERROR* trying to get
vblank count for disabled pipe 0
[ 1598.321239] mtrr: no MTRR for d000,1000 found
[ 1603.223533] [drm:gm45_get_vblank_counter] *ERROR* trying to get
vblank count for disabled pipe 0
[ 1613.874329] mtrr: no MTRR for d000,1000 found
[ 1635.653315] [drm:gm45_get_vblank_counter] *ERROR* trying to get
vblank count for disabled pipe 0
[ 1701.928449] [drm:gm45_get_vblank_counter] *ERROR* trying to get
vblank count for disabled pipe 0
[ 1701.941433] mtrr: no MTRR for d000,1000 found
[ 1701.985047] Xorg[7926]: segfault at 5f15 ip 00499ea2 sp
7fff60d9f9e0 error 4 in Xorg[40+1bc000]





smime.p7s
Description: S/MIME Cryptographic Signature

Re: logging out fails in KDE4 (debian testing)

[Matthew Moore]

On Saturday September 26 2009 9:39:43 am Γιώργος Πάλλας wrote:
> Does this happen to anybody else? Should I report it as a bug?
> I googled it and found several references of the problem, although old
> (around April 2009).

Are you using an intel graphics chip? This was happening on my laptop about 6 
months ago, and I finally tracked it down to the intel driver crashing on 
logout. I use kdm, so a workaround for me was to add the line

TerminateServer=true

to the [X-:*-Core] section of the file /etc/kde4/kdm/kdmrc.

Hope that helps,
MM


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

logging out fails in KDE4 (debian testing)

[Γιώργος Πάλλας]

After updating to the latest versions of packages of debian testing
about 2-3 days ago, I noticed that the log out function has stopped
working. It plays the log out sound, and then a black console screen,
and absolutely no response to any combination of keys (ctrl-alt-del,
ctrl-alt-f{1-5}). But it is not frozen, because if I press the on/off
button of the laptop, it begins the shutdown process.

Does this happen to anybody else? Should I report it as a bug?
I googled it and found several references of the problem, although old
(around April 2009).

Cheers,
G.


smime.p7s
Description: S/MIME Cryptographic Signature