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 771803 - Won't start. Exits with error
Won't start. Exits with error
Status: RESOLVED NOTGNOME
Product: nautilus
Classification: Core
Component: Crashers
3.21.x
Other Linux
: Normal blocker
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-09-22 03:33 UTC by Rob Stone
Modified: 2016-09-22 12:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rob Stone 2016-09-22 03:33:35 UTC
After applying updates nautilus starts up and fails. See below:-

Sep 22 13:11:45 roblaptop gnome-terminal-[4279]: GtkScrollbar 0x55e3d99522f0 is drawn without a current allocation. This should not happen.
Sep 22 13:11:52 roblaptop /usr/lib/gdm3/gdm-x-session[2804]: Activating service name='org.gnome.Nautilus'
Sep 22 13:11:52 roblaptop org.gnome.Nautilus[2834]: /usr/bin/nautilus: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnome-autoar-0.so.0: undefined symbol: archive_entry_is_encrypted
Sep 22 13:11:52 roblaptop /usr/lib/gdm3/gdm-x-session[2804]: Activated service 'org.gnome.Nautilus' failed: Process org.gnome.Nautilus exited with status 127



root@roblaptop:/var/log# nautilus --version
nautilus: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnome-autoar-0.so.0: undefined symbol: archive_entry_is_encrypted
root@roblaptop:/var/log# 

package versions

nautilus          3.21.91.1-1
nautilus-actions  3.2.3-1+b1
nautilus-data     3.21.91.1-1
nautilus-sendto   3.8.4-1
Comment 1 Mohammed Sadiq 2016-09-22 03:52:42 UTC
What version of libarchive13 are you using? You require at least 3.2.0 (which is present in Debian testing)

See bug 770735 for some details.
Comment 2 Carlos Soriano 2016-09-22 07:43:25 UTC
Yeah, seems you are missing gnome-autoar, how do you built nautilus?
Comment 3 Rob Stone 2016-09-22 08:06:59 UTC
I upgraded libarchive13 and nautilus is now loading.
There must be a dependency link missing on the Debian packages.

Thanks for your quick response.
Comment 4 Carlos Soriano 2016-09-22 08:09:35 UTC
(In reply to Rob Stone from comment #3)
> I upgraded libarchive13 and nautilus is now loading.
> There must be a dependency link missing on the Debian packages.
> 
> Thanks for your quick response.

We have hard requirements on those. How is possible that this happened?

I would like to make sure we didn't do anything wrong on our side.
Comment 5 Mohammed Sadiq 2016-09-22 08:39:14 UTC
(In reply to Carlos Soriano from comment #4)
> We have hard requirements on those. How is possible that this happened?
> 
> I would like to make sure we didn't do anything wrong on our side.

Debian Stretch GNU/Linux (current testing) does have libarchive13 version 3.2.0+. The older Debian (Debian Jessie) have version 3.1.x. But gnome-autoar doesn't have a versioned dependency on libarchive13. 
So when someone updgrades his/her system from Jessie to Stretch it is possible that libarchive13 wasn't upgraded, but a fresh install won't cause any issue (the same is the case for Ubuntu too). It should be fixed downstream.

Rob Stone: can you please file a bug on this at Debian bugs?
Comment 6 Carlos Soriano 2016-09-22 09:10:45 UTC
(In reply to Mohammed Sadiq from comment #5)
> (In reply to Carlos Soriano from comment #4)
> > We have hard requirements on those. How is possible that this happened?
> > 
> > I would like to make sure we didn't do anything wrong on our side.
> 
> Debian Stretch GNU/Linux (current testing) does have libarchive13 version
> 3.2.0+. The older Debian (Debian Jessie) have version 3.1.x. But
> gnome-autoar doesn't have a versioned dependency on libarchive13. 
> So when someone updgrades his/her system from Jessie to Stretch it is
> possible that libarchive13 wasn't upgraded, but a fresh install won't cause
> any issue (the same is the case for Ubuntu too). It should be fixed
> downstream.
> 
> Rob Stone: can you please file a bug on this at Debian bugs?

I don't understand. gnome-autoar has a hard dependency on libarchive.
https://git.gnome.org/browse/gnome-autoar/tree/configure.ac?h=gnome-3-22#n57
Comment 7 Mohammed Sadiq 2016-09-22 09:20:17 UTC
(In reply to Carlos Soriano from comment #6)
> I don't understand. gnome-autoar has a hard dependency on libarchive.
> https://git.gnome.org/browse/gnome-autoar/tree/configure.ac?h=gnome-3-22#n57

Sure. There is no issue with the dependency here. The problem is only in debian.

gnome-autoar debain package[0] depends on libarchive13, but isn't bound to any version.

So see this case: The user was using Debian Jessie, and have already installed libarchive13, which is at version 3.1.x. Now at some point the user upgraded the system (or just nautilus). Which shall install nautilus 3.22, and the gnome-autoar dependency. But as gnome-autoar doesn't care about the version of libarchive13 (as per Debian dependency rules done downstream), and as the system already have libarchive13, the package may not be upgraded causing undefined symbol issue, and thus segfault.

[0] https://packages.debian.org/stretch/libgnome-autoar-0-0
Comment 8 Carlos Soriano 2016-09-22 12:25:57 UTC
Ok so closing as this is downstream.

Although autoar needs a new release to have the fix for double checking the hard dep.