hangs while opening trash if there are files with emblems inside

mitya57, could you please run the command "apport-collect 553082" in a terminal. This will attach information to the bug report that may be helpful to the developers.

I Have reported this bug upstream, you can track its status and comment at https://bugzilla.gnome.org/show_bug.cgi?id=614544

I already uploaded this to the upstream bug, but I will put it here as well in case it can be of any help.

Thank you for sending the bug to GNOME there

> Could you please run the command "apport-collect 553082"
I've done it

Mitya57, It must not have worked, but o well I do not think it will be needed for this bug. For future reference it is best to report bugs by opening a terminal and typing "apport-collect <packagename>", this will automatically gather some relevant information and attach it to the bug report.

Today, the patch for gvfs was released (see https://bugzilla.gnome.org/show_bug.cgi?id=614544). Can you apply it before the release candidate?

the upstream bug has a change to fix the issue now which has been uploaded to lucid

the issue is a gvfs one

suitable for SRU, but doesn't justify a respin of RC or an additional change between RC and final. Rejected from the unapproved queue, please reupload to lucid-proposed.

Is it uploaded? I still don't get it in lucid-proposed repository.

Fix commited means it is not uploaded yet, fixed release means it is uploaded.

the fix will go in a lucid stable update

I upgraded gvfs from our current git snapshot to 1.6.1 final, which fixes this bug and updates 3 translation .po files. (In LTS versions we routinely update GNOME to new upstream bug fix microreleases).

I attach a debdiff to current lucid version, with the autoconf noise filtered out.

Tested locally, I'll upload to lucid-proposed in a minute, awaiting SRU team approval/review.

Accepted gvfs into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Yes, it seems to be fixed.

I've tested the proposed package and the issue is indeed fixed with it, marking this as verification done, thanks all.

This bug was fixed in the package gvfs - 1.6.1-0ubuntu1

---------------
gvfs (1.6.1-0ubuntu1) lucid-proposed; urgency=low

  * New upstream bug fix release. Compared to the last git snapshot, this
    changes:
    - client: Don't loop on problematic dbus input (LP: #553082)
    - Translation updates
  * Remove 01_dont_ignore_blank_cd_drives.patch: Applied upstream.
 -- Martin Pitt <email address hidden> Tue, 27 Apr 2010 12:51:26 +0200

Copied lucid-proposed to maverick.

Bah, I can't release this due to a Launchpad bug:

2010-05-11 09:55:18 ERROR gvfs 1.6.1-0ubuntu1 in lucid (binaries conflicting with the existing ones)

I accepted a no-change rebuild to also get powerpc binaries, so these need to be re-tested.

I've tested with 1.6.1-0ubuntu1build1 from lucid-proposed and my Nautilus window still hangs when opening the trash that already contains an icon with an emblem created with the older GVFS. Does the fix simply address files with emblems added after installing 1.6.1-0ubuntu1build1 from lucid-proposed?

No, it should not be so. With gvfs 1.6.1-0ubuntu1, my nautilus opened trash which it didn't open earlier, and it stills opens it. But with 1.6.1-0ubuntu1build1 if I delete file with emblem, I cannot find it in the trash. I think it's something wrong with this build1.

I suggest that a bug of the trash not working in an operating system merits a label of more than "low importance." A sophisticated user will figure out how to empty the trash by browsing to it, but a newbie will likely go back to Windows or Mac. It could be a deal-breaker for them.

Anyway, thank you for working on this important bug!

did you restart your session? could you describe how you tested? the current stable update does fix the issue there but the comments added previously are blocking the update to be accepted in lucid-updates now

the emblem not being displayed is an another issue than the one adressed there, it's better to have this bug that nautilus hanging

The bug report is about nautilus hanging when a file with an emblem is moved to the trash, that's fixed by the proposed package and i can confirm that. The part of nautilus/trash not showing that file is another bug to be fixed, please let's keep one issue per bug. Marking this as verification done, thanks all.

This bug was fixed in the package gvfs - 1.6.1-0ubuntu1build1

---------------
gvfs (1.6.1-0ubuntu1build1) lucid-proposed; urgency=low

  * No-change rebuild to get the missing powerpc binaries.

gvfs (1.6.1-0ubuntu1) lucid-proposed; urgency=low

  * New upstream bug fix release. Compared to the last git snapshot, this
    changes:
    - client: Don't loop on problematic dbus input (LP: #553082)
    - Translation updates
  * Remove 01_dont_ignore_blank_cd_drives.patch: Applied upstream.
 -- Martin Pitt <email address hidden> Wed, 12 May 2010 11:47:17 +0200

Pedro Villavicencio wrote:
> The part of nautilus/trash not showing that file is another bug to be fixed
I created a new Bug #587172.

Why hasn't hit the archives yet? I see the new one is set for low urgency, but a crashing nautilus that can't open the Trash folder seems a pretty important regression.

not sure what you are asking, the update has been accepted in lucid--updates see the bug comments

Could you please apply the second patch from https://bugzilla.gnome.org/show_bug.cgi?id=614544 too?
It fixes bug #587172.

Tomas Bzatek [gvfs developer] 2010-06-25 12:59:21 UTC
> Have you tried applying both patches? The first one has been already committed
> and the other is still needed too. Works fine for me for the scenario described
> in [lp bug #587172]