file-roller crashed with SIGSEGV in gdk_window_is_destroyed()

Bug #1530589 reported by Václav Haisman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
New
Undecided
Unassigned

Bug Description

It crashed when I tried to view a .zip file. It is similar to #1428619 but on WIly.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: file-roller 3.16.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-22.27-lowlatency 4.2.6
Uname: Linux 4.2.0-22-lowlatency x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Sat Jan 2 23:30:25 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2011-11-13 (1511 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: file-roller /home/username/log4cplus-1.2.0-rc6.zip
SegvAnalysis:
 Segfault happened at: 0x7f37fa0ad0d0 <gdk_window_is_destroyed>: movzbl 0xc6(%rdi),%eax
 PC (0x7f37fa0ad0d0) ok
 source "0xc6(%rdi)" (0x000000c7) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 gdk_window_is_destroyed () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 gtk_get_event_widget () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ()
Title: file-roller crashed with SIGSEGV in gdk_window_is_destroyed()
UpgradeStatus: Upgraded to wily on 2015-10-24 (70 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin mythtv netdev plugdev sambashare scanner tape vboxusers video wireshark

Revision history for this message
Václav Haisman (vzeman79) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1428619, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.