hangs on packages libfm4 and libfm-extra4

Bug #1522563 reported by Jeffery Wilkins
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
debsums (Debian)
Fix Released
Unknown
debsums (Ubuntu)
Fix Released
High
Unassigned

Bug Description

not really sure what the bug is exactly but what I tested was

# debsums libfm-extra4
/usr/lib/x86_64-linux-gnu/libfm-extra.so.4.0.3 OK

after this it just hangs with high cpu usage

# debsums libfm4
/usr/lib/x86_64-linux-gnu/libfm.so.4.0.3 OK
/usr/share/doc/libfm4/AUTHORS OK
/usr/share/doc/libfm4/NEWS.gz OK
/usr/share/doc/libfm4/README OK

after this it just hangs with high cpu usage

will try to reinstall these packages and reply back if the problem persists

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: debsums 2.1.2
ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.2-0ubuntu8
Architecture: amd64
Date: Thu Dec 3 11:53:14 2015
PackageArchitecture: all
SourcePackage: debsums
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jeffery Wilkins (djcanadianjeff) wrote :
Revision history for this message
Jeffery Wilkins (djcanadianjeff) wrote :

root@xubuntu:/tmp# apt-get install --reinstall libfm4 libfm-extra4
Reading package lists... Done
Building dependency tree
Reading state information... Done
Need to get 133 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ca.archive.ubuntu.com/ubuntu/ xenial/universe libfm-extra4 amd64 1.2.3-0ubuntu1 [14.6 kB]
Get:2 http://ca.archive.ubuntu.com/ubuntu/ xenial/universe libfm4 amd64 1.2.3-0ubuntu1 [118 kB]
Fetched 133 kB in 0s (239 kB/s)
(Reading database ... 356823 files and directories currently installed.)
Preparing to unpack .../libfm-extra4_1.2.3-0ubuntu1_amd64.deb ...
Unpacking libfm-extra4 (1.2.3-0ubuntu1) over (1.2.3-0ubuntu1) ...
Preparing to unpack .../libfm4_1.2.3-0ubuntu1_amd64.deb ...
Unpacking libfm4 (1.2.3-0ubuntu1) over (1.2.3-0ubuntu1) ...
Setting up libfm-extra4 (1.2.3-0ubuntu1) ...
Setting up libfm4 (1.2.3-0ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu4) ...
root@xubuntu:/tmp# debsums libfm4
/usr/lib/x86_64-linux-gnu/libfm.so.4.0.3 OK
/usr/share/doc/libfm4/AUTHORS OK
/usr/share/doc/libfm4/NEWS.gz OK
/usr/share/doc/libfm4/README OK
/usr/share/doc/libfm4/changelog.Debian.gz OK
/usr/share/doc/libfm4/copyright OK
root@xubuntu:/tmp# debsums libfm-extra4
/usr/lib/x86_64-linux-gnu/libfm-extra.so.4.0.3 OK
/usr/share/doc/libfm-extra4/changelog.Debian.gz FAILED
/usr/share/doc/libfm-extra4/copyright OK
root@xubuntu:/tmp#

Changed in debsums (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in debsums (Ubuntu):
status: New → Confirmed
Revision history for this message
Ryo Onodera (ryoqun) wrote :

I've encountered with similar problem for the package libfuse2.

After some investigation, it seems that this is caused by an infinite loop inside resolve_path.

After this tiny hack, it finished to work:

```
ryoqun@miyako:~$ diff -u /usr/bin/debsums{?*,}
--- /usr/bin/debsums.backup 2016-10-26 13:12:30.157544031 +0900
+++ /usr/bin/debsums 2016-10-26 13:33:01.565480144 +0900
@@ -427,7 +427,9 @@
     my $path = shift;
     my @tokens = split(/\//, $path);
     my @parts = ();
- while (@tokens) {
+ my $loop_count = 0;
+ while (@tokens && $loop_count < 2000) {
+ $loop_count++;
         my $token = shift @tokens;
         next if $token eq '.' || $token eq '';
         if ($token eq '..') {
@@ -443,6 +445,9 @@
             push @parts, $token;
         }
     }
+ if ($loop_count >= 2000) {
+ warn "maybe infinite loop: $path ";
+ }
     return join('/', @parts);
 }

```

Axel Beckert (xtaran)
Changed in debsums (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Debian Perl Group (pkg-perl-maintainers)
Changed in debsums (Ubuntu):
importance: Undecided → High
Revision history for this message
Nate Eldredge (nate-thatsmathematics) wrote :

I encountered this with libfl-dev. The cause is apparently a symlink loop:

lrwxrwxrwx 1 root root 27 Feb 28 2016 /usr/share/doc/libfl-dev/NEWS.Debian.gz -> ../libfl-dev/NEWS.Debian.gz

Revision history for this message
Dominique Dumont (domi-dumont) wrote :

I've uploaded a new package in Debian with a fix for this issue.

All the best

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package debsums - 2.1.3

---------------
debsums (2.1.3) unstable; urgency=medium

  * Team upload.

  [ Axel Beckert ]
  * debian/README.source: Explain the new version numbering scheme, refers
    to Semantic Versioning (http://semver.org/).
  * Declare compliance with Debian Policy 3.9.8. (No changes needed.)
  * Bump debhelper compatibility to 9 as recommended.
    + Update versioned debhelper build-dependency accordingly.

  [ Salvatore Bonaccorso ]
  * debian/control: Use HTTPS transport protocol for Vcs-Git URI

  [ gregor herrmann ]
  * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
  * Remove Ryan Niebur from Uploaders. Thanks for your work!

  [ Dominique Dumont ]
  * protect against symlink loop (Closes: #822633) (LP: #1522563)

 -- Dominique Dumont <email address hidden> Tue, 15 Nov 2016 07:52:19 +0100

Changed in debsums (Ubuntu):
status: In Progress → Fix Released
Changed in debsums (Debian):
status: New → Fix Released
Revision history for this message
Ryo Onodera (ryoqun) wrote :

Thanks for fixing this!!!

So, when is this released to xenial??

Axel Beckert (xtaran)
Changed in debsums (Ubuntu):
assignee: Debian Perl Group (pkg-perl-maintainers) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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