2013-12-18 21:35:05 |
Keith Burnett |
bug |
|
|
added bug |
2013-12-18 21:35:50 |
Keith Burnett |
information type |
Private |
Public |
|
2013-12-18 21:38:10 |
Keith Burnett |
attachment added |
|
abiword.crash https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/3932128/+files/abiword.crash |
|
2013-12-18 21:48:56 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for Ubuntu packages |
2013-12-18 21:49:00 |
Apport retracing service |
abiword (Ubuntu): status |
New |
Invalid |
|
2013-12-18 21:49:04 |
Apport retracing service |
attachment removed |
CoreDump.gz https://bugs.launchpad.net/bugs/1262375/+attachment/3932096/+files/CoreDump.gz |
|
|
2013-12-18 21:49:06 |
Apport retracing service |
tags |
apport-crash i386 need-i386-retrace saucy |
apport-crash i386 saucy |
|
2013-12-18 21:52:52 |
penalvch |
description |
https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1246111/
I was advised to open a new bug, even though bug number 1246111 describes the behaviour I am seeing.
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
keith@saucer:~$ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
(Xubuntu 13.10)
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
keith@saucer:~$ apt-cache policy abiword
abiword:
Installed: 3.0.0~svn20130523-1ubuntu2
Candidate: 3.0.0~svn20130523-1ubuntu2
Version table:
*** 3.0.0~svn20130523-1ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
Produce a document in Abiword
Save As a .abw file
Save As a .pdf file
4) What happened instead
Produce a document in Abiword
Save As a .abw file
Abiword crashes and produces a crash report file at /var/crash/_usr_bin_abiword.1000.crash
I shall attempt to upload the .crash file as an attachment
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 5 (LWP 6441):
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
1) lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
(Xubuntu 13.10)
2) apt-cache policy abiword
abiword:
Installed: 3.0.0~svn20130523-1ubuntu2
Candidate: 3.0.0~svn20130523-1ubuntu2
Version table:
*** 3.0.0~svn20130523-1ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status
3) What you expected to happen is produce a document in Abiword Save As a .abw file Save As a .pdf file
4) What happened instead us produce a document in Abiword. Save As a .abw file.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 5 (LWP 6441):
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
2013-12-18 21:54:44 |
penalvch |
abiword (Ubuntu): importance |
Undecided |
Low |
|
2013-12-18 21:54:44 |
penalvch |
abiword (Ubuntu): status |
Invalid |
Incomplete |
|
2013-12-18 21:56:31 |
penalvch |
summary |
abiword crashed with SIGABRT when saving a document as a PDF file |
abiword crashed with SIGABRT saving as PDF file |
|
2013-12-19 09:03:42 |
Keith Burnett |
attachment added |
|
A simple text file produced in Abiword which when saved as a PDF results in Abiword crashing https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/3932449/+files/test.abw |
|
2013-12-19 12:05:26 |
penalvch |
description |
1) lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
(Xubuntu 13.10)
2) apt-cache policy abiword
abiword:
Installed: 3.0.0~svn20130523-1ubuntu2
Candidate: 3.0.0~svn20130523-1ubuntu2
Version table:
*** 3.0.0~svn20130523-1ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status
3) What you expected to happen is produce a document in Abiword Save As a .abw file Save As a .pdf file
4) What happened instead us produce a document in Abiword. Save As a .abw file.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 5 (LWP 6441):
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
1) lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
(Xubuntu 13.10)
2) apt-cache policy abiword
abiword:
Installed: 3.0.0~svn20130523-1ubuntu2
Candidate: 3.0.0~svn20130523-1ubuntu2
Version table:
*** 3.0.0~svn20130523-1ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status
3) What you expected to happen is when one opens the file https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/3932449/+files/test.abw and saves as a PDF, it doesn't crash.
4) What happened instead is it does.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 5 (LWP 6441):
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
2013-12-19 12:06:19 |
penalvch |
summary |
abiword crashed with SIGABRT saving as PDF file |
abiword crashed with SIGABRT in FV_UnixSelectionHandles::FV_UnixSelectionHandles() saving as PDF file |
|
2013-12-19 12:07:06 |
penalvch |
description |
1) lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
(Xubuntu 13.10)
2) apt-cache policy abiword
abiword:
Installed: 3.0.0~svn20130523-1ubuntu2
Candidate: 3.0.0~svn20130523-1ubuntu2
Version table:
*** 3.0.0~svn20130523-1ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status
3) What you expected to happen is when one opens the file https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/3932449/+files/test.abw and saves as a PDF, it doesn't crash.
4) What happened instead is it does.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 5 (LWP 6441):
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
1) lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
(Xubuntu 13.10)
2) apt-cache policy abiword
abiword:
Installed: 3.0.0~svn20130523-1ubuntu2
Candidate: 3.0.0~svn20130523-1ubuntu2
Version table:
*** 3.0.0~svn20130523-1ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status
3) What you expected to happen is when one opens the file https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/3932449/+files/test.abw and saves as a PDF, it doesn't crash.
4) What happened instead is it does. For a crash report with debugging symbols installed (and amd64 retrace) please see https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262635 .
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 5 (LWP 6441):
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
2013-12-19 12:10:45 |
penalvch |
abiword (Ubuntu): status |
Incomplete |
Triaged |
|
2013-12-20 19:25:03 |
Keith Burnett |
bug watch added |
|
http://bugzilla.abisource.com/show_bug.cgi?id=13586 |
|
2013-12-20 19:49:05 |
penalvch |
bug task added |
|
abiword |
|
2013-12-20 19:52:21 |
penalvch |
abiword (Ubuntu): milestone |
|
ubuntu-14.04-feature-freeze |
|
2013-12-21 00:01:32 |
Bug Watch Updater |
abiword: status |
Unknown |
Confirmed |
|
2013-12-21 00:01:32 |
Bug Watch Updater |
abiword: importance |
Unknown |
Critical |
|
2013-12-28 02:11:17 |
penalvch |
description |
1) lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
(Xubuntu 13.10)
2) apt-cache policy abiword
abiword:
Installed: 3.0.0~svn20130523-1ubuntu2
Candidate: 3.0.0~svn20130523-1ubuntu2
Version table:
*** 3.0.0~svn20130523-1ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status
3) What you expected to happen is when one opens the file https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/3932449/+files/test.abw and saves as a PDF, it doesn't crash.
4) What happened instead is it does. For a crash report with debugging symbols installed (and amd64 retrace) please see https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262635 .
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 5 (LWP 6441):
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
1) lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
(Xubuntu 13.10)
2) apt-cache policy abiword
abiword:
Installed: 3.0.0~svn20130523-1ubuntu2
Candidate: 3.0.0~svn20130523-1ubuntu2
Version table:
*** 3.0.0~svn20130523-1ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status
3) What you expected to happen is when one opens the file https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/3932449/+files/test.abw and saves as a PDF, it doesn't crash.
4) What happened instead is it does. For a crash report with debugging symbols installed (and amd64 retrace) please see https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262635 .
Documented fix:
http://bugzilla.abisource.com/show_bug.cgi?id=13586#c2
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 5 (LWP 6441):
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
2014-01-02 01:52:09 |
Bug Watch Updater |
abiword: status |
Confirmed |
Fix Released |
|
2014-01-25 16:15:07 |
penalvch |
abiword (Ubuntu): importance |
Low |
Medium |
|
2014-01-25 16:15:54 |
penalvch |
tags |
apport-crash i386 saucy |
amd64 apport-crash i386 saucy trusty |
|
2014-02-23 19:12:48 |
penalvch |
description |
1) lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
(Xubuntu 13.10)
2) apt-cache policy abiword
abiword:
Installed: 3.0.0~svn20130523-1ubuntu2
Candidate: 3.0.0~svn20130523-1ubuntu2
Version table:
*** 3.0.0~svn20130523-1ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status
3) What you expected to happen is when one opens the file https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/3932449/+files/test.abw and saves as a PDF, it doesn't crash.
4) What happened instead is it does. For a crash report with debugging symbols installed (and amd64 retrace) please see https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262635 .
Documented fix:
http://bugzilla.abisource.com/show_bug.cgi?id=13586#c2
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 5 (LWP 6441):
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
1) lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
2) apt-cache policy abiword
abiword:
Installed: 3.0.0-4
Candidate: 3.0.0-4
Version table:
*** 3.0.0-4 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen is when one opens the file https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/3932449/+files/test.abw and saves as a PDF, it doesn't crash.
4) What happened instead is it does. For a crash report with debugging symbols installed (and amd64 retrace) please see https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262635 .
Documented fix:
http://bugzilla.abisource.com/show_bug.cgi?id=13586#c2
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 18 19:10:39 2013
ExecutablePath: /usr/bin/abiword
ExecutableTimestamp: 1371838828
InstallationDate: Installed on 2013-12-17 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
MarkForUpload: True
ProcCmdline: abiword
ProcCwd: /home/keith
Signal: 6
SourcePackage: abiword
Stacktrace:
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x5
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 5 (LWP 6441):
#0 0xb7742424 in ?? ()
No symbol table info available.
Cannot access memory at address 0x6
Title: abiword crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
2014-03-29 20:35:29 |
Thaddaeus Tintenfisch |
attachment added |
|
r33663_fix-crash-when-saving-to-pdf.patch https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1262375/+attachment/4051742/+files/r33663_fix-crash-when-saving-to-pdf.patch |
|
2014-03-30 00:26:21 |
Ubuntu Foundations Team Bug Bot |
tags |
amd64 apport-crash i386 saucy trusty |
amd64 apport-crash i386 patch saucy trusty |
|
2014-03-30 00:26:28 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
2014-04-09 13:57:05 |
Adam Dingle |
bug |
|
|
added subscriber Adam Dingle |
2014-04-13 21:03:15 |
Launchpad Janitor |
abiword (Ubuntu): status |
Triaged |
Fix Released |
|
2014-04-14 12:49:13 |
Pasi Lallinaho |
abiword (Ubuntu): assignee |
|
Thaddäus Tintenfisch (thad-fisch) |
|