canonical / ubuntu-core-desktop Goto Github PK

I have the simple-scan snap in candidate (44.0, Rev 792) on a core desktop system. When I scan a document and click the download button, the default location it tries to open, as a suggested download location, gives a permissions error. This is because the default location opened is /run/user/1001/doc, which nobody will have access to. This happens on the firefox snap as well, so I suspect this is a shared issue.

You can still click OK and then go select another location like ~/Downloads and download the document just fine though.

UPower clients usually connects to the standard DBus signal org.freedesktop.DBus.Properties.PropertiesChanged to detect changes in the properties of a device, like the battery percentage or the charging/on-battery flag. But, for some reason, in the current images of ubuntu-core-desktop, this signal isn't received by the clients if they are snapped. In a normal Ubuntu desktop, the same snap does receive the notifications. Also, running the binary outside the snap, as root, it does receive the signals.

The current SNAPD code has specific apparmor configuration to allow to pass the PropertiesChanged signals:

To test this, you can download this snap: https://drive.google.com/file/d/1nsPB2amxZaqy5uy5bLAKg2mpvXqmq_L8/view?usp=share_link

Installing it in the system and running it with "snap run upower-test" will show all the properties for the path "/org/freedesktop/UPower/devices/battery_BAT0". Any change on their properties will also be notified (like when the power cord is connected/disconnected).

Running it in a classic Ubuntu desktop, it will work fine (as long as the "upower-observer" plug is connected, of course).

Running it in an ubuntu-core-desktop laptop will read all the properties, but won't detect the signals.

In the same ubuntu-core-desktop system, going to the root terminal and running it directly ("/snap/upower-test/current/usr/bin/upower") will work fine, showing all the properties and detecting the signals.

The ubuntu-core-desktop README file says:

This directory contains an image of Ubuntu Core 22 with the GDM display manager loaded into the boot file system. It can be launched in a Qemu virtual machine by following these instructions:

Download and decompress the two image files and place them in the same directory.   

and the README then says:

• Add an image as a VM launchable from GNOME Boxes or virt-manager:_

Is Canonical going to add/include LXD's VM capability in this README as well?
Including any specific install/config instructions to start/utilize ubuntu-core-desktop in an LXD VM.

Hi,

I have downloaded a image from actions and I am going to use it on my secondary device in order to transition my current workflow into all Snap and Workshops LXC containers. I am wondering if I'll be able to update the installed OS from Settings or Terminal (apt upgrade)? Please let me know.

Best regards,

Most modern printers are driverless IPP printers, and their driverless IPP does not only work via network connections but also via USB, using the IPP-over-USB standard. To support this in Ubuntu Core Desktop, the "ipp-usb" Snap needs to get seeded. Once done this, driverless printers connected via USB are immediately available. The printer's internal web admin interface can then be accessed via http://localhost:60000/.

I have been looking at this project to examine whether an immutable version of the budgie desktop is possible.

I have been looking at adding and removing snaps, generating images etc.

I can see that I will need a slight tweaks and a tuck with the ubuntu-session snap for us.

But I am missing the obvious ... what is the snap/snaps project(s) that is/are actually installing gnome-shell plus GDM? Initially I would need to look at substituting gnome-shell with budgie. Eventually replacing GDM with lightdm or similar.

TIA