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 521063 - afte file rename, moving down one file and deleting, deletes the renamed file, not the one above
afte file rename, moving down one file and deleting, deletes the renamed file...
Status: RESOLVED DUPLICATE of bug 345314
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: Normal critical
: 1.2.6
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2008-03-07 19:10 UTC by jurgis.pralgauskis
Modified: 2008-03-09 22:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
configure: error: C compiler cannot create executables - configure: exit 77 (9.80 KB, text/plain)
2008-03-08 11:43 UTC, jurgis.pralgauskis
Details

Description jurgis.pralgauskis 2008-03-07 19:10:42 UTC
Please describe the problem:

I renamed my scriptX.py to scriptY.py, 
and in the window just under it there was (compiled version of scriptX.py) scriptX.pyc, which I wanted to delete
so I moved down, and pressed Delete (and confirmed automaticlly because my intention was very clear)

what I didn't expect, is that gnome-cmd decided 
that I am dealing with the file I just renamed (but I really  moved to one file down) 
and deleted it, so bye bye my scriptY.py instead of scriptX.pyc :(


Steps to reproduce:
1. have at least two files in directory
2. rename the upper file
3. go down one file
4. try to delete/copy/move/rename the file



Actual results:
and it acts on the file above (instead of current file)

Expected results:
act on the current file :)

Does this happen every time?
yes

Other information:
this would not be such big problem, if I could find it in some .Trash 
(see http://bugzilla.gnome.org/show_bug.cgi?id=348414)
Comment 1 epiotr 2008-03-07 23:15:43 UTC
What version do you use?
Comment 2 jurgis.pralgauskis 2008-03-08 11:43:52 UTC
Created attachment 106839 [details]
configure: error: C compiler cannot create executables - configure: exit 77

trying to set up gcmd 1.2.5
first thought the problem was because  gcmd 1.2.4 was already running,
so exited it, but that didn't help
Comment 3 jurgis.pralgauskis 2008-03-08 11:46:41 UTC
1.24 Ubuntu Gutsy
I couldn't find any newer debs (Ubuntu or Debian)
http://www.nongnu.org/gcmd/download.html#distro

tried to setup 1.25 manually, but configure failed -- see attachment #106839 [details]  
Comment 4 epiotr 2008-03-09 22:50:53 UTC
Please upgrade to the latest 1.2.5, which has the reported problem fixed.

AFAIK Ubuntu doesn't provide packages for 1.2.5 (although I've signaled the Ubuntu  maintainer of the package about about the new version...), but you can try to build the package yourself using http://launchpadlibrarian.net/12381394/gnome-commander_1.2.5-0ubuntu1.dsc

As of your build problem - this is related to:

/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure:3195: $? = 1
configure:3233: result: 
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME "gnome-commander"
| #define PACKAGE_TARNAME "gnome-commander"
| #define PACKAGE_VERSION "1.2.5"
| #define PACKAGE_STRING "gnome-commander 1.2.5"
| #define PACKAGE_BUGREPORT "http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-commander"
| #define PACKAGE "gnome-commander"
| #define VERSION "1.2.5"
| #define _GNU_SOURCE 1
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }
configure:3240: error: C compiler cannot create executables
See `config.log' for more details.


Please refer to http://anaaman.blogspot.com/2006/01/crt1o-no-such-file-no-such-file-or.html for details how solve the problem.



Hope it'll help,
Piotr

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