Ubuntu
glib2.0 package

python2.5 crashed with SIGSEGV

Bug #128419 reported by Nemes Ioan Sorin on 2007-07-26

14

Affects		Status	Importance	Assigned to	Milestone
	dbus (Ubuntu)	Invalid	Medium	Unassigned
	glib2.0 (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: python2.5

randomly after an upgrade on 23 July - at every boot some programs crashed.
sometime a program called "id", sometime "notification-daemon" sometime hmm "mplayer" and now "python".

I think some service / daemon goes wrong.

Each time I see the notification icon after boot on Gnome. I can let this icon on his peace and work away without any visible prejudice.

So I'm not clear if is a really crash on Python OR something else - induced by a defective service / daemon.

I hope the stack trace will help you to find the real problem.

ProblemType: Crash
Architecture: i386
Date: Wed Jul 25 23:17:43 2007
Dependencies:
libgcc1 1:4.2.1-0ubuntu1
gcc-4.2-base 4.2.1-0ubuntu1
zlib1g 1:1.2.3.3.dfsg-5ubuntu1
libc6 2.6-3ubuntu2
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/python2.5
NonfreeKernelModules: cdrom
Package: python2.5-minimal 2.5.1-1ubuntu4
PackageArchitecture: i386
ProcCmdline: python exaile.py
ProcCwd: /usr/share/exaile
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: python2.5
Stacktrace:
#0 0xb7b682fa in ?? () from /usr/lib/libdbus-1.so.3
#1 0x00000000 in ?? ()
StacktraceTop:
?? () from /usr/lib/libdbus-1.so.3
?? ()
Title: python2.5 crashed with SIGSEGV
Uname: Linux sorin 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev scanner tape video

Tags:

Revision history for this message

Nemes Ioan Sorin (nemes-sorin) wrote on 2007-07-26:

#1

Disassembly.txt Edit (884 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (41.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (673 bytes, text/plain; charset="utf-8")
Registers.txt Edit (507 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (5.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2007-07-26: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (1.7 KiB, text/plain)

StacktraceTop:_dbus_pending_call_get_connection_and_lock (pending=0x98d2e40) at dbus-pending-call.c:309
reply_handler_timeout (data=0x98d2e40) at dbus-connection.c:3063
dbus_timeout_handle (timeout=0x9694380) at dbus-timeout.c:473
timeout_handler_dispatch (data=0x967c288) at dbus-gmain.c:343
g_timeout_dispatch (source=0x968e3a0, callback=0x98d2e40, user_data=0x967c288) at /build/buildd/glib2.0-2.13.7/glib/gmain.c:3488

Revision history for this message

Apport retracing service (apport) wrote on 2007-07-26: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (7.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2007-07-26: Stack trace with source code

#4

StacktraceSource.txt Edit (1.8 KiB, text/plain)

Changed in python2.5:
importance:	Undecided → Medium

Revision history for this message

Matthias Klose (doko) wrote on 2007-08-14:

#5

dbus/glib2.0 problem?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-09-19:

#6

doesn't look like a glib2.0 bug

Changed in glib2.0:
status:	New → Invalid

Revision history for this message

Sebastien Bacher (seb128) wrote on 2008-07-26:

#7

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try if that's still an issue on hardy?

Changed in dbus:
importance:	Undecided → Medium
status:	New → Incomplete

Revision history for this message

Nemes Ioan Sorin (nemes-sorin) wrote on 2008-07-27: Re: [Bug 128419] Re: python2.5 crashed with SIGSEGV

#8

nope I can't confirm this issue on Hardy ..can be closed

2008/7/26 Sebastien Bacher <email address hidden>:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try if that's still an issue on hardy?
>
> ** Changed in: dbus (Ubuntu)
> Importance: Undecided => Medium
> Status: New => Incomplete
>
> --
> python2.5 crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/128419
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Nemes Ioan Sorin

Revision history for this message

Nemes Ioan Sorin (nemes-sorin) wrote on 2008-07-27:

#9

..at least from my side

2008/7/27 SorinN <email address hidden>:
> nope I can't confirm this issue on Hardy ..can be closed
>
> 2008/7/26 Sebastien Bacher <email address hidden>:
>> Thank you for taking the time to report this bug and helping to make
>> Ubuntu better. You reported this bug a while ago and there hasn't been
>> any activity in it recently. We were wondering is this still an issue
>> for you? Can you try if that's still an issue on hardy?
>>
>> ** Changed in: dbus (Ubuntu)
>> Importance: Undecided => Medium
>> Status: New => Incomplete
>>
>> --
>> python2.5 crashed with SIGSEGV
>> https://bugs.launchpad.net/bugs/128419
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
>
> --
> Nemes Ioan Sorin
>

--
Nemes Ioan Sorin

Revision history for this message

Sebastien Bacher (seb128) wrote on 2008-07-27:

#10

thank you for the update, closing the bug, feel free to reopen if you get the issue again though

Changed in dbus:
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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