Your message dated Sun, 13 Jul 2014 16:19:21 +0100
with message-id 
<CAD=6czp03snzznoufzd08uuy8nr3er4jbthbweu_g_xgs7m...@mail.gmail.com>
and subject line Re: debian #666867 - nautilus: Nautilus doesn't open after 
last update
has caused the Debian Bug report #666867,
regarding nautilus: Nautilus doesn't open after last update
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
666867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666867
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nautilus
Version: 3.2.1-3
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Maintainer,

After update my system with last gnome 3.4 packages from sid, nautilus stoped
to work.

The follow message is showed when i try open it through terminal.

flamarion@litletree:~$ env LANG=C nautilus
Could not register the application: Method `DescribeAll' returned type
`(a(savbav))', but expected `(a{s(bgav)})'

and with my LANG, the problem is the same.

flamarion@litletree:~$ nautilus
Could not register the application: O método "DescribeAll" retornou o tipo
"(a(savbav))", mas é esperado "(a{s(bgav)})"

This behaviour made me install another file manager as temp solution for
navigate in directories.

If exist one more step to test, please let me know for to send more information
about this possible problem.

Thank you,



- -- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nautilus depends on:
ii  desktop-file-utils         0.18-1
ii  gsettings-desktop-schemas  3.2.0-2
ii  gvfs                       1.10.1-3
ii  libatk1.0-0                2.4.0-1
ii  libc6                      2.13-27
ii  libcairo-gobject2          1.12.0-2
ii  libcairo2                  1.12.0-2
ii  libexempi3                 2.2.0-1
ii  libexif12                  0.6.20-2
ii  libfontconfig1             2.8.0-3.1
ii  libfreetype6               2.4.9-1
ii  libgail-3-0                3.2.3-1
ii  libgdk-pixbuf2.0-0         2.26.0-2
ii  libglib2.0-0               2.32.0-3
ii  libglib2.0-data            2.32.0-3
ii  libgnome-desktop-3-2       3.2.1-3
ii  libgtk-3-0                 3.2.3-1
ii  libnautilus-extension1a    3.2.1-3
ii  libnotify4                 0.7.5-1
ii  libpango1.0-0              1.30.0-1
ii  libselinux1                2.1.9-4
ii  libtracker-sparql-0.14-0   0.14.0-2
ii  libx11-6                   2:1.4.4-4
ii  libxml2                    2.7.8.dfsg-7
ii  nautilus-data              3.2.1-3
ii  shared-mime-info           0.90-1

Versions of packages nautilus recommends:
ii  brasero          3.2.0-4
ii  eject            2.1.5+deb1+cvs20081104-10
ii  gnome-sushi      0.4.0-1
ii  gvfs-backends    1.10.1-3
ii  librsvg2-common  2.36.0-4

Versions of packages nautilus suggests:
ii  eog                    3.2.2-2+b1
ii  evince [pdf-viewer]    3.2.1-1+b1
ii  totem                  3.0.1-8
ii  tracker                <none>
ii  vlc [mp3-decoder]      1:2.0.1-0.0
ii  vlc-nox [mp3-decoder]  1:2.0.1-0.0
ii  xdg-user-dirs          0.14-1

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJPeOKsAAoJEJhPZF0zwv0zMrUP+gMqXoJCJ0heQEXMq0Ppu51W
hdNLSdw5WGgc+q34doKggLibuwOTbd4TRJj5FOkmgWBw7renWTC6tud2tPT8dzMy
KMQ3Jpb6Ob9txZKwH21CYcvqTAwj+f5gFOVBkp7iMTOIBN0NdgSgN4phhVskxmnV
VAhvUTuhzlAzZc1Dqc9x3ajCkNFk9ckpTWbGrstBD2SxhDyapXWtU4sjxpkG0rUp
o6jSn7SeVy8LmbgO+kSrn/D7l/Vtcs1xHYt2cZpNsrEwJcaAbw8Gz8mRBi+ODJAG
XtVhHgQt5gAj351nfR0IljNPrSYvyueEYUFPqytluLid1Eua9yFXHwCb3qRN/3YN
6wugJx6PklrV3+Eo+ntc7ygrJ6gOMqud4tvWbYdCmlWyuNutfS2mT8zF0tHpjrpC
vsc+xIfDrFktkTFXZAnUIDe8mqujN62+yF5pi1ljQN3po5l15/8gfvODKFP/VXyq
kqniJPXSeQY5/IHE3So0/Kd/WLM/BrFalIgVFO8dwlZFtScedEEu4JyB3XoXYfxg
vuEyu5iiEdrHD885Z6pcyOs0yAJ54bVp9RMYqu4ICgi6ofte5RPPWHKtkWeEuVKE
aDtArKOYg+fHrM8lpyd5zTlVS/fG1IHTSSC/4oWHHY7DnLijRuOn6PBEHa46kHEz
/xjqwJ2C0tUxuI1b2NxM
=ZOJq
-----END PGP SIGNATURE-----



--- End Message ---
--- Begin Message ---
version: 3.12.0-2

this is an old bug.

I'm closing this bug now since it seems to be fixed.

If you can still reproduce it feel free to reopen and provide more info.

thanks
regards
althaser

--- End Message ---

Reply via email to