Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report:
libudisks2-0 version 1.99.0-2 required, but 1.99.0-3 is available outdated debug symbol package for libudisks2-0: package version 1.99.0-3 dbgsym version 1.99.0-2 gir1.2-freedesktop version 1.33.9-1 required, but 1.33.10-1 is available python-gi version 3.3.90-1 required, but 3.3.91-1 is available libglib2.0-0 version 2.33.10-0ubuntu3 required, but 2.33.12-3 is available udisks2 version 1.99.0-2 required, but 1.99.0-3 is available outdated debug symbol package for udisks2: package version 1.99.0-3 dbgsym version 1.99.0-2 libglib2.0-data version 2.33.10-0ubuntu3 required, but 2.33.12-3 is available python-gobject version 3.3.90-1 required, but 3.3.91-1 is available libgirepository-1.0-1 version 1.33.9-1 required, but 1.33.10-1 is available outdated debug symbol package for libgirepository-1.0-1: package version 1.33.10-1 dbgsym version 1.33.9-1 gir1.2-glib-2.0 version 1.33.9-1 required, but 1.33.10-1 is available outdated debug symbol package for libfile-fcntllock-perl: package version 0.14-2 dbgsym version 0.14-1build1 outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu3 dbgsym version 3.16-1ubuntu2 python3-gi version 3.3.90-1 required, but 3.3.91-1 is available outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1046801/+attachment/3296012/+files/CoreDump.gz ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1046801 Title: file-roller crashed with SIGSEGV in gtk_list_store_set_valist() Status in “file-roller” package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Open an archive with File Roller ( I opened a zip file). 2. Browse to a folder. 3. Click on the "add" button. 4. Select any folder. 5. Crash! ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: file-roller 3.5.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu4 Architecture: i386 CrashCounter: 1 Date: Thu Sep 6 17:38:12 2012 ExecutablePath: /usr/bin/file-roller InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120627) ProcCmdline: file-roller /home/username/AceCream_1.1rev.zip ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/usr/bin/zsh SegvAnalysis: Segfault happened at: 0xb6e2628c: mov (%esi),%eax PC (0xb6e2628c) ok source "(%esi)" (0x00000009) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 gtk_list_store_set_valist () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 gtk_list_store_set () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () Title: file-roller crashed with SIGSEGV in gtk_list_store_set_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1046801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
