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 587325 - Gnome-Commander 1.2.8 crashes in a clean chroot environment
Gnome-Commander 1.2.8 crashes in a clean chroot environment
Status: RESOLVED FIXED
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: High critical
: 1.2.8
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2009-06-29 16:19 UTC by Christoph Korn
Modified: 2009-07-09 10:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace (3.86 KB, text/plain)
2009-07-01 16:22 UTC, Christoph Korn
Details
complete backtrace (3.77 KB, text/plain)
2009-07-01 19:32 UTC, Christoph Korn
Details
gnome-commander -d=cdkimn (3.67 KB, text/plain)
2009-07-02 07:06 UTC, Christoph Korn
Details

Description Christoph Korn 2009-06-29 16:19:44 UTC
Steps to reproduce:
1. I have built gnome-commander in a chroot for ubuntu jaunty (amd64).
2. I installed it in a clean chroot environment.
3. The program crashes at startup.


Stack trace:
$ gnome-commander 
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

** (gnome-commander:11197): CRITICAL **: GnomeCmdConFtp* gnome_cmd_con_ftp_new(const gchar*, const std::string&): assertion `uri != NULL' failed

** (gnome-commander:11197): WARNING **: Failed to open file '/home/korn/.gnome-commander/gnome-commander.xml': No such file or directory

(gnome-commander:11197): Gtk-WARNING **: Could not find the icon 'gnome-fs-home'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
	http://icon-theme.freedesktop.org/releases

** (gnome-commander:11197): WARNING **: Couldn't load icon: Icon 'gnome-fs-home' not present in theme

** (gnome-commander:11197): WARNING **: Couldn't load icon: Icon 'gnome-fs-home' not present in theme

** (gnome-commander:11197): WARNING **: Couldn't load icon: Icon 'gnome-fs-home' not present in theme

** (gnome-commander:11197): WARNING **: Couldn't load icon: Icon 'gnome-fs-network' not present in theme

** (gnome-commander:11197): WARNING **: Couldn't load icon: Icon 'gnome-fs-network' not present in theme

** (gnome-commander:11197): WARNING **: Couldn't load icon: Icon 'gnome-fs-network' not present in theme

** (gnome-commander:11197): CRITICAL **: GnomeCmdConFtp* gnome_cmd_con_ftp_new(const gchar*, const std::string&): assertion `uri != NULL' failed

(gnome-commander:11197): Gtk-CRITICAL **: gtk_signal_connect_full: assertion `GTK_IS_OBJECT (object)' failed

** (gnome-commander:11197): CRITICAL **: GnomeCmdBookmarkGroup* gnome_cmd_con_get_bookmarks(GnomeCmdCon*): assertion `GNOME_CMD_IS_CON (con)' failed
Segmentation fault


Other information:
The sources have not been patched before.

These are the runtime dependencies:
Depends: libart-2.0-2 (>= 2.3.18), libatk1.0-0 (>= 1.20.0), libbonobo2-0 (>= 2.15.0), libbonoboui2-0 (>= 2.15.1), libc6 (>= 2.4), libcairo2 (>= 1.2.4), libexiv2-5, libexpat1 (>= 1.95.8), libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:4.1.1), libgconf2-4 (>= 2.13.5), libglib2.0-0 (>= 2.16.0), libgnome2-0 (>= 2.17.3), libgnomecanvas2-0 (>= 2.11.1), libgnomeui-0 (>= 2.22.0), libgnomevfs2-0 (>= 1:2.17.90), libgtk2.0-0 (>= 2.16.0), libice6 (>= 1:1.0.0), liborbit2 (>= 1:2.14.10), libpango1.0-0 (>= 1.14.0), libpopt0 (>= 1.14), libsm6, libstdc++6 (>= 4.2.1), libtag1c2a (>= 1.5), zlib1g (>= 1:1.1.4)
Comment 1 palfrey 2009-07-01 14:04:10 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Christoph Korn 2009-07-01 16:22:11 UTC
Created attachment 137699 [details]
backtrace

