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 566417 - Gnome-commander crashes by deleting files
Gnome-commander crashes by deleting files
Status: RESOLVED FIXED
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: Normal critical
: 1.2.8
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2009-01-03 14:51 UTC by tblu
Modified: 2009-01-26 21:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gnome-commander.mo (135.07 KB, application/x-gettext-translation)
2009-01-25 13:55 UTC, epiotr
Details

Description tblu 2009-01-03 14:51:04 UTC
Steps to reproduce:
1. E.G. choose any file on your home directory
2. delete it
3. the application will not delete it. It will crash instead.


Stack trace:


Other information:
Comment 1 epiotr 2009-01-05 19:10:21 UTC
What distro and gcmd version?
Comment 2 tblu 2009-01-11 20:34:23 UTC
Distro: Paldo
gcmd version: 1.2.7
Comment 3 ramas 2009-01-22 20:26:49 UTC
I think the problem affects italian locale...perhaps a malformed translation string?
Comment 4 epiotr 2009-01-25 13:55:18 UTC
Created attachment 127201 [details]
gnome-commander.mo

Good point. I've found in it.po broken translation string:

	#: ../src/gnome-cmd-delete-dialog.cc:88
	#, c-format
	msgid "Deleted %ld of %ld file"
	msgid_plural "Deleted %ld of %ld files"
	msgstr[0] "[file %ld di %ld] \"%s\""
	msgstr[1] "Cancellati %ld di %ld files"

The attachment contains corrected it.gmo file for 1.2.7 release - please replace your current installed translation/usr/share/locale/it/LC_MESSAGES/gnome-commander.mo with the attached file
Comment 5 ramas 2009-01-26 16:25:55 UTC
Wow! The fixed .mo file solved the problem here! Good work! :)
Comment 6 epiotr 2009-01-26 21:50:13 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.