SVN crashes on svn:// login with: svn assert failure

Bug #1287725 reported by Remco Brenninkmeijer
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
subversion (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

When I try to connect to even an empty repo through svn protocol it crashes with a coredump.
I am running Ubuntu 14.04 beta1

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: subversion 1.8.8-1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AssertionMessage: svn: /build/buildd/subversion-1.8.8/subversion/libsvn_subr/dirent_uri.c:1315: svn_uri_basename: Assertion `svn_uri_is_canonical(uri, ((void *)0))' failed.
CurrentDesktop: Unity
Date: Tue Mar 4 14:45:49 2014
ExecutablePath: /usr/bin/svn
InstallationDate: Installed on 2014-02-08 (23 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140208)
ProcCmdline: svn co svn://maxe:backupsystem
Signal: 6
SourcePackage: subversion
StacktraceTop:
 __assert_fail_base (fmt=0x7f09dfd554b8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f09e043f550 "svn_uri_is_canonical(uri, ((void *)0))", file=file@entry=0x7f09e043f328 "/build/buildd/subversion-1.8.8/subversion/libsvn_subr/dirent_uri.c", line=line@entry=1315, function=function@entry=0x7f09e043fa90 "svn_uri_basename") at assert.c:92
 __GI___assert_fail (assertion=0x7f09e043f550 "svn_uri_is_canonical(uri, ((void *)0))", file=0x7f09e043f328 "/build/buildd/subversion-1.8.8/subversion/libsvn_subr/dirent_uri.c", line=1315, function=0x7f09e043fa90 "svn_uri_basename") at assert.c:101
 svn_uri_basename () from /usr/lib/x86_64-linux-gnu/libsvn_subr-1.so.1
 ?? ()
 ?? ()
Title: svn assert failure: svn: /build/buildd/subversion-1.8.8/subversion/libsvn_subr/dirent_uri.c:1315: svn_uri_basename: Assertion `svn_uri_is_canonical(uri, ((void *)0))' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Remco Brenninkmeijer (requist1) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in subversion (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in subversion (Ubuntu):
status: New → Confirmed
Revision history for this message
Remco Brenninkmeijer (requist1) wrote :

It was a long time ago but if I remember correct it appeared to be a server problem which causes the dump at the client side.

So the message is being given if the repository can not be reached. (Same thing will happen if you try to checkout from a server which does not run subversion).

<b>Definitely a user-error, but especially considering the likeliness of this error it should rather result in a nice user message instead of this core dump. </b>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.