| 2014-01-31 17:07:04 |
Richard Elkins |
bug |
|
|
added bug |
| 2014-01-31 17:07:50 |
Richard Elkins |
description |
Running in Trusty Alpha 2 up-to-date.
Package: xscreensaver 5.15-3ubuntu1
Subject file: /usr/bin/xscreensaver
Script:
set -x
sudo apt-get -y remove xscreensaver
sudo apt-get -y install xscreensaver
which xscreensaver
sudo apt-get -y remove xscreensaver
The execution of `which` returns the status that the file does exist. Sometime during the remove execution, some sub ordinate process goes looking for it after it was already removed by another subprocess.
I reported this against the package definition itself because I have never seen apt get confused before (my best guess). Please note that this is a minor issue and has no significant impact to Trusty operations.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xscreensaver 5.15-3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Jan 31 10:54:37 2014
InstallationDate: Installed on 2014-01-31 (0 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140126)
SourcePackage: xscreensaver
UpgradeStatus: No upgrade log present (probably fresh install) |
Running in Trusty Alpha 2 up-to-date.
Package: xscreensaver 5.15-3ubuntu1
Subject file: /usr/bin/xscreensaver
Script:
set -x
sudo apt-get -y remove xscreensaver
sudo apt-get -y install xscreensaver
which xscreensaver
sudo apt-get -y remove xscreensaver
The execution of `which` returns the status that the file does exist. Sometime during the remove execution, some subordinate process goes looking for it after it was already removed by another subprocess.
I reported this against the package definition itself because I have never seen apt get confused before (my best guess). Please note that this is a minor issue and has no significant impact to Trusty operations.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xscreensaver 5.15-3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Jan 31 10:54:37 2014
InstallationDate: Installed on 2014-01-31 (0 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140126)
SourcePackage: xscreensaver
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2014-01-31 17:09:42 |
Richard Elkins |
description |
Running in Trusty Alpha 2 up-to-date.
Package: xscreensaver 5.15-3ubuntu1
Subject file: /usr/bin/xscreensaver
Script:
set -x
sudo apt-get -y remove xscreensaver
sudo apt-get -y install xscreensaver
which xscreensaver
sudo apt-get -y remove xscreensaver
The execution of `which` returns the status that the file does exist. Sometime during the remove execution, some subordinate process goes looking for it after it was already removed by another subprocess.
I reported this against the package definition itself because I have never seen apt get confused before (my best guess). Please note that this is a minor issue and has no significant impact to Trusty operations.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xscreensaver 5.15-3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Jan 31 10:54:37 2014
InstallationDate: Installed on 2014-01-31 (0 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140126)
SourcePackage: xscreensaver
UpgradeStatus: No upgrade log present (probably fresh install) |
Running in Trusty Alpha 2 up-to-date.
Package: xscreensaver 5.15-3ubuntu1
Version of apt: 0.9.14.1ubuntu2
Subject file: /usr/bin/xscreensaver
Script:
set -x
sudo apt-get -y remove xscreensaver
sudo apt-get -y install xscreensaver
which xscreensaver
sudo apt-get -y remove xscreensaver
The execution of `which` returns the status that the file does exist. Sometime during the remove execution, some subordinate process goes looking for it after it was already removed by another subprocess.
I reported this against the package definition itself because I have never seen apt get confused before (my best guess). Please note that this is a minor issue and has no significant impact to Trusty operations.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xscreensaver 5.15-3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Jan 31 10:54:37 2014
InstallationDate: Installed on 2014-01-31 (0 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140126)
SourcePackage: xscreensaver
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2014-01-31 17:11:39 |
Richard Elkins |
attachment added |
|
`script -c myscript.sh -f script.log` https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1275015/+attachment/3964510/+files/script.log |
|
| 2014-01-31 18:46:52 |
Ubuntu QA Website |
tags |
amd64 apport-bug trusty |
amd64 apport-bug package-qa-testing trusty |
|
| 2014-02-17 19:50:57 |
Tormod Volden |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681613 |
|
| 2014-02-17 19:50:57 |
Tormod Volden |
bug task added |
|
xscreensaver (Debian) |
|
| 2014-02-17 23:56:59 |
Bug Watch Updater |
xscreensaver (Debian): status |
Unknown |
Fix Released |
|
| 2015-02-14 01:48:03 |
Richard Elkins |
xscreensaver (Ubuntu): status |
New |
Fix Released |
|
