GNOME Bugzilla – Bug 447882
crash in GNOME Commander: Gnome Commander => Advan...
Last modified: 2008-01-04 23:15:09 UTC
Version: 1.2.4 What were you doing when the application crashed? Gnome Commander => Advanced Raneme Tool => Replacing file name spaces with _ Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 43147264 vsize: 43147264 resident: 23719936 share: 17899520 rss: 23719936 rss_rlim: 4294967295 CPU usage: start_time: 1181913294 rtime: 77 utime: 69 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-commander' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208625440 (LWP 10910)] (no debugging symbols found) 0x0091a402 in __kernel_vsyscall ()
+ Trace 141204
Thread 1 (Thread -1208625440 (LWP 10910))
----------- .xsession-errors (23 sec old) --------------------- Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 14 [45%] [-25.50dB] [on] Front Right: Playback 14 [45%] [-25.50dB] [on] Simple mixer control 'Master',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 12 [39%] [-28.50dB] [on] Front Right: Playback 12 [39%] [-28.50dB] [on] MADPlug-Message: xing: bytes = 6333632 frames = 8089 MADPlug-Message: info->duration = 0 MADPlug-Message: mad_timer_count = 0 Creating directory /home/solitarymike/.gnome-commander... Creating directory /home/solitarymike/.gnome-commander/plugins... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for gnome-commander, gtk, glib, gnome-vfs, libgnome, libgnomeui and pango (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 451601 has been marked as a duplicate of this bug. ***
*** Bug 453106 has been marked as a duplicate of this bug. ***
*** Bug 453978 has been marked as a duplicate of this bug. ***
*** Bug 457101 has been marked as a duplicate of this bug. ***
copying from bug 457101 comment 2: Confirmed - gcmd crashes after second CTRL+M if used regex replacements. But in your case you don't need regexes, simply use (instead of default $N) the following: $n(:-2)$c(2).$e as filename template. Please refer to the manual for detailed explanation of placeholders.
The bug seems ot have gone with SVN rev1235. Howver the fix may have introduced a new one: Converting '_' into anything else doesn't work, the underscore fails to be recognized.
The bug seems ot have gone with SVN rev1235. Howver the fix may have introduced a new one: Converting '_' into anything else doesn't work, the underscore fails to be recognized. (bugzilla sticks so i post it again)
Here is my stacktrace of the regex-crash. I am using svn version 1444 of gnome-commander. The distribution is dapper drake, running gnome 2.14.3 and glib 2.10.3. Backtrace was generated from '/usr/local/bin/gnome-commander' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226344768 (LWP 5324)] [New Thread -1266332752 (LWP 5325)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 183620
Thread 1 (Thread -1226344768 (LWP 5324))
*** Bug 407418 has been marked as a duplicate of this bug. ***
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.