gnome-commander assert failure: gnome-commander: /build/buildd/cairo-1.10.2/src/cairo-clip.c:92: _cairo_clip_path_destroy: La declaración `((*&(&clip_path->ref_count)->ref_count) > 0)' no se cumple.

Bug #769259 reported by Martin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-commander (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-commander

lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

gnome-commander 1.2.8.10

Buscaba un archivo en mi directorio / arranque el gnome-commander desde una terminal con sudo gnome-commander

La aplicación se cierra automaticamente sin llegar a mostrar resultados

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-commander 1.2.8.10-3build1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
AssertionMessage: gnome-commander: /build/buildd/cairo-1.10.2/src/cairo-clip.c:92: _cairo_clip_path_destroy: La declaración `((*&(&clip_path->ref_count)->ref_count) > 0)' no se cumple.
CrashCounter: 1
Date: Fri Apr 22 17:10:01 2011
ExecutablePath: /usr/bin/gnome-commander
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcCmdline: gnome-commander
ProcEnviron:
 PATH=(custom, no user)
 LC_MESSAGES=es_HN.UTF-8
 LANG=es_AR.utf8
 LANGUAGE=es_HN:en
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-commander
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/libcairo.so.2
 ?? () from /usr/lib/libcairo.so.2
Title: gnome-commander assert failure: gnome-commander: /build/buildd/cairo-1.10.2/src/cairo-clip.c:92: _cairo_clip_path_destroy: La declaración `((*&(&clip_path->ref_count)->ref_count) > 0)' no se cumple.
UpgradeStatus: Upgraded to natty on 2011-04-21 (1 days ago)
UserGroups:

Revision history for this message
Martin (mbattiti) wrote :
Revision history for this message
Uwe (turboscholz) wrote :

Is this still reproducible with the latest release?

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.