After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 559468 - GNOME Commander: Crashing after selecting...
GNOME Commander: Crashing after selecting...
Status: RESOLVED DUPLICATE of bug 567404
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: Normal normal
: 1.2.8
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2008-11-05 17:02 UTC by Tibor Farkas
Modified: 2009-01-13 20:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Tibor Farkas 2008-11-05 17:02:36 UTC
Version: 1.2.6

Crashing after selecting directorys with spacebar or leftclick+ctrl


Distribution: Ubuntu 8.10 (intrepid)
Gnome Release: 2.24.1 2008-10-24 (Ubuntu)
BugBuddy Version: 2.24.1
Comment 1 epiotr 2008-11-05 17:11:16 UTC
Please upgrade to the latest version: 1.2.7. Packages for Ubuntu can be found here: http://www.getdeb.net/app/GNOME+Commander
Comment 2 Tibor Farkas 2008-11-05 17:20:11 UTC
Installing the new 1.2.7 version from getdeb _NOT solved this problem for me.
Comment 3 Tibor Farkas 2008-11-05 17:24:29 UTC
This is the crash output in terminal:

** (gnome-commander:6602): CRITICAL **: void gnome_cmd_file_list_show_dir_size(GnomeCmdFileList*, GnomeCmdFile*): assertion `GNOME_CMD_IS_FILE (finfo)' failed


Comment 4 epiotr 2008-11-07 18:28:37 UTC
Does it happen for every directory? If not - is there any special about these dirs (like non-utf8 encodings)?
Comment 5 Tibor Farkas 2008-11-08 06:39:17 UTC
(In reply to comment #4)
> Does it happen for every directory? If not - is there any special about these
> dirs (like non-utf8 encodings)?
> 

It happens in every directory. Before updating to 1.2.6 this problem doesn't exists. there is no special encoding in the directory's.
Comment 6 epiotr 2009-01-13 20:00:32 UTC

*** This bug has been marked as a duplicate of 567404 ***