On 18.03.2024 18:42, Dmitry Kasatkin wrote:
[...]
>> To address this issue, change the project license to GPL-2.0-or-later
>> and libimaevm to LGPL 2.0 or later.
Acked-by: Alberto Mardegan
--
С уважением,
Альберто Мардеган
Ведущий разработчик
https://auroraos.ru/
Hi all!
I've recently bumped into an issue on AuroraOS (a fork of
SailfishOS), where as soon as an application window gets created, the
output gets filled with logs similar to these, and the application gets
stuck:
[W] unknown:230 - qrc:/Sailfish/Silica/private/TabBar.qml:230:5: QML
Hi Colin,
thanks for your extensive reply, and for debugging this!
On 24/11/22 21:10, Colin Watson wrote:
[...]
and I see from that that you have your qbs-in-lts PPA configured to
build against ppa:ubuntu-toolchain-r/ubuntu/test. Do you have to use
that PPA? As I understand it it's not at
Hi all,
yesterday a daily recipe of mine failed to build on Bionic (on Jammy
and Focal it succeeded) because the "qbs" dependency could not be found.
But since the last successful Bionic build (which happened in June) I
did not change the build depends of this project, so I'm a bit at a loss
Добрый день, Олег! The bug you are hitting is actually not related to
this one, and is bug 1621102. You can try with a bind-mount instead.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Thanks Simon for confirming.
** Changed in: snapd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1900679
Title:
[snap]
At least some of these seem could have been fixed by
https://github.com/snapcore/snapd/pull/12127 (which has been merged in
master, but is not part of any release yet).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Hi Alexandre, there's no need to file a different bug, I just tagged
this one as affecting "linux (Ubuntu)" as well (the launchpad "linux"
project is actually the kernel.
You just need to run the command mentioned in comment #12 to provide the
extra information needed.
--
You received this bug
Thanks Alex and John for jumping in -- I did some investigation and I'm
more and more persuaded that this is indeed a kernel (AppArmor bug).
The good thing is that this is 100% reproducible by just installing the
latest 22.10 daily images: firefox starts with warnings, and slack does
not start at
Hi all!
On some occasions I've found myself in need of debugging the
executable under gdb, strace and valgrind. Running
gdb ./default/install-root/usr/local/bin/MyApp
has always worked well for me, but I wonder:
1) Would this break if the app depends on shared libraries existing in
Small update: we have now merged a change that allows snaps to work on
system where the users' home directories are not /home// but
/home///https://bugs.launchpad.net/snapd/+bug/1620771
instead.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hi AG-Ubrio, the profile that you should check is not the lightdm one,
but this:
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox
It doesn't matter much, though, since this also has the rule
/tmp/** mrwlkix,
Can you please check in the logs, if you get some apparmor denials when
Hi AG-Ubrio, the profile that you should check is not the lightdm one,
but this:
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox
It doesn't matter much, though, since this also has the rule
/tmp/** mrwlkix,
Can you please check in the logs, if you get some apparmor denials when
OK, it appears that a simple way to trigger this bug is to run
sudo losetup -f /var/lib/snapd/snaps/bare_5.snap
Every time this command is run, the error is reported. If you add the
"-P" option, which should be used to force a partition scan, then you
get an additional warning line:
Sep 20
*** This bug is a duplicate of bug 1917348 ***
https://bugs.launchpad.net/bugs/1917348
I'm closing this bug and setting it as a duplicate of
https://bugs.launchpad.net/snapd/+bug/1917348
There are several issues related to NFS and remote filsystems in
general, and we will be tackling them
Hi Chris, that's expected, because the fix has only been committed to
the repo, it's not in any release yet.
If you feel adventurous, you could use snapd from the edge channel
("snap refresh --channel=latest/edge snapd"), but it's not something I
recommend to keep active, so if you feel like
It looks like the LXD snap has mounted "proc" and "sys" over
/var/snap/lxd/common/var/lib/lxcfs/{proc,sys}/ but it's not unmounting
them.
In the "remove" hook, the LXD snap should unmount any mounted
filesystems; not doing so can have disastrous effects if there are also
user partitions mounted
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1951210
Title:
libreoffice help doesn't open in firefox
Proposed fix: https://github.com/snapcore/snapd/pull/12127
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1951210
Title:
libreoffice help doesn't open in firefox (404 error on
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1951210
Title:
libreoffice help doesn't open in firefox (404
Attaching the logs when running chromium. The /usr/share/libreoffice is
missing from chromium's mount namespace, and the logs show that an error
occurred when creating it:
change.go:446: DEBUG: remove "/tmp/.snap/usr/share" (error: )
change.go:320: DEBUG: mount
WritableProfile(emit, "/usr/share/", 3)
I need to investigate this, but my first guess is that this has the
effect of making firefox and chrome see a different /usr/share/ tree
than the one from the host. I'll be investigating this.
** Changed in: snapd (Ubuntu)
Assignee: (unassign
Добрый день, Павел!
On 02/06/22 13:14, Карелин Павел wrote:
It's too bad the core developers of QBS didn't do this sooner. Now the
fresh compiled version of QBS can only be downloaded as an archive (and
in my country even this cannot be done now).
I happen to live in the same country :-)
*** This bug is a duplicate of bug 1833004 ***
https://bugs.launchpad.net/bugs/1833004
Thanks Islam for reporting this. I'm going to mark this as a duplicate,
as we already have this issue reported as bug 1833004.
** This bug has been marked a duplicate of bug 1833004
Application SNAP is
(Ubuntu)
Assignee: (unassigned) => Alberto Mardegan (mardy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778375
Title:
All snap loops are being output for lsblk, blkid, and fdisk -l.
To man
Hi Fernando, and thanks for reporting this bug!
If, as you wrote in the bug description, you reproduce it when logging
in with your uername and password, then this bug is not related to bug
1593407, which is about the "guest session" (that is the session for
those users who don't have a login
Hi Fernando, and thanks for reporting this bug!
If, as you wrote in the bug description, you reproduce it when logging
in with your uername and password, then this bug is not related to bug
1593407, which is about the "guest session" (that is the session for
those users who don't have a login
Hi all!
In case this is of interest to somebody else than me: I've recently
updated my Ubuntu PPA containing QBS 1.22.1 for Ubuntu Xenial, Bionic,
Focal and Jammy:
https://launchpad.net/~mardy/+archive/ubuntu/qbs-on-lts
Except for Jammy, QBS is linked statically, without using the Qt
For the record, I've opened a discussion in the jupiter-notebook forums:
https://github.com/jupyter/notebook/discussions/6436
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959417
Title:
browsers
For the record, I've opened a discussion in the jupiter-notebook forums:
https://github.com/jupyter/notebook/discussions/6436
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Oh, this is interesting! Then, Etienne, my suggestion is the following:
re-enable the snapd.apparmor service, and if that (as I expect) fixes
the bug, let's stop discussing this issue here, and instead open a
separate issue about the service being disabled.
It may be that something went wrong
Oh, this is interesting! Then, Etienne, my suggestion is the following:
re-enable the snapd.apparmor service, and if that (as I expect) fixes
the bug, let's stop discussing this issue here, and instead open a
separate issue about the service being disabled.
It may be that something went wrong
Oh, thanks Alex, I forgot that we have our own service for loading the
AppArmor profiles of the snaps!
Etienne, could you please show the output of
sudo systemctl status snapd.apparmor
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Oh, thanks Alex, I forgot that we have our own service for loading the
AppArmor profiles of the snaps!
Etienne, could you please show the output of
sudo systemctl status snapd.apparmor
?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
On 24/05/22 23:31, Alberto Mardegan wrote:
Here's the error: https://pastebin.com/68KdfagX
Oh, I see it now, there's a lonely "-D" in the compiler command line:
... -DXDG_THUMBNAILS -D -DQT_SVG_LIB ...
It came from this:
cpp.defines: product.embedAsResource ? "
Hi all,
I upgraded to QBS 1.22.1 and I get a very weird errorwhen building on
Android (Qt 5.15.2); the build for Linux desktop (x86_64) instead works
fine.
Here's the error: https://pastebin.com/68KdfagX
The source code is https://gitlab.com/mardy/mappero/-/commits/qt5.12
I should also
Some updates, while I'm still investigating this on a QEMU running
Ubuntu Core 22.
The "snap auto-import" command is only needed on Ubuntu Core systems, so
the plan is to remove the /lib/udev/rules.d/66-snapd-autoimport.rules
from the snapd deb package (and consequently also from the snapd snap).
Some updates, while I'm still investigating this on a QEMU running
Ubuntu Core 22.
The "snap auto-import" command is only needed on Ubuntu Core systems, so
the plan is to remove the /lib/udev/rules.d/66-snapd-autoimport.rules
from the snapd deb package (and consequently also from the snapd snap).
e analysis by Jiwei Sun is
correct: it's happening because of the added SystemCallFilter entry to
the udev unit file.
** Changed in: snapd
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: snapd
Importance: Undecided => High
--
You received this bug notifica
e analysis by Jiwei Sun is
correct: it's happening because of the added SystemCallFilter entry to
the udev unit file.
** Changed in: snapd
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: snapd
Importance: Undecided => High
--
You received this bug notifica
*** This bug is a duplicate of bug 1966203 ***
https://bugs.launchpad.net/bugs/1966203
Thanks Nick, indeed! I'm closing this since 1966203 was reported first.
** This bug has been marked a duplicate of bug 1966203
Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit
*** This bug is a duplicate of bug 1966203 ***
https://bugs.launchpad.net/bugs/1966203
Thanks Nick, indeed! I'm closing this since 1966203 was reported first.
** This bug has been marked a duplicate of bug 1966203
Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit
Hi Christian,
On 23/05/22 11:12, Christian Kandeler wrote:
Presumably you have set qbs.install to true somewhere in the library
product, with no per-arch differentiation, leading to a conflict. Since
in the Android case the libraries are not the final build artifact, they
should not get
Hi Rafael,
On 23/05/22 13:38, Raphael Cotty wrote:
Hello,
the libMapperoCore.so should have the architecture name like this:
libMapperoCore-arch.so
What type of product do you use for the MapperoCore?
It's a DynamicLibrary. Is there something special which I should do to
give the compiled
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Alberto Mardegan (mardy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971955
Title:
systemd-udevd call unshare process w
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Alberto Mardegan (mardy)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1971955
Title:
systemd-udevd call unshare proc
Hi again Vincent :-)
Please ignore the part about adding more attributes to the SystemCallFilter
list; I don't think it's a road we want to follow.
What would be more important for me to know, is whether things work if
you change the RUN line to just
RUN+="/usr/bin/snap auto-import
Hi again Vincent :-)
Please ignore the part about adding more attributes to the SystemCallFilter
list; I don't think it's a road we want to follow.
What would be more important for me to know, is whether things work if
you change the RUN line to just
RUN+="/usr/bin/snap auto-import
Thanks Vincent. I think I got some hints: I downloaded the package from
Jammy, I unpacked it and then ran a diff on the systemd unit file for
the udev service (since in the documentation of udev[1] it's written
that programs are executed in a sandbox) from the version in Focal:
==
---
Thanks Vincent. I think I got some hints: I downloaded the package from
Jammy, I unpacked it and then ran a diff on the systemd unit file for
the udev service (since in the documentation of udev[1] it's written
that programs are executed in a sandbox) from the version in Focal:
==
---
Hi Paul and Laurent, thanks for your bug report. Can you please check
what happens when you manually run tha same commands that you see as
failed?
For example, from Laurent's log:
sudo /usr/lib/snapd/snap-device-helper add snap_brave_brave
/class/video4linux 0:0 && echo ok
Also, if you
Thanks Etienne, this is a bit surprising! Do I understand correctly,
that on the slower machine (where you are seeing this bug) you will not
be able to start firefox until you have run that apparmor_parser
command? Not even if you try starting firefox well after the login?
It's strange, because
Thanks Etienne, this is a bit surprising! Do I understand correctly,
that on the slower machine (where you are seeing this bug) you will not
be able to start firefox until you have run that apparmor_parser
command? Not even if you try starting firefox well after the login?
It's strange, because
Hi again :-)
Sorry for the spamming, this hopefully is an easy question: how do I
find out, from within a QBS build directory, what where the command-line
options which I passed to QBS to initialize the project?
Like, if I ran:
qbs run profile:android515 project.geotagger:false -f ..
I
Hi there!
So far I've built my Android application using Qt 5.12, for the arm
architecture only, and everything has worked fine.
Today I tried migrating to 5.15, which supports multiarch, and I'm
getting an issue: after building all the files for all the four
supported architectures ("Qt
Mmm... I'm running out of ideas! Mayve it's something with the
environment?
Vincent, can you try changing the rule to
RUN+="/bin/bash -c 'set > /tmp/set.log'"
and attach set.log here?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Mmm... I'm running out of ideas! Mayve it's something with the
environment?
Vincent, can you try changing the rule to
RUN+="/bin/bash -c 'set > /tmp/set.log'"
and attach set.log here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Jeffrey and Erik!
You are being heard :-) But this is not an easy task, and the amount of work
required to support the case of home directories nested somewhere deeper inside
/home is very different (read: lower) than that required to support home
directories located elsewhere in the
Hi Jeffrey and Erik!
You are being heard :-) But this is not an easy task, and the amount of work
required to support the case of home directories nested somewhere deeper inside
/home is very different (read: lower) than that required to support home
directories located elsewhere in the
** Changed in: snapd
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: snapd
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776800
Hi Erik, I see now what's the problem (this is specific to your setup --
this probably does not concern other people who commented here): your
home directories are under /staff, whereas currently snaps only support
the traditional /home// scheme.
Please subscribe to
** Changed in: snapd
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: snapd
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Hi Erik, I see now what's the problem (this is specific to your setup --
this probably does not concern other people who commented here): your
home directories are under /staff, whereas currently snaps only support
the traditional /home// scheme.
Please subscribe to
Vincent, maybe the udev rules are running under a user lacking some
privileges?
Can you please try changing the rule to
RUN+="/bin/bash -c 'id > /tmp/id.log'"
and then paste here the output of id.log? (hopefully I didn't mess up
the quoting in the command :-) )
--
You received this bug
Vincent, maybe the udev rules are running under a user lacking some
privileges?
Can you please try changing the rule to
RUN+="/bin/bash -c 'id > /tmp/id.log'"
and then paste here the output of id.log? (hopefully I didn't mess up
the quoting in the command :-) )
--
You received this bug
Thanks Erik and Andrew for the logs!
It looks like we have more than one bug here:
1) Andrew's logs show that after restarting the snapd service, NFS was
correctly detected and there are no more AppArmor denials on that. But
on Erik's machine, for some reason, that did not happen.
2) Even if
Thanks Erik and Andrew for the logs!
It looks like we have more than one bug here:
1) Andrew's logs show that after restarting the snapd service, NFS was
correctly detected and there are no more AppArmor denials on that. But
on Erik's machine, for some reason, that did not happen.
2) Even if
Hi Etienne, can you be a bit more explicit about what is the issue that
you are seeing? What are the services which are not starting?
Also please attach the SVG file generated by "sudo systemd-analyze
plot", it might help us.
--
You received this bug notification because you are a member of
Hi Etienne, can you be a bit more explicit about what is the issue that
you are seeing? What are the services which are not starting?
Also please attach the SVG file generated by "sudo systemd-analyze
plot", it might help us.
--
You received this bug notification because you are a member of
I believe that this is a duplicate of bug 1884299.
A few questions to people affected by this bug:
1) are you using autofs?
2) can you please try running "sudo systemctl restart snapd" after
logging in into your $HOME, and then try running a snap again?
3) If that still fails, can you paste
I believe that this is a duplicate of bug 1884299.
A few questions to people affected by this bug:
1) are you using autofs?
2) can you please try running "sudo systemctl restart snapd" after
logging in into your $HOME, and then try running a snap again?
3) If that still fails, can you paste
Hi Vincent, if I understand it correctly, this command scans the
inserted media for snapd assertions and imports them.
It's still not clear to me what's happening: even if you are running on
a classic system, the "auto-import is disabled on classic" is just a
notification and not an error: the
Hi Vincent, if I understand it correctly, this command scans the
inserted media for snapd assertions and imports them.
It's still not clear to me what's happening: even if you are running on
a classic system, the "auto-import is disabled on classic" is just a
notification and not an error: the
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959375
Title:
[SRU] Please support group manipulation with "extrausers"
To
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1959375
Title:
[SRU] Please support group manipulation
Hi Brian,
I finally tested the new packages on Ubuntu Core 18 (with the bionic
packages) and Ubuntu Core 20 (with the focal ones). I first tried to reproduce
the issue in Ubuntu Desktop, by making /etc/groups and /etc/passwd read-only
and indeed I couldn't add my user to a group, but
Hi Brian,
I finally tested the new packages on Ubuntu Core 18 (with the bionic
packages) and Ubuntu Core 20 (with the focal ones). I first tried to reproduce
the issue in Ubuntu Desktop, by making /etc/groups and /etc/passwd read-only
and indeed I couldn't add my user to a group, but
We did some progress in investigating this, and it appears that a
problem still exists: if the system is using autofs and snapd is started
before any NFS home directory is mounted, snapd will fail to detect the
fact that the system is using autofs (or NFS), and will not grant snap-
confine those
A similar issue was discussed in the forums:
https://forum.snapcraft.io/t/cannot-open-path-of-the-current-working-
directory-permission-denied-bis/28704
If the system is using autofs and snapd is started before any NFS home
directory is mounted, snapd will fail to detect the fact that the system
Hi Vincent, thanks for reporting this. There should be some message
printed by the "snap auto-import" command when it fails.
Can you please try to manually run (as root) the command
/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239
and paste here the output?
** Changed
Hi Vincent, thanks for reporting this. There should be some message
printed by the "snap auto-import" command when it fails.
Can you please try to manually run (as root) the command
/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239
and paste here the output?
** Changed
Access to the "$HOME/.local/share/fonts/" is provided by the "desktop"
interface. The libreoffice snap should add this interface to its plugs,
and then fonts from this location should become usable.
I'm marking this bug as invalid for snapd (since it does not appear that
we need to do anything
Access to the "$HOME/.local/share/fonts/" is provided by the "desktop"
interface. The libreoffice snap should add this interface to its plugs,
and then fonts from this location should become usable.
I'm marking this bug as invalid for snapd (since it does not appear that
we need to do anything
Hi Fabian,
On 02/05/22 09:52, Fabian Kosmale wrote:
I think your issue might be QTBUG-91390 (ListModel does not keep
objects with JS ownership alive in 5.15). That was fixed in Qt 6.2
(https://codereview.qt-project.org/c/qt/qtdeclarative/+/354140), but
due to the behaviour change never
Hi Furkan,
On 01/05/22 20:01, Furkan Üzümcü wrote:
I think adding an object to a `ListModel` does not alter its
ownership. If the page with the initial property which holds a
reference to the object returned from the C++ method is destroyed,
then I would expect that object to be destroyed as
Hi there!
I think I'm experiencing an issue related to
https://bugreports.qt.io/browse/QTBUG-50319
In my case, I have a C++ method returning a new QObject, which has
automatic Javascript ownership. This is fine, because indeed I want to
have my object managed by the QML engine.
Then I'm
Hi Dave, I did not see any I/O errors from the kernel, but in your first
boot log
(https://errors.ubuntu.com/oops/fa9433d0-c022-11ec-8ae0-fa163e993415)
there are plenty of errors which might be related to missing files:
===
Apr 19 21:46:38 localhost.localdomain pulseaudio[841]: Failed to load
Hello again, Dave! Looking at the logs, it doesn't seem that your
problem is related to bug 1969162.
What I'm left to suspect is a storage issue, since there are many errors about
files failing to load in the logs. I've had similar issues with a RPi3, where I
had to flash the same Ubuntu image
Thanks Brian! :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969529
Title:
snapd failing to seed firefox on Pi 400
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1969162 ***
https://bugs.launchpad.net/bugs/1969162
Thanks Julian! I believe that this is the same bug as 1969162, but feel
free to comment back if you believe that's not the case.
** This bug has been marked a duplicate of bug 1969162
bad interaction
Hi Dave, and thanks for reporting this. As you wrote about the "10
minutes", a bell rang in my head. :-)
Could it be the same issue as
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162? The
problem is that I don't think this should happen on a fresh install --
but on the other hand, I
Here's the PR: https://github.com/snapcore/snapd/pull/11680
And please forget what I wrote about our prerm script: that script is
not stopping snapd, but only all the systemd service installed *by snap
packages*, so it should be fine.
--
You received this bug notification because you are a
added: github.com/systemd/systemd/issues #8102
https://github.com/systemd/systemd/issues/8102
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Changed in: snapd (Ubuntu)
Statu
Hi Pablo, and thanks for reporting this issue.
snapd requires the systemd user session to be running, but according to
the information you provided ("systemctl --user") that's not the case in
your xRDP session. I did a quick research, and it seems that there's
quite a few of similar problems
On 06/03/22 16:23, Konstantin Ritt wrote:
For those who have experienced inconvenience due to these blockings, I
propose to gather at some public site and create binaries repo driven by
community, not by political influences.
Sorry for jumping in so late. Please count me in.
My problem is
On 06/03/22 17:07, coroberti wrote:
There are KDE repos, aren't there?
For example:
https://invent.kde.org/qt/qt/qtbase/-/commits/kde/5.15
The source code, as far as I can tell, it's not the problem. The problem
is with the binary releases, and I cannot find them in the KDE site.
Ciao,
Just yesterday we landed a fix in snapd to address some issues with
cups: https://github.com/snapcore/snapd/pull/11616
Unfortunately I do not know the details of the issue that this change
solves, but maybe someone with more knowledge of cups can tell if that
change could fix this bug too.
--
Hi Richard, I can confirm the issue: I do have the
/usr/share/libdrm/amdgpu.ids file in my host, but it's probably not
visible to the snap (and no AppArmor denial appears in the logs).
But whether this means that GPU acceleration is disabled, this is
something that would be better answered by the
The code managing this situation actually has the information about the
PIDs of the running processes.
Samuele, do you think we should print them as part of the error message?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
* In order to use the microk8s snap in Ubuntu Core, one currently needs
to be root. This is far from optimal, since normally (on desktop and
server installations) this is not necessary.
* This make it hard to provide consistent documentation on
1 - 100 of 4008 matches
Mail list logo
