raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: terminator (Ubuntu Raring)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs,
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: terminator (Ubuntu Quantal)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: verification-done-quantal verification-done-raring
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951236
Title:
terminator crashed with SIGSEGV
This bug was fixed in the package terminator - 0.96-0ubuntu1.0.1
---
terminator (0.96-0ubuntu1.0.1) precise-proposed; urgency=low
* Add drag_crash.patch: Cherrypicked patch (rev 1357), Extra guarding
against crashy gtk functions, to fix crash when dragging a terminal
window
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951236
Title:
terminator crashed with SIGSEGV in PyEval_EvalFrameEx()
To manage notifications about this bug
Hello Terry, or anyone else affected,
Accepted terminator into raring-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/terminator/0.96-2ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Also affects: terminator (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951236
Title:
terminator crashed with SIGSEGV in
The crash is not present in saucy's terminator. I performed a bisection
search to isolate r1357 as the fix. I can fairly easily crash r1356,
but could not repro the crash in r1357 or newer.
r1357 indicates it is a fix for upstream bug #1089190, which seems to
describe this same problem.
**
** Description changed:
- To reproduce: Drag a window to a new horizontal position within another
- window. Only seems to work with at least 4 windows (2x2). Reproducible
- every time if dragged to top position of a window and to bottom position
- of same window without releasing it. Or just
Uploaded patch to precise, quantal, and raring.
** Changed in: terminator (Ubuntu Precise)
Status: In Progress = Fix Committed
** Changed in: terminator (Ubuntu Quantal)
Status: In Progress = Fix Committed
** Changed in: terminator (Ubuntu Raring)
Status: In Progress = Fix
** Changed in: terminator
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951236
Title:
terminator crashed with SIGSEGV in PyEval_EvalFrameEx()
To manage
I believe I have fixed the terminal dragging crasher in trunk.
** Also affects: terminator
Importance: Undecided
Status: New
** Changed in: terminator
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Great! Will the fix be backported to LTS ? thnx btw!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951236
Title:
terminator crashed with SIGSEGV in PyEval_EvalFrameEx()
To manage notifications
** 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/951236
Title:
terminator crashed with SIGSEGV in PyEval_EvalFrameEx()
To manage notifications about this bug go to:
Got a similar crash just now. Also was repositioning windows, it locked
up and crashed. Stacktrace is slightly different but same general
theme.
Segfault happened at: 0x1: Cannot access memory at address 0x1
PC (0x0001) not located in a known VMA region (needed executable
region)!
**
I didn't think that Python being a high level language should segfault
caused by a bug in a Python script? Especially where something as low
level as VMA is concerned. If this isn't the case then I would love to
know. Just a thought anyway.
--
You received this bug notification because you are a
16 matches
Mail list logo
