I have successfully produced this crash again with lightdm
0.3.7-0ubuntu2, as requested. I've filed a new report (private duplicate
bug 796521) from that crash. I'm removing the CoreDump.gz attachment in
this bug and marking it public (I've looked over the data in the other
files and it doesn't look like login credentials, and since it's my
system, I can choose to take on that minimal level of risk). Hopefully
that will make this bug easier to confirm and otherwise work on, while
bug 796521 will still have all the automatically attached information
(so perhaps "Apport retracing service" will be able to improve its stack
trace). As with this bug, I've subscribed Jean-Baptiste Lallement and
Robert Ancell to bug 796521 so they have full access to it even though
it's private.
I have tried to produce this crash on another Oneiric i386 system on
identical (virtual) hardware, so as to produce a complete bug report
including core dump that I know doesn't contain any passwords I actually
use on other machines. I have not succeeded, so far. So it seems that
there is some undiscovered factor involved in determining whether or not
this crash occurs.
** Changed in: lightdm (Ubuntu)
Status: Incomplete => New
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/795324/+attachment/2163086/+files/CoreDump.gz
** Visibility changed to: Public
** Description changed:
Binary package hint: lightdm
On an Oneiric i386 system, I updated a number of packages yesterday
(/var/log/dpkg.log attached compressed as dpkg.log.gz), and was given
the choice between remaining with gdm (2.32.1-0ubuntu5) as my display
manager, or switching to lightdm (0.3.7-0ubuntu1). I decided to try out
lightdm. It appeared to work without problems, and defaulted to my
default gdm session type as desired. But immediately after log in (to a
unity-2d session), Apport informed me that lightdm had crashed with with
SIGSEGV in g_child_watch_dispatch().
I don't have any more information, except that this bug looks similar to
bug 795050, which is a SIGSEGV in a similar bug different dispatch
function (g_main_context_dispatch()). But I did *not* also experience
bug 795050. In that bug, Jean-Baptiste Lallement posted
(https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/795050/comments/2)
saying he got it at the same time as bug 795062, so perhaps this bug is
actually a duplicate of (inaccessible to me, thus presumably private)
bug 795062.
- Since this crash was in a display manager, which provides a login
- screen, I am concerned about possible disclosure of sensitive
- information, so I'm keeping this bug private until it is processed by
- "Apport retracting service" or a bug triager (or I myself) examine it
- and determine that it's probably safe. However, I am manually
- subscribing Jean-Baptiste Lallement to this bug, so he can compare it to
- bug 795062.
-
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: lightdm 0.3.7-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
Uname: Linux 2.6.39-3-generic i686
Architecture: i386
Date: Wed Jun 8 19:14:16 2011
ExecutablePath: /usr/bin/lightdm
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110604)
ProcCmdline: lightdm
ProcEnviron:
- PATH=(custom, no user)
- LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ LANG=en_US.UTF-8
SegvAnalysis:
- Segfault happened at: 0x804bb73: mov 0x20(%eax),%eax
- PC (0x0804bb73) ok
- source "0x20(%eax)" (0xaaaaaaca) not located in a known VMA region (needed
readable region)!
- destination "%eax" ok
+ Segfault happened at: 0x804bb73: mov 0x20(%eax),%eax
+ PC (0x0804bb73) ok
+ source "0x20(%eax)" (0xaaaaaaca) not located in a known VMA region (needed
readable region)!
+ destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
- ?? ()
- g_child_watch_dispatch (source=0x9c7fbc0, callback=0x804bb10,
user_data=0x9c81000) at /build/buildd/glib2.0-2.29.4/./glib/gmain.c:4471
- g_main_dispatch (context=0x9c5b850) at
/build/buildd/glib2.0-2.29.4/./glib/gmain.c:2477
- g_main_context_dispatch (context=0x9c5b850) at
/build/buildd/glib2.0-2.29.4/./glib/gmain.c:3050
- g_main_context_iterate (context=0x9c5b850, block=1448320, dispatch=1,
self=<value optimized out>) at /build/buildd/glib2.0-2.29.4/./glib/gmain.c:3128
+ ?? ()
+ g_child_watch_dispatch (source=0x9c7fbc0, callback=0x804bb10,
user_data=0x9c81000) at /build/buildd/glib2.0-2.29.4/./glib/gmain.c:4471
+ g_main_dispatch (context=0x9c5b850) at
/build/buildd/glib2.0-2.29.4/./glib/gmain.c:2477
+ g_main_context_dispatch (context=0x9c5b850) at
/build/buildd/glib2.0-2.29.4/./glib/gmain.c:3050
+ g_main_context_iterate (context=0x9c5b850, block=1448320, dispatch=1,
self=<value optimized out>) at /build/buildd/glib2.0-2.29.4/./glib/gmain.c:3128
Title: lightdm crashed with SIGSEGV in g_child_watch_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
** Description changed:
Binary package hint: lightdm
On an Oneiric i386 system, I updated a number of packages yesterday
(/var/log/dpkg.log attached compressed as dpkg.log.gz), and was given
the choice between remaining with gdm (2.32.1-0ubuntu5) as my display
manager, or switching to lightdm (0.3.7-0ubuntu1). I decided to try out
lightdm. It appeared to work without problems, and defaulted to my
default gdm session type as desired. But immediately after log in (to a
unity-2d session), Apport informed me that lightdm had crashed with with
SIGSEGV in g_child_watch_dispatch().
I don't have any more information, except that this bug looks similar to
bug 795050, which is a SIGSEGV in a similar bug different dispatch
function (g_main_context_dispatch()). But I did *not* also experience
- bug 795050. In that bug, Jean-Baptiste Lallement posted
- (https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/795050/comments/2)
- saying he got it at the same time as bug 795062, so perhaps this bug is
- actually a duplicate of (inaccessible to me, thus presumably private)
- bug 795062.
+ bug 795050.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: lightdm 0.3.7-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
Uname: Linux 2.6.39-3-generic i686
Architecture: i386
Date: Wed Jun 8 19:14:16 2011
ExecutablePath: /usr/bin/lightdm
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110604)
ProcCmdline: lightdm
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x804bb73: mov 0x20(%eax),%eax
PC (0x0804bb73) ok
source "0x20(%eax)" (0xaaaaaaca) not located in a known VMA region (needed
readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
?? ()
g_child_watch_dispatch (source=0x9c7fbc0, callback=0x804bb10,
user_data=0x9c81000) at /build/buildd/glib2.0-2.29.4/./glib/gmain.c:4471
g_main_dispatch (context=0x9c5b850) at
/build/buildd/glib2.0-2.29.4/./glib/gmain.c:2477
g_main_context_dispatch (context=0x9c5b850) at
/build/buildd/glib2.0-2.29.4/./glib/gmain.c:3050
g_main_context_iterate (context=0x9c5b850, block=1448320, dispatch=1,
self=<value optimized out>) at /build/buildd/glib2.0-2.29.4/./glib/gmain.c:3128
Title: lightdm crashed with SIGSEGV in g_child_watch_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/795324
Title:
lightdm crashed with SIGSEGV in g_child_watch_dispatch()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/795324/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
