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 397216 - crash in GNOME Commander: I was attempting to appl...
crash in GNOME Commander: I was attempting to appl...
Status: RESOLVED DUPLICATE of bug 376909
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: High critical
: 1.2.4
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2007-01-16 11:13 UTC by rbooth01
Modified: 2007-02-10 19:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description rbooth01 2007-01-16 11:13:19 UTC
Version: 1.2.0

What were you doing when the application crashed?
I was attempting to apply permissions to a large folder. I selected "read" access for Owner, Group, and Other, and chose to apply settings recursively, and to apply changes to directory only, then crash. Looks to me like it crashed well before it could have traversed the entire heirarchy of subfolders.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 35405824 vsize: 0 resident: 35405824 share: 0 rss: 13058048 rss_rlim: 0
CPU usage: start_time: 1168945753 rtime: 0 utime: 496 stime: 0 cutime:408 cstime: 0 timeout: 88 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-commander'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225587024 (LWP 15329)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225587024 (LWP 15329))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_insert
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall

Comment 1 Marc-Andre Lureau 2007-02-10 19:56:30 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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