emesene is no longer developed and has been removed from Ubuntu and
Debian back in 2015
** No longer affects: pygobject (Ubuntu)
** No longer affects: pygobject-2 (Ubuntu)
** Changed in: emesene (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: emesene (Ubuntu)
Assignee: eduardo
This crash seems to be limited to Ubuntu 12.10 and 13.04 (looking at the
duplicates and the linked upstream bug report). And that's no longer
supported.
Also the affected program is unmaintained for some years now.
** Changed in: pygobject (Ubuntu)
Status: Triaged => Fix Released
--
You
** Changed in: pygobject (Ubuntu)
Assignee: (unassigned) => roopa (roopat85)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050358
Title:
emesene crashed with SIGSEGV in tupledealloc.24592()
** Changed in: emesene (Ubuntu)
Status: Triaged = Confirmed
** Changed in: pygobject-2 (Ubuntu)
Status: Triaged = Confirmed
** Changed in: pygobject (Ubuntu)
Status: Triaged = Confirmed
** Changed in: pygobject (Ubuntu)
Assignee: (unassigned) = Anders (eddiedog988)
--
** Changed in: emesene (Ubuntu)
Status: Confirmed = Triaged
** Changed in: pygobject-2 (Ubuntu)
Status: Confirmed = Triaged
** Changed in: pygobject (Ubuntu)
Status: Confirmed = Triaged
** Changed in: pygobject (Ubuntu)
Assignee: Anders (eddiedog988) = (unassigned)
--
** Changed in: emesene (Ubuntu)
Assignee: (unassigned) = eduardo (lalo7america)
** Changed in: pygobject-2 (Ubuntu)
Assignee: (unassigned) = eduardo (lalo7america)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since this bug:
- Is valid.
- Is well described.
- Is reported in the upstream project.
- Is ready to be worked on by a developer.
It's already triaged.
** Changed in: emesene (Ubuntu)
Status: Confirmed = Triaged
** Changed in: pygobject-2 (Ubuntu)
Status: Confirmed = Triaged
**
** Tags added: raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050358
Title:
emesene crashed with SIGSEGV in tupledealloc.24592()
To manage notifications about this bug go to:
this bug is being tracked here:
https://github.com/emesene/emesene/issues/1537
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050358
Title:
emesene crashed with SIGSEGV in tupledealloc.24592()
To
I reported a related crash in bug#1069163. Checking today I find the
same behavior reported there; no mention of tupledealloc in the
stacktrace.
What is new is a stacktrace reported when I start emesene from a
terminal, which I didn't see before it crashed originally. Now it says:
~$ emesene
Also affecting me, but in the form of bug #1051490 (SIGSEGV in
g_main_context_dispatch())
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050358
Title:
emesene crashed with SIGSEGV in
This is also affecting me. Upgraded today Kubuntu 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050358
Title:
emesene crashed with SIGSEGV in tupledealloc.24592()
To manage notifications
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
DistroRelease: Ubuntu 12.10
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423)
Package: pygobject-2
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Tags: quantal running-unity
Uname: Linux
This uses the old static (and unmaintained) pygobject bindings,
reassigning.
** Package changed: pygobject (Ubuntu) = pygobject-2 (Ubuntu)
** Changed in: pygobject-2 (Ubuntu)
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here's a backtrace of that happening:
#0 0x004b5c78 in tupledealloc.24592 (op=0x29ed690)
at ../Objects/tupleobject.c:218
#1 0x0048a56a in func_dealloc.15338 (op=0x29ec6e0)
at ../Objects/funcobject.c:461
#2 0x7498b0fa in pyg_iowatch_data_free (data=0x2b9fe00)
Martin, it also seems to happen when I start emesene in Gtk3 mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050358
Title:
emesene crashed with SIGSEGV in tupledealloc.24592()
To manage
** Also affects: pygobject (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pygobject (Ubuntu)
Status: New = Confirmed
** Changed in: pygobject (Ubuntu)
Importance: Undecided = High
** Changed in: emesene (Ubuntu)
Importance: Medium = Critical
--
You received
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050358
Title:
emesene crashed with SIGSEGV in tupledealloc.24592()
To manage notifications about this bug go to:
** Also affects: pygobject (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pygobject (Ubuntu)
Status: New = Confirmed
** Changed in: pygobject (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs,
19 matches
Mail list logo