Cannot execute oem-config-prepare - application is not trusted

Bug #1712581 reported by Jean-Baptiste Lallement
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Default settings and artwork for Baltix OS
Triaged
High
Mantas Kriaučiūnas
casper (Baltix)
Confirmed
High
Mantas Kriaučiūnas
ubiquity (Ubuntu)
Fix Released
High
Jean-Baptiste Lallement

Bug Description

artful desktop 20170823

When the user clicks on the oem-config-prepare-icon on the desktop, it cannot be executed directly and there is a dialog saying that the application is not trusted (cf screenshot - in french)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 23 15:25:15 2017
InstallationDate: Installed on 2013-09-03 (1449 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
Revision history for this message
Iain Lane (laney) wrote : Re: [Bug 1712581] [NEW] Cannot execute oem-config-prepare - application is not trusted

On Wed, Aug 23, 2017 at 01:29:21PM -0000, Jean-Baptiste Lallement wrote:
> Public bug reported:
>
> artful desktop 20170823
>
> When the user clicks on the oem-config-prepare-icon on the desktop, it
> cannot be executed directly and there is a dialog saying that the
> application is not trusted (cf screenshot - in french)

I'm not working on this (at least not right now), but in case somebody
wants to pick it up, see scripts/casper-bottom/25adduser in casper.
Specifically, to mark the .desktop file as trusted, run something like:

    if [ -x "/root/usr/bin/dbus-run-session" ] && [ -x "/root/usr/bin/gio" ]; then
        chroot /root sudo -i -u $USERNAME dbus-run-session -- gio set /home/$USERNAME/Desktop/$(basename "$file") metadata::trusted true
    fi

Obviously the chroot bit may or may not be appropriate - I don't know
how this desktop file is installed.

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

Changed in ubiquity (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Jean-Baptiste Lallement (jibel)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 17.10.7

---------------
ubiquity (17.10.7) artful; urgency=medium

  [ Jean-Baptiste Lallement ]
  * Mark the files for oem-config as trusted so they are properly handled by
    nautilus. (LP: #1712581)

  [ Iain Lane ]
  * ubi-console-setup.py: Set DPKG_MAINTSCRIPT_{NAME,PACKAGE} variables for
    our manual running of keyboard-configuration.postinst. This script now
    runs dpkg-maintscript-helper to remove an old conffile. That code won't
    fire in ubiquity, but we still need to not error out. (LP: #1715605)

 -- Mathieu Trudel-Lapierre <email address hidden> Thu, 07 Sep 2017 11:02:30 -0400

Changed in ubiquity (Ubuntu):
status: Triaged → Fix Released
Changed in baltix-default-settings:
assignee: nobody → Mantas Kriaučiūnas (mantas)
importance: Undecided → High
status: New → Triaged
Changed in casper (Baltix):
importance: Undecided → High
assignee: nobody → Mantas Kriaučiūnas (mantas)
Changed in casper (Baltix):
status: New → Confirmed
Changed in casper (Baltix):
milestone: none → baltix-18.04
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.