desktop-packages team mailing list archive

[jondee <1452084@xxxxxxxxxxxxxxxxxx>]

Can confirm gvfs-ls trash:/// works fine producing the output of all the
files in the trash:// location.

I have another account on the system with plenty of files in that
trash:// works perfectly fine for. Guest mode trash:// also works
perfectly fine.

The program still crashes with SIGSEGV (__GI__IO_default_xsputn
(f=0x7fffff7ff600, data=<optimised out>, n=38) at genops.c:463) with
python-nautilus uninstalled and pruged out (I did not restart the
system, but I ensured that nautilus was completely killed before I re-
attempted the test)

I'm guessing there's probably something in my trash:// that's triggering
this right? Any particular file types I should look for? Interestingly
opening `nautilus ~/.local/share/Trash/files` causes a sefault too!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1452084

Title:
  Segmentation fault whilst opening Rubbish Bin/ trash://

Status in nautilus package in Ubuntu:
  New

Bug description:
  Package version 1:3.14.2-0ubuntu9 from http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  Ubuntu 15.04 amd64 on an i5-4670K CPU

  Hi, I'm currently getting a consistent SIGSEGV from Nautilus when
  attempting to open the rubbish bin. This happens whether I click the
  bookmark on the left or instantaneously if I run `nautilus trash://`.
  The crash occurs before the icons have fully loaded, but a second
  after the rubbish bin is selected.

  I installed the debug symbols for nautilus and ran with gdb and got
  the following output:

  (gdb) run
  Starting program: /usr/bin/nautilus 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  (nautilus:21736): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen:
  assertion 'GDK_IS_SCREEN (screen)' failed

  (nautilus:21736): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (nautilus:21736): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
  [Thread 0x7ffff7f8ba00 (LWP 21736) exited]
  [Inferior 1 (process 21736) exited normally]
  (gdb) run
  Starting program: /usr/bin/nautilus 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  nautilus-wipe-Message: Initializing
  [New Thread 0x7fffe9017700 (LWP 22649)]
  [Thread 0x7fffe9017700 (LWP 22649) exited]
  [New Thread 0x7fffc1347700 (LWP 22680)]
  [New Thread 0x7fffe35f1700 (LWP 22651)]
  [New Thread 0x7fffe3fff700 (LWP 22650)]
  [New Thread 0x7fffe9818700 (LWP 22648)]

  Program received signal SIGSEGV, Segmentation fault.
  0x00007ffff372332e in __GI__IO_default_xsputn (f=0x7fffff7ff5f0, data=0x50e080, n=6) at genops.c:447
  447	genops.c: No such file or directory.

  I can provide more info if needed as I can easily reproduce the bug. I
  know a little about using gdb as well, but may need a bit of guidance
  as I'm no hardened C programmer. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions