Ubuntu
sddm package

package sddm (not installed) failed to install/upgrade: conffile name 'usr/share/sddm/scripts/Xsetup' is not an absolute pathname

Bug #1891068 reported by Lawson Vaughan
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
sddm (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

SDDM Failed to install

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: sddm (not installed)
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu44
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Aug 10 18:28:17 2020
ErrorMessage: conffile name 'usr/share/sddm/scripts/Xsetup' is not an absolute pathname
InstallationDate: Installed on 2020-08-10 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200728)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu1
 apt 2.1.9
SourcePackage: sddm
Title: package sddm (not installed) failed to install/upgrade: conffile name 'usr/share/sddm/scripts/Xsetup' is not an absolute pathname
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Changed in sddm (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel Letzeisen (dtl131) wrote :

https://git.launchpad.net/ubuntu/+source/sddm/commit/debian/conffiles?id=decb2c92d000e8c771f7f0d1c2bba9e1b6be5e98

I subscribed the maintainer that made ^that change. I understand the error message and logical solution (add '/' in front of paths listed in that file), but I'm not sure why the error is just appearing now.

Revision history for this message
Rik Mills (rikmills) wrote :

> I'm not sure why the error is just appearing now

Because of this change in the latest dpkg.

"dpkg-deb, dpkg: Do not accept relative pathnames in DEBIAN/conffiles."

Rik Mills (rikmills)
Changed in sddm (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sddm - 0.18.1-1ubuntu3

---------------
sddm (0.18.1-1ubuntu3) groovy; urgency=medium

  * debian/conffiles: Switch to using absolute paths, which are now
    being enforced by the latest dpkg. (LP: #1891068)

 -- Rik Mills <email address hidden> Thu, 13 Aug 2020 07:43:10 +0100

Changed in sddm (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Daniel Letzeisen (dtl131) wrote :

Thank you, Rik. I figured it was something like that.

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

Other bug subscribers

Remote bug watches

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