Error on enable autostart

Bug #1756630 reported by Aldo Esteban Paz
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Fix Released
Arthur Borsboom

Bug Description

Preferences -> Startup
On set "Start Xpad automatically after login" gives the error "Error enabling Xpad autostart" if the autostart directory (~/.config/autostart) not exists.

Version: 4.8.0-1
OS: Ubuntu 16.10

Tags: iso-testing

Related branches

Aldo Esteban Paz (apaz)
description: updated
Revision history for this message
Neyder (neyder) wrote :

Confirm this after testing final build of lubuntu

Changed in xpad:
status: New → Confirmed
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Revision history for this message
Jb (jebsolutions) wrote :

This is not a fix.

But you can manually add a startup entry by hand from an lxterminal window. I do this as part of my install script. It works for 16.04 and 18.04 and might help someone in the mean time until this gets properly fixed:

manually create the necessary directories:
mkdir -p "$(dirname "$LXDE_AUTOSTART_FILE")"
chown -R "$USERNAME:$USERNAME" "/home/$USERNAME/.config/"

appending your command to the autostart file:

Revision history for this message
Jb (jebsolutions) wrote :

When I start Xpad on the daily 18.04 the error is "Could not copy /usr/share/applications/xpad.desktop to /home/{yourusername}/.config/autostart/xpad.desktop": No such file or directory.

With {yourusername}being whatever user you logged in as.

The /home/{yourusername}/.config/ directory exists...but /home/{yourusername}/.config/autostart does not. If I make this folder the error goes away.

I'm not sure why the directory isn't created automatically.

Revision history for this message
Jb (jebsolutions) wrote :

I'm also not sure why Xpad trys to force itself to always autostart. It doesn't do this on 16.04.

Revision history for this message
sudodus (nio-wiklund) wrote :

Autostart works as usual for distros using LXDE, as described by @Jb, adding a command line to


I think this bug is specific to Xpad.

Revision history for this message
Jb (jebsolutions) wrote :

There are a few ways lxde autostarts.

xpad under Lubuntu 16.04 also uses:

I notice that under Lubuntu 16.04's light-locker is also launched this way. But under 18.04 light-locker is started some other way.

A possible quick fix/work around for xpad would be to just create the /home/$USERNAME/.config/autostart/ directory during the xpad install.

Just an fyi -- xpad looks like a nice app, but I don't use it. So I may not be commenting further on this particular bug.

Changed in xpad:
importance: Undecided → Medium
status: Confirmed → In Progress
assignee: nobody → Arthur Borsboom (arthurborsboom)
milestone: none → 5.1.0
Revision history for this message
Arthur Borsboom (arthurborsboom) wrote :

I recall one of the older versions of Xpad (4.5 / 4.6 ?), which kept setting a system-wide autostart for Xpad each time. This has been fixed in 4.7 where only the autostart for the current user is enabled and only the first time Xpad is run. So, from 4.7 and newer this autostart persistence behavior should not be happening anymore (hopefully). :)

Regarding the bug report, I managed to reproduce it. I have resolved the issue by creating the directory "home_dir%/.config/autostart" if it does not exist. The fix is submitted and will be available from v5.1

Thanks for the submitting the bug.


Changed in xpad:
status: In Progress → Fix Committed
Revision history for this message
Jb (jebsolutions) wrote :


I did notice one minor typo on line 370:
the word "directoryy" has an extra "y".

Thank you for the quick fix. I did not try your patch, but it looks good.

Thank you!

Revision history for this message
Arthur Borsboom (arthurborsboom) wrote :

Thanks for the hint of the typo.
Fix commited.

Changed in xpad:
status: Fix Committed → Fix Released
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.