I installed the debugging symbols for the gnome libraries.

Attached is the backtrace of gnome-commander in gdb.
Comment 3 palfrey 2009-07-01 16:25:02 UTC
(In reply to comment #2)
> Created an attachment (id=137699) [edit]
> backtrace
> 
> I installed the debugging symbols for the gnome libraries.
> 
> Attached is the backtrace of gnome-commander in gdb.

The trace still appears to be missing some symbols. Can you please install the debugging symbols for gnome-commander as well? Thanks!
Comment 4 Christoph Korn 2009-07-01 19:32:02 UTC
Created attachment 137706 [details]
complete backtrace

This is the backtrace with the debugging symbols of gnome-commander installed.
Comment 5 epiotr 2009-07-01 20:38:14 UTC
What sources do you use? 1.2.8?
Did you use gcmd before? Do you have $HOME/.gnome-commander/connections file present? If so, try to empty it. If that doesn't help, try to delete it (but please backup it BEFORE ;o)

backtrace with gnome-vfs debugging lib could be helpful too, so if possible - please install it.

gcmd comes with kind of debugging implemented, you can start it within console with -d= parameter. Please experiment a bit to see if that could bring some more data. The complete list of available flags is attached below:

  a user actions debugging
  c file and directory counting
  d directory ref-counting
  f file ref-counting
  g run_command debugging
  i image loader
  k directory pool
  l directory listings
  m connection debugging
  n directory monitoring
  p python plugins
  s SMB network browser
  t metadata tags
  v internal viewer
  w widget_lookup
  x xfer
  y brief MIME based imageload
  z detailed MIME based imageload
Comment 6 Christoph Korn 2009-07-01 21:01:49 UTC
(In reply to comment #5)
> What sources do you use? 1.2.8?
Yes, I use the 1.2.8 sources. No patches applied.

> Did you use gcmd before? 
No, I cannot find such a command in any package.

> Do you have $HOME/.gnome-commander/connections file
> present? If so, try to empty it. If that doesn't help, try to delete it (but
> please backup it BEFORE ;o)
The file is not present. The entire .gnome-commander directory does not exist.
After the application crashes the directory exists but is empty.

> 
> backtrace with gnome-vfs debugging lib could be helpful too, so if possible -
> please install it.
The debugging symbols of that package are already installed:
http://packages.ubuntu.com/jaunty/libgnomevfs2-0-dbg


> 
> gcmd comes with kind of debugging implemented, you can start it within console
> with -d= parameter. Please experiment a bit to see if that could bring some
> more data. The complete list of available flags is attached below:
> 
>   a user actions debugging
>   c file and directory counting
>   d directory ref-counting
>   f file ref-counting
>   g run_command debugging
>   i image loader
>   k directory pool
>   l directory listings
>   m connection debugging
>   n directory monitoring
>   p python plugins
>   s SMB network browser
>   t metadata tags
>   v internal viewer
>   w widget_lookup
>   x xfer
>   y brief MIME based imageload
>   z detailed MIME based imageload
> 

Sorry, but this binary does neither exist in the gnome-commander package nor in any package from the ubuntu repository.
Comment 7 epiotr 2009-07-01 21:56:01 UTC
> The file is not present. The entire .gnome-commander directory does not exist.
> After the application crashes the directory exists but is empty.

Try to create empty .gnome-commander/connections before the first start


> Sorry, but this binary does neither exist in the gnome-commander package nor in
> any package from the ubuntu repository.

I meant eg. :

  gnome-commander -d=cdklmn

sorry for being imprecise.
Comment 8 Christoph Korn 2009-07-02 07:06:15 UTC
Created attachment 137722 [details]
gnome-commander -d=cdkimn

This is the output of gnome-commander -d=cdkimn
Comment 9 epiotr 2009-07-09 10:22:50 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.