parole crashed with SIGSEGV in _IO_new_fclose()

Bug #1214514 reported by Sebastian Rohde
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
parole (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

parole crashed with SIGSEGV in _IO_new_fclose()

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: parole 0.5.2-1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Fri Aug 16 22:29:33 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/parole
InstallationDate: Installed on 2013-07-15 (36 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MarkForUpload: True
ProcCmdline: /usr/bin/parole
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fcf6227e874 <_IO_new_fclose+4>: mov (%rdi),%edx
 PC (0x7fcf6227e874) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: parole
StacktraceTop:
 _IO_new_fclose (fp=0x0) at iofclose.c:54
 parole_clear_history_file_full ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: parole crashed with SIGSEGV in _IO_new_fclose()
UpgradeStatus: Upgraded to saucy on 2013-08-12 (7 days ago)
UserGroups: adm bacula cdrom dip libvirtd lpadmin plugdev root sambashare sudo vboxusers

Revision history for this message
Sebastian Rohde (sebastian-rohde) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _IO_new_fclose (fp=0x0) at iofclose.c:54
 parole_clear_history_file_full (relpath=<optimized out>) at parole-rc-utils.c:113
 parole_clear_history_file () at parole-rc-utils.c:100
 parole_open_location_clear_history (model=0x7fcf68082d30) at parole-open-location.c:160
 g_closure_invoke (closure=0x7fcf68096a80, return_value=0x0, n_param_values=1, param_values=0x7fffc344d530, invocation_hint=0x7fffc344d4d0) at /build/buildd/glib2.0-2.37.5/./gobject/gclosure.c:777

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in parole (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public Security
information type: Public Security → Private Security
information type: Private Security → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in parole (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul White (paulw2u) wrote :

When testing Xubuntu 17.04 I found parole crashed. Reporting the crash through the standard system prompts led me here, i.e. same crash error message.

Reproducible every time:

1) Open Parole
2) Select from menu: Media | Open Location
3) Click on "Clear History"

I would expect dialog to close and parole to stay open but it crashes.

tags: added: zesty
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1214514

tags: added: iso-testing
Paul White (paulw2u)
tags: added: artful
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package parole - 1.0.0-0ubuntu1

---------------
parole (1.0.0-0ubuntu1) bionic; urgency=medium

  * New upstream release.
    - Fixes crash on clear history (LP: #1214514)
    - Fixes crash on seek (LP: #1374887)

 -- Sean Davis <email address hidden> Wed, 28 Feb 2018 23:33:58 -0500

Changed in parole (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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