I got hit by this too, now that I've upgraded to 24.04. I can see that
my logins are in "~/snap/chromium/common/chromium/Default/Login Data",
but the password manager in Chromium is empty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
*** 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 s
** 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/1778375
Title:
All snap loops are being output for lsblk, blkid, a
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 in
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 an
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 duri
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 U
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).
nalysis 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 notificat
*** 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
co
** 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
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 --mount
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:
==
--- /lib
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 don't
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 yo
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 Ubun
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 system
** 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 https://bugs.launchpad.net/snap
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 not
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 the
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 Ubun
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 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 pro
** 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 manag
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 unfortuna
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 pe
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 in
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 the
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 o
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:
https://bugs.launchpad.net/ubunt
*** 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 bet
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 d
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 membe
.
** Bug watch 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 (Ubunt
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 repor
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.
--
Yo
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.
https://bu
** 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 micr
** 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 micr
Marking as Invalid for Impish, since the issue only happens with a read-
only rootfs like we use in Ubuntu Core, and UC is only based on LTS
releases.
** Changed in: shadow (Ubuntu Impish)
Status: New => Won't Fix
** Changed in: shadow (Ubuntu Impish)
Importance: Undecided => Low
--
Y
** Patch added: "debdiff for Bionic"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568639/+files/0001-Bionic-patch-for-LP-1959375.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Patch added: "debdiff for Jammy"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568614/+files/0001-Jammy-changes-for-LP-1797786.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Patch removed: "debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568607/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch
** Patch added: "debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+a
** Patch removed: "Patch for focal"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568568/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch
** Patch added: "debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+att
I tested a newer version of the patch that Michael sent me, and I verify
that it works properly :-)
I'm attaching it here; it includes changes to the
1015_add_zsys_support.patch, but that's only as a result of a quilt
refresh, since the patch did not apply cleanly anymore (since
src/usermod.c was
Thanks Roman, we are working on it in
https://github.com/snapcore/snapd/pull/10676
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Alberto Mardeg
Hi Gene, thanks for reporting this!
I have no idea what the problem might be, but please try this:
1) Since you are already root, try not using sudo (though I'm almost sure that
this is not causing any issues)
2) Please post the output of these commands (after re-trying to enable
livepatch):
Hi Xavier, thanks for reporting this issue, and sorry for the
regression!
Do you think that this is the same bug as
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960972? Comment #2
in that bug has a workaround; can you please try and see if that helps
you too?
--
You received this bug no
Unfortunately this is by design: the snapd "home" interface allows
access to all files in a user's home, except from the "snap" dir and all
toplevel hidden directories. So,
~/.i/love/dot/folders
is not allowed, but
~/i/.love/dot/folders
is. The point is that toplevel hidden directories
Hi Christian, we already merged support of fuse3 in master; Now we have
a dependency on `libfuse-dev | libfuse3-dev`, and it should just be a
matter of rebuilding the code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Here are the changes we'd need to backport to Focal in order to fix this
bug there:
To package xdg-desktop-portal-gtk:
-
https://github.com/flatpak/xdg-desktop-portal-gtk/commit/920afdde7afc023e77ecfeb4e174cb42f22cbfe3
To package xdg-desktop-portal:
-
https://github.com/flatpak/xdg-desktop-port
Hi Olivier, let me take some time to investigate what are the changes to
the next major version, because if we are lucky and they are small and
safe, we could really think about a SRU. At least for 20.04, which is
going to be supported for quite a few years from now.
Also, let's keep in mind that
Hi Olivier! I tried on hirsute, and it's working :-)
Then I guess that the only series still supported by Canonical and
affected by this bug are the LTSes.
** Also affects: chromium-browser (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: chromium-browser (Ubuntu Bion
After some good hints from Oliver I did some investigation on this
issue. Indeed it looks like the chromium snap is doing the right thing:
it first checks if the D-Bus service "org.freedesktop.portal.Desktop" is
running (if not, it falls back on calling ListActivatableNames, which is
not ideal beca
Hi Tobias, thank you for getting in touch! I just tried installing the
manuskript snap, and verified that indeed it does not start. After a few
seconds it prints this line:
Qt: Session management error: Could not open network socket
I'm not sure where this error comes from; I suspected that i
Hi Olivier (or whoever knows about Chromium), I see that the upstream
support for the XDG file selector portal landed somewhere in July this
year (https://chromium-
review.googlesource.com/c/chromium/src/+/2992214/), but I cannot find
information on which Chromium version contains this change.
I'm
** Patch added: "Support-system-image-read-only-etc.patch"
https://bugs.launchpad.net/snappy/+bug/1650688/+attachment/5543088/+files/Support-system-image-read-only-etc.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I can confirm that Ratchanan's patches work (well, I only tried the one
on timedated, as the one on timedatectl is not essential to fix this
bug).
But I don't think that it should be treated separately from the existing
patch we have, so I'm attaching a refreshed patch which includes
Ratchanan's c
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
This has been addressed in https://github.com/snapcore/snapd/pull/11055
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950634
T
Thanks Lukas! It's very likely that there are several issues in this
area, because while I can confirm that your latest image fixes the
reproducer I pasted before (in the Google cloud, too), the spread test
failure is still reproducible with the "tests/main/services-disabled-
kept-happy" test.
I n
--purge):
installed snapd package post-removal script subprocess returned error exit
status 1
```
Since the error is logged anyway, I think we should not fail here and
instead proceed no matter what.
** Changed in: snapd (Ubuntu)
Importance: Undecided => Low
** Changed in: snapd (Ubuntu)
Assi
** Changed in: snapd (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950634
Title:
package snapd (not installed) failed to install/upgrade: installed
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*"
Thanks for the information, David. But is apt happy now, or is it still
complaining about the snapd package state? What happens if you run "apt
-f install"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
One more update: I verified that the steps from comment #17 can be used
to reproduce the issue in an Ubuntu Core image started in qemu, and
without using the spread. I verified it with the 20211105 image provided
by Lukas in https://people.ubuntu.com/~slyon/uc18/
To reproduce it, start the image i
Hi David! I'm sorry to read that you had this bad experience. What is
the current situation?
I see from the logs that the error occurred because the snapd post-
removal script found that the /var/snap directory was in use. Can you
please check what are its contents now (you could run `tree /var/sn
Might be related to https://github.com/systemd/systemd/issues/11342
** Bug watch added: github.com/systemd/systemd/issues #11342
https://github.com/systemd/systemd/issues/11342
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
An update to the comment above. We have found out a sequence of commands
that seems to reproduce the issue reliably: in the spread session
started by the command from the comment above, if you type this:
systemctl stop 'snap-disabled\x2dsvcs\x2dkept-x1.mount'
systemctl daemon-reload
#
> can you provide steps on how this is reproducable then?
So far we have not been able to isolate the problem, so the only way so
far is to run the spread tests from the snapd directory (from the master
branch):
spread -debug -repeat 20 google:ubuntu-
core-18-64:tests/main/services-disabled-k
I'm coming with bad news. Today both me and Michael have individually
retested both snaps you provided (20211102 and 20211105), and the bug
happened with both of them. It's possible that yesterday Michael
accidentally used QEMU for his tests, without realizing (and in QEMU it
seems that this bug is
Interestingly, I cannot open the image. Abdenour, can you please try
uploading again after renaming the file to a different name? I wonder if
it's because of the accented letters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Public bug reported:
Since a month or so, we've been seeing random failures in our snapd
spread tests where systemd could not start the mount unit associated
with a snap because of a failed dependency.
The issue is described in the comments to PR
https://github.com/snapcore/snapd/pull/10935, but
I believe that this is the same issue as #1946656, which will be fixed
in snapd 2.53:
https://github.com/snapcore/snapd/commit/da1caa8b12c0f839320f29012b4565d1f702eb42
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: snapd (Ubu
I closed this too soon. The crash still happens, but I cannot reproduce
it reliably: there are moments when any search leads to a crash, but
after some time it stops crashing and continues working for hours.
From the console, the crash appears like this:
==
$ chromium-browser
[456694:456
Wow, I wanted to provide an example URL, but now it doesn't crash
anymore. Before, I had it reliably crashing several times on any Yandex
search result page.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Closing, will reopen if I happen to reproduce it again. :-)
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942431
Title:
Lates
Public bug reported:
After upgrading to `93.0.4577.63`, Chromium crashes after opening Yandex
search pages: the page is briefly shown, and then immediately afterwards
Chromium crashes.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: Invalid
--
You received this
snapd could be changed not to be run all the time: the `snap` command
could start snapd if it's not running, and this would address the first
and third points mentioned by Ian (because when a snap program is run,
what is first executed is actually /usr/bin/snap), and it should be
possible to handle
Public bug reported:
I just updated to Ubuntu 20.04, and when I started Chromium nothing
happened. Since I am a dumb user, I clicked the Chromium icon three
times, thinking that maybe the first clicks hadn't been registered.
Chromium finally started after a while, but at that point I noticed that
Public bug reported:
Similarly to python3-setuptools, which was handled in
https://bugs.launchpad.net/ubuntu/+source/doxyqml/+bug/1585517, all the
Python packages should be marked as "Multi-Arch: foreign" to allow
proper cross installation.
** Affects: python-flake8 (Ubuntu)
Importance: Unde
This is now fixed in Ubports :-)
https://github.com/ubports/system-settings/pull/81
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502820
Title:
Battery graph not showing full history
To manage not
Public bug reported:
Canonical modified the AppArmor policy in order to make authercast work:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+files/isc-dhcp_4.3.1-5ubuntu2_4.3.1-5ubuntu2.4~overlay1.diff.gz
(only the first chunk of the patch is relevant to this is
Public bug reported:
The projects has a pkg-config file, but it's not present in the Ubuntu
package.
** Affects: log4cplus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Hi Brandon (and everyone else experiencing the signin-ui crash), in
order to fix this bug I need to get the exact backtrace of the signon-ui
program.
Could you please run
apport-bug /var/crash/...[pick the signon-ui crash file]
from a terminal, so that launchpad can analyze the crash?
--
Y
As far as I can see, there is no plan to remove these packages (please confirm,
Jeremy). And indeed I'm going to maintain these packages in the future as well:
libsignon-{qt,glib}, signond, libaccounts-{qt,glib}
I'm also willing to maintain other packages mentioned in this bug, such
as online-a
** Changed in: content-hub (Ubuntu)
Status: New => In Progress
** Changed in: content-hub (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676893
Title:
** Changed in: content-hub (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/1676893
Title:
Inform client if ContentHub service is
whether the service is available.
** Affects: content-hub (Ubuntu)
Importance: Undecided
Assignee: Alberto Mardegan (mardy)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
*** This bug is a duplicate of bug 1451728 ***
https://bugs.launchpad.net/bugs/1451728
** This bug has been marked a duplicate of bug 1451728
[master] kde-config-telepathy-accounts package install error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Fix available here, waiting for QA:
https://bileto.ubuntu.com/#/ticket/2608
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673984
Title:
Can not add google account any more (Zesty)
To manage notifi
The "Add account" button should simply show you a list of account
providers on the right side of the system settings panel. Then you need
to click on one of them, in order to start the account creation.
If that does not work, please provide a screenshot.
** Changed in: account-plugins (Ubuntu)
Eugene (and others), if you are still affected by this bug, please
follow bug 1666285 instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029289
Title:
Need to authorize my google account each t
** Branch linked: lp:~mardy/signon-ui/unity-crash-1673984
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673984
Title:
Can not add google account any more (Zesty)
To manage notifications about this
signon-ui (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/1673984
Title:
Can not add google account any more (Zesty)
To manage notifi
Public bug reported:
Please install the meshlab-mardy snap. This Qt application works fine in
unity7, and actually mostly works in unity8 too. However, as soon as it
starts, for some reason it creates a secondary black window for a few
seconds (title being something like "MeshLab_64bit"), which th
1 - 100 of 1559 matches
Mail list logo
