[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: snapd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950855
T
I'm currently not able to get this version of the application running.
cura said, they are not providing any support for usb printing anymore,
since their own printers do not use USB printing anymore, and they don't
care about other printers.
I'd have to install the software directly, not as a sna
We should be able to suppress the warnings by generating "deny" rules in
snapd. What is important now to know is if the application can work even
without the rules you manually added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Well, at least they are needed to get rid of lots of highly annoying
warning messages in lots of warning widgets Lubuntu keeps displaying
when running it. The warning messages just keep you away from beeing
able to work normally.
--
You received this bug notification because you are a member of U
Are you sure the AppArmor changes are definitely required? If so this
would to be done by adding these accesses to an appropriate interface
within snapd (via a code-change to snapd itself -
https://github.com/snapcore/snapd/) - and once that has been released,
making sure the snap author plugs this
Now it is
Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial
adapter
crw-rw-r--+ 1 root root 189, 4 Nov 18 23:49 /dev/bus/usb/001/005
getfacl !$
getfacl /dev/bus/usb/001/005
getfacl: Removing leading '/' from absolute path names
# file: dev/bus/usb/001/005
# owner: root
# g
You can collect a strace of the app by running:
snap run --strace='-vf -s 256' cura-slicer.cura
And yes, as @alexmurray indicated, this may be something with device
cgroups. The problem with those is there is nothing logged if access is
denied, making the debugging process complicated.
Assumi
So if the change to the AppArmor profile hasn't helped (other than to
silence this message) then I suspect that is not the real issue. Perhaps
this is related to the snap's device cgroup?
There is good documentation on debugging snaps at
https://forum.snapcraft.io/t/debugging-snaps/18420 - in par
The apparmor changes brought some minor improvement, now there's no more
apparmor messages at all from the cura snap.
I am somewhat familiar with AppArmor, but wasn't aware that there are
files for editing. I thought the apparmor profiles are dynamically
created by snapd when starting a snap.
It
output of journalctl -t audit -b0 attached
** Attachment added: "journalctl -t audit -b0"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1950855/+attachment/5541213/+files/audit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I think @mardy meant:
journalctl -t audit
And to only show messages from the current boot cycle, not the entire
history, you can run it as:
journalctl -t audit -b0
You can manually edit the apparmor profile for cura-slicer to add this
access and see if it helps - add a line like the following t
I do not have a journald command on my ubuntu 20.04 system.
apt-file search journald | fgrep /bin/
reports nothing, so it doesn't seem to be installable.
There is a /lib/systemd/systemd-journald but it doesn't take arguments:
/lib/systemd/systemd-journald -t audit
This program takes one or no
Hi Hadmut, and thanks for reporting this. Could you please paste the
full journald audit log (`journald -t audit`)? I'd like to see if those
AppArmor denials you are seeing are the only ones, or if there's more.
I cannot see any interface in snapd that would grant access to the
"/sys/devices/pnp*"
13 matches
Mail list logo
