** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Are you still able to reproduce it with the stock bionic kernel? If yes,
it's still a bug
** Changed in: mesa (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--- Comment From heinz-werner_se...@de.ibm.com 2019-02-13 02:37 EDT---
IBM bugzilla status-> closed, Fix Released for Xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799208
Title:
That said, if someone filed a bug against lirc because lirc-setup is
broken, that bug is certainly valid. But IMHO, that's a very different
story. And since there is a usable work-around it would probably just be
closed as fixed upstream.
--
You received this bug notification because you are a
The main issue described in this bug is bogus, as apparent from bug
#1788235
However, the configuration script lirc-setup *is* indeed broken . This
is fixed in Debian upstream from 0.10.1, but hasn't trickled down. That
said, users will still need to read README.Debian, and the process to
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Hi Tony, thank you for taking the time to submit this bug.
The log indicates several broken packages still on your system that appear to
be interfering with the upgrade. Try running 'sudo apt-get remove libblas3
libpython2.7-stdlib libopenblas-base python-scipy' and then attempting the
upgrade
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1814648
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383
Thanks for the details, but if I see correctly this was handled in the dock
extension, meaning the lock does not forcibly locks all apps, but dock now
"respects" the lock request.
This means this or
Thanks a lot Oliver already - I've heard that testing those could take a
few days due to the breaks all around Asia. But I guess next week most
people will be back and once this is pre-checked from the PPA we can
upload to the SRU to have the final verification then.
--
You received this bug
Huh, I see people have started a bunch more whacking on yaml-cpp since
the start of this MIR. Great!
The Mir team certainly have the skills required to submit PRs for these,
and failing anything else we can distro-patch them in. If fixing these
bugs is the price of security-team signoff, I think
I'm not sure what the exact problem is that's reported here.
Is it the string "#:#:#:#" itself that replaces the disk ID in case of an error
with the disk/path.
And if so - which problem is it causing then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The problem has mysteriously resolved itself.
I updated once again yesterday via Software Updater (for good measure).
I haven't changed any settings; kernel is still 4.4. Based on some
Googling it seems the problem might have been related to some part of my
system which is hallucinating mid-sleep
This has been fixed for disco with the upload of pam 1.3.1-2ubuntu1.
** Changed in: pam (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666203
Title:
Which files, when missing, cause this to happen? Can you provide strace
output of the failing process?
This seems unlikely to be due to PAM, which has fairly well exercised
error handling and is designed to fail closed; but it's possible there
is a bug in the configuration of PAM for one or more
This bug was fixed in the package gst-plugins-good1.0 - 1.15.1-1ubuntu2
---
gst-plugins-good1.0 (1.15.1-1ubuntu2) disco; urgency=medium
* Cherry-pick Revert-pulsesrc-Move-to-extended-stream-API.patch:
- Back out a feature that depends on an unreleased PulseAudio
feature
Are you able to find the last known good kernel in grub and boot into it
to see if the problem exist? Please also reproduce the problem and
attach your /var/log/kern.log to this bug in your next reboot. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
> As discussed in bug #1814403, this is by design.
Disagree. Mathieu mentioned in Comment #31 of bug #1814403:
> When your system doesn't boot correctly through the kernel however, it
would likely not show the menu without this fix -- you'd have no way to
switch back to a working kernel,
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799208
Title:
dbginfo.sh does not complete on Ubuntu 16.04(.5)
To manage
Public bug reported:
Hi,
Recently, I installed Ubuntu 18.04 on my Dell G7 7588. From day one, the
system has random freezes/crashes (usually a few a day)
The way the crashes manifest is that 2 out of my 3 monitors go black and
in some cases sound and inputs get stuck. In some rare cases, I can
If you are booting via UEFI and your /boot is on btrfs then grub has
detected that /boot/grub/env is not writable from within grub and
therefore the boot menu is shown with a delay. As discussed in bug
#1814403, this is by design.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
> If you still feel your system is showing the menu and timeout at every
boot unnecessarily, or if you feel the default timeout is too long,
please file a separate bug with the information specific to your system
and particular case so we can look into it
In this case please look into
Additional information: all affected devices boot via grub-efi.
** This bug is no longer a duplicate of bug 1814403
Latest update causes 30 sec. menu delay timeout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am unsubscribing ubuntu-sponsors. Please feel free to resubscribe when
you have something ready for sponsoring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814562
Title:
Update to new upstream
The attachment "bionic2.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for dbconfig-common (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: dbconfig-common (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for dbconfig-common (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: dbconfig-common (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
xnox, raof, many thanks for your replies earlier.
I've read through yaml-cpp and can see the benefits: it sticks to C++
things and is remarkably readable. There's a lot of tests.
But there's six CVEs that have been completely ignored. While at least
some of the CVEs wouldn't affect Mir's use (no
Public bug reported:
Recently before 6.2 upstream release, translations of Indonesian help
has reached around 90%. Please build libreoffice-help-id package so that
translation can be easily used by users.
** Affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
--
You
@azzar1 correct the upstream change made the snaps reviewable, however
the ubuntu-reviews plugin suppresses the ODRS plugin so reviews fail to
be posted. We should have patched the NOT_REVIEWABLE quick back in.
I agree it's easier to move forwards and SRU the ODRS change back to
Cosmic (bug
Public bug reported:
[Impact]
The Ubuntu review server is being retired which will cause all Ubuntu package
reviews to stop working. We are switching to using the Open Desktop Review
Service (https://odrs.gnome.org/). This plugin has existed for sometime in the
GNOME Software source, so it is
You absolutely can change /etc/grub.d/00_header to change or remove the
code. The problem is; I don't think there is a way around us providing a
way to reach the menu for the those setups where "recordfail", the
feature that lets the boot menu start on failure, doesn't work, while
also making it
Some more questions:
- Is "Boot Order Lock" enabled on the affected system? (This is another
feature in BIOS/firmware).
- Please include the output of 'sudo efibootmgr -v'
** Changed in: grub2-signed (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
I'm unable to reproduce this. I've tried upgrading from bionic to
cosmic, or various partitioning set ups. Clearly there is something
special about some set up that can cause this kind of issue, but I'm
unsure what it could be.
Could you please tell us more about how your system was installed
** Project changed: lxfind => pcmanfm-qt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814326
Title:
home, root, and temp folders display errors
To manage notifications about this bug go
This is the *nastiest* bug I've ever encountered in the wild on my own
in Linux (that has no good solution after this long). Package
1.2.2-0ubuntu0.16.04.4 has disappeared from the mirrors for Xenial (not
that anyone should expect a normal user to go through the deep dive that
is this subject,
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
This is the *nastiest* bug I've ever encountered in the wild on my own
in Linux (that has no good solution after this long). Package
1.2.2-0ubuntu0.16.04.4 has disappeared from the mirrors for Xenial (not
You have been subscribed to a public bug:
Folks: Not sure why this is "LxFIND" . . . for problem in Lubuntu Next
18.10 && Lu 19.04 . . . after latest update/upgrade, the desktop icons
for Home, Root, and Temp folders have exclamation points over them . . .
previously in both 18.10 & now 19.04 .
This bug was fixed in the package qtbase-opensource-src - 5.11.3+dfsg-
5ubuntu1
---
qtbase-opensource-src (5.11.3+dfsg-5ubuntu1) disco; urgency=medium
* Sync with experimental branch of Debian packaging Git.
-- Dmitry Shachnev Mon, 11 Feb 2019 13:43:15
+0300
** Changed in:
** Summary changed:
- ftbfs on ppc64el -- please remove package from disco
+ ftbfs on ppc64el and arm64 -- please remove package from disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815396
Ok, found it:
PrivateTmp=true
ProtectHome=true
ProtectSystem=full
these systemd service parameters prevent it from starting properly...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815699
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: docker.io (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815683
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: docker.io (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815683
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: docker.io (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815683
I have changed it to public. I don't find why I change it to private.
Sorry.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806845
Title:
The
** Changed in: libcwd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508282
Title:
libcwd: FTBFS with GCC 5
To manage notifications about this bug
hpp23,
the fix is waiting for SRU review for some weeks now
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text=gnome-shell
So we actually care of fixes, like we care about no regress in other
things and so being a little conservative before releasing a new
version.
--
You received
It looks like it only happens inside linux containers (lxc) :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815699
Title:
installed ejabberd package post-installation script subprocess
This bug was fixed in the package landscape-client - 18.01-0ubuntu7
---
landscape-client (18.01-0ubuntu7) disco; urgency=medium
* debian/patches/mem-usage-1685885.patch: Reduce memory usage by
unused twisted logs. (LP: #1685885)
-- Simon Poirier Fri, 08 Feb 2019
12:02:17
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ejabberd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680182
Title:
I looked into this a bit and the feature worked differently than I
thought.
If you pick one of the 4 choices, it creates a __custom theme in
~/.local/share/sounds/ (derived from Yaru if Yaru is your selected sound
theme) with just the alert sounds overriden.
GNOME is looking for help in perhaps
Public bug reported:
On an empty just installed ubuntu 18.04 `apt install ejabberd` fails.
Relevant apt log:
Setting up erlang-p1-cache-tab (1.0.12-2) ...
Setting up erlang-p1-xml (1.1.28-1) ...
Setting up erlang-p1-eimp (1.0.2-2) ...
Setting up erlang-p1-xmpp (1.1.19-1) ...
Setting up ejabberd
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815698
Title:
package grub-efi-amd64-signed 1.93.13+2.02-2ubuntu8.12 failed to
install/upgrade: installed
Hello Dan,
Ubuntu is a great system! I use it almost exclusively for my development.
Always looking for a way to give back. I know just opening a bug is not the
most help so whatever way I can assist I am more than happy to do.
Yes it was the latest from VirtualBox upstream. I am running on a
@Diftraku you will need to be specific about what behavior you are
seeing and why you think this is a bug, since the behavior of
2.02-2ubuntu8.12 is known to not be the same as in 2.02-2ubuntu8.10.
If you have /boot on LVM and are booting in UEFI mode, then you will see
a boot delay.
--
You
Oh! Simon has already prepared an update, it just needs someone to test
it and report that it works:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages
Can anyone here test and report back if this update addresses the issue
and doesn't introduce new problems?
Thanks
Public bug reported:
package error before installing
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64-signed 1.93.13+2.02-2ubuntu8.12
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules:
Not sure what happened, but I tried installing the HWE kernel, even
those it's not entirely ready, but it did install the new video drivers
and that solved it.
** Changed in: mesa (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
** Patch added: "xenial2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mosquitto/+bug/1815695/+attachment/5238143/+files/xenial2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815695
** Also affects: inkscape
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815694
Title:
GLib-CRITICAL and does not start
To manage notifications about
Public bug reported:
One of the recent security patches for the 1.4.x series of Mosquitto
contained a mistake that can cause an attempted read from incorrect
memory, if a user has persistent data being saved to disk.
The attached patches fix the problem.
** Affects: mosquitto (Ubuntu)
Eduardo, I hope you don't mind me subscribing you to this, but it seems
like you would be the person best placed.
** Description changed:
One of the recent security patches for the 1.4.x series of Mosquitto
- contained a mistake that can cause and attempted read from incorrect
+ contained a
** Patch added: "cosmic2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mosquitto/+bug/1815695/+attachment/5238142/+files/cosmic2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815695
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814931
Title:
Mosquitto CVE-2018-12551, CVE-2018-12550, CVE-2018-12546
To manage
** Description changed:
1) I try:
/snap/bin/inkscape
2) but terminal showed me:
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon:
assertion failed (error == NULL): Icon 'image-missing' not present in theme
Mint-Y (gtk-icon-theme-error-quark, 0)
Public bug reported:
1) I try:
/snap/bin/inkscape
2) but terminal showed me:
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon:
assertion failed (error == NULL): Icon 'image-missing' not present in theme
Mint-Y (gtk-icon-theme-error-quark, 0)
Emergency save activated!
Same as what Chris mentioned. I occasionally use a Hauppauge 950Q USB
device that has IR support on my laptop, but I don't keep it plugged in
24/7 since I frequently travel with this laptop. I don't want to mess
around with scripts and disable services, so right now my "workaround"
is to only
** Tags added: ubiquity-18.04.14.6
** Tags added: ubiquity-18.04.14.11
** Tags added: ubiquity-18.10.12
** Tags added: ubiquity-19.04.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815691
Title:
** Tags added: xenial2bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815687
Title:
Updating from 16.04 to 18.04
To manage notifications about this bug go to:
subscribed ~field-medium
** Tags added: canonical-bootstack
** Tags added: field-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792880
Title:
totalGigabytesUsed in openstack limits show
Public bug reported:
Suddenly sometimes during the past two weeks my kubuntu installation has
started to freeze up. I can't remember what apt upgrade that caused it,
and I have done several the last few days hoping for it to be resolved.
I didn't know what was causing it as I hadn't made any
filemanager-actions will be available in Ubuntu 19.04 which will be
released in April.
** Package changed: nautilus (Debian) => filemanager-actions (Debian)
** Package changed: nautilus-actions (Ubuntu) => filemanager-actions
(Ubuntu)
** Changed in: filemanager-actions (Ubuntu)
Status:
** Tags removed: third-party-packages
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814949
Title:
gnome-control-center refuses to open if you try to open the Details
Thanks Christian, very thorough.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815415
Title:
please update libseccomp for newer kernel syscalls
To manage notifications about this bug go to:
** Attachment added: "ubiquity-18.04.2-syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1815691/+attachment/5238122/+files/ubiquity-18.04.2-syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "ubiquity-18.10-syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1815691/+attachment/5238123/+files/ubiquity-18.10-syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "ubiquity-19.04-syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1815691/+attachment/5238124/+files/ubiquity-19.04-syslog.txt
** Tags added: bionic cosmic disco rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "ubiquity-18.04.1-syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1815691/+attachment/5238121/+files/ubiquity-18.04.1-syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I attempted to install Ubuntu from multiple ISOs, made with dd to a USB
disk, onto an Intel NUC7i5BNHXF and none of them were able to detect the
disk on the system. I was able to successfully install Ubuntu 16.04!
using the image identified linked to from here:
Two immediately above comments reference EFI boot. This bug report and
fix were regarding an original bug that appeared in non-EFI boot
environment.
It's possible your encountering a different bug or have an unclean EFI
--
You received this bug notification because you are a member of Ubuntu
** Changed in: nautilus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640541
Title:
nautilus shows Windows Network but fails to open it
To manage
Ok, let's close the bug then. It could have been a side effect of adding
a printer in settings which has a weird workflow/is a known issue
** Changed in: gnome-software (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Is there anything specific I should do? Just extracting the file in
Nautilus doesn’t generate any entries in journalctl.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815480
Title:
“Extract Here”
** Changed in: apport (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814611
Title:
ubuntu-bug never (any longer) opens browser window
To manage
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
What's the issue exactly? That the package doesn't show a text interface
to configure things anymore? That seems the same than bug #1788235 which
has been closed as not being a bug
@Alec, the issue you are referring to is different right?
** Changed in: lirc (Ubuntu)
Importance: Undecided =>
*** This bug is a duplicate of bug 1813354 ***
https://bugs.launchpad.net/bugs/1813354
also I believe I did not use mirror:// urls but I used the
mirror.ubuntu.com urls
--
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 1813354 ***
https://bugs.launchpad.net/bugs/1813354
This was marked as a duplicate of bug #1813354 but my situation was
different. The upgrader began the upgrade and failed due to a package
problem. I only INFERRED that the problem was due to the mirror
Thanks for the update, closing the bug then
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/437288
Title:
Nautilus uses a
The right place to report requests like that is also upstream where the
code is written, https://gitlab.gnome.org/GNOME/gtk/issues
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413283
Title:
"Set
** Package changed: xorg (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814481
Title:
bluetooth keyboard not working
To manage notifications about this bug go to:
** Changed in: cups (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813432
Title:
Specific PDF file fails to print to HP m551dn printer
To manage
** Package changed: tracker (Ubuntu) => cheese (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815323
Title:
After Cheese update does not work
To manage notifications about this bug go to:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
*** This bug is a duplicate of bug 1813354 ***
https://bugs.launchpad.net/bugs/1813354
** This bug has been marked a duplicate of bug 1813354
release-upgrader unable to deal with sources.list entries of "deb mirror://"
--
You received this bug notification because you are a member of
It's weird that vm/real machine would make a difference, maybe it's a
timing issue (.desktop created by snapd later than the desktop UI loads
and the UI doesn't refresh?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for your bug report, could you maybe report it as well to the gvfs
upstream gitlab?
https://gitlab.gnome.org/GNOME/gvfs/issues
** Changed in: gvfs (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1 - 100 of 540 matches
Mail list logo
