duplicity gets stuck

Bug #1728730 reported by Tommy Pollák on 2017-10-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity worked again to my satisfaction.

Now in 17.10 there is a problem with duplicity again. It seems to get stuck after a while. I can move the mouse and see the pointer move on the display but nothing else works. Only way to get on is to power off (and power on again).
---
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tpollak 2206 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
InstallationDate: Installed on 2012-10-28 (1828 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MachineType: Dell Inc. Dell System XPS L502X
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
Tags: artful
Uname: Linux 4.13.0-16-generic i686
UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/20/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0NJT03
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: HuronRiver System
dmi.product.name: Dell System XPS L502X
dmi.sys.vendor: Dell Inc.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1728730

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected artful
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Tommy Pollák (tpollak) wrote :

Added log files and changed status from Incomplete to Confirmed.

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Tommy Pollák (tpollak) wrote :

Though I downloaded
linux-headers-4.14.0-041400rc7_4.14.0-041400rc7.201710292231_all.deb
linux-headers-4.14.0-041400rc7-generic_4.14.0-041400rc7.201710292231_i386.deb
linux-image-4.14.0-041400rc7-generic_4.14.0-041400rc7.201710292231_i386.deb
and executed
sudo dpkg -i *.deb
I can not see 4.14 when booting. So I listed /lib/modules
~$ ls /lib/modules/
3.11.0-19-generic 3.19.0-31-generic 3.8.0-31-generic
3.13.0-37-generic 3.2.0-45-generic-pae 4.10.0-37-generic
3.16.0-36-generic 3.5.0-37-generic 4.13.0-16-generic

Obviously I have missed to do something. What? sudo apt-get ??????

Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers