Having done some digging, heavily guided by persia on irc (thanks
persia), it seems the bug is actually in apt not adept. Specifically it
seems to be in the file acquire-worker.cc.
#8 in the backtrace mentions a call to pkgAcqArchive::Failed from
pkgAcqArchive::RunMessages. #9 shows that this function belongs to
/usr/lib/libapt-pkg-libc6.4-6.so.3.53
Having downloaded and unpacked the feisty source for apt running `grep
-r pkgAcquire::Worker::RunMessages *` over the directory returns
apt-0.6.46.4ubuntu10/apt-pkg/acquire-worker.cc:bool
pkgAcquire::Worker::RunMessages()
so the Run::Messages() function is in acquire-worker.cc. Looking through
that file RunMessages() is defined on line 185. Scrolling further down
the call to Failed() is on line 317. This is part of a case block
starting on line 296, which says that the block which seems to be
causing the problem is executed when `case 400` occurs. The comment on
line 294 indicates that case 400 occurs when there is a URI failure.
It's hard to know for certain but it seems possible that this refers to
a URI from the apt sources.list file. This could be caused by a flaky
internet connection but it's hard to know for sure.
This gives us two problems. If the network connection is flaky some URIs
won't load. Not much we can do about a flaky network unfortunately
although this seems to be the cause of the users problem. Secondly under
certain (unknown) circumstances, when libapt receives a 400 error, it
can crash, rather than providing a useful error to the calling program,
for retry or user feedback. This probably is a bug but it's hard to know
what causes the crash without seeing points #0-#5 of the backtrace. If
either of the people who have commented on this bug could supply that it
would be a big help. Alternatively, more information on which packages
were being installed would help so we could try to reproduce it.
thanks,
Rich
** Changed in: apt (Ubuntu)
Sourcepackagename: adept => apt
Assignee: (unassigned) => Richard Birnie
Status: New => Incomplete
** Tags added: need-i386-retrace
** Summary changed:
- adept crash when downloading packages in feisty
+ apt crashes when wireless connection fails
--
apt crashes when wireless connection fails
https://bugs.launchpad.net/bugs/103593
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
