[apport] kdm crashed with SIGSEGV in _pam_free_data()

Bug #99515 reported by Friedhelm Weidenhaupt
4
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: kdebase

it crashed while systemboot. i didn made any software or hardware changes before

ProblemType: Crash
Architecture: i386
Date: Fri Mar 30 17:07:23 2007
Disassembly: 0xb7c83840:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/kdm
Package: kdm 4:3.5.6-0ubuntu18
PackageArchitecture: i386
ProcCmdline: -:1
ProcCwd: /
ProcEnviron: PATH=/bin:/usr/bin:/sbin:/usr/sbin
Signal: 11
SourcePackage: kdebase
StacktraceTop:
 ?? ()
 _pam_free_data () from /lib/libpam.so.0
 pam_end () from /lib/libpam.so.0
 ?? ()
 ?? ()
Uname: Linux home 2.6.20-13-386 #2 Sun Mar 25 00:18:53 UTC 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
Friedhelm Weidenhaupt (schwede) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
_pam_free_data (pamh=0x80b5418, status=0) at pam_data.c:118
pam_end (pamh=0x80b5418, pam_status=0) at pam_end.c:27
SessionExit (status=34) at /build/buildd/kdebase-3.5.6/./kdm/backend/client.c:1658
ManageSession (d=0x80a84c8) at /build/buildd/kdebase-3.5.6/./kdm/backend/session.c:535

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Marco Maini (maini10) wrote :

Thanks for you report.

Changed in kdebase:
status: New → Confirmed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Does this still happen with KDE4?

Changed in kdebase:
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase:
importance: Undecided → Low
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.