I use this extension as a workaround: [fix-dark-theme-input-
boxes](https://addons.mozilla.org/en-US/firefox/addon/fix-dark-theme-
input-boxes/) ([source](https://gitlab.com/Roboe/userscripts/tree/master
/fix-dark-theme-input-boxes/))
--
You received this bug notification because you are a
** Bug watch added: Mozilla Bugzilla #1527048
https://bugzilla.mozilla.org/show_bug.cgi?id=1527048
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/220263
Title:
Bad Firefox integration with dark
In the mean time, could `widget.content.gtk-theme-override` be set to
`Adwaita` by default? This would fix the issue (except for the settings
page), and Adwaita is always present on systems with GTK+. I opened
https://bugzilla.mozilla.org/show_bug.cgi?id=1527048 for this change,
everyone please
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
Public bug reported:
tracking bug
** Affects: freeipmi (Ubuntu)
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/1815897
Title:
Please merge 1.6.3-1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: squid (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/1815852
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: squid (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/1815852
Title:
Public bug reported:
* Impact
That's a new bug-fix only update from GNOME
There is a micro-release exception for GNOME:
https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
https://gitlab.gnome.org/GNOME/evolution/blob/gnome-3-30/NEWS
https://gitlab.gnome.org/GNOME/evolution/commits/gnome-3-30
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The breaking check is in virDomainDefCheckABIStabilityFlags which is meant to:
This compares two configurations and looks for any differences
which will affect the guest ABI. This is primarily to allow
validation of custom XML config passed in during
*** This bug is a duplicate of bug 1814949 ***
https://bugs.launchpad.net/bugs/1814949
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1814949, so is being marked as such.
** Description changed:
+ * Impact
+ Evolution doesn't work with Kopano IMAP servers:
+
+ * Test case
+ Configure an account on a Kopano IMAP server and try to use it from evolution
+
+ * Regression potential
+ The change is in the imap handling code so it would be good to test on a few
looks like fixed in Debian, and imported in Ubuntu. Closing
** Changed in: python-selenium (Ubuntu)
Status: New => 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/1188271
Title:
looks like the latest version is fixed, so from bionic to disco it
should be already ok.
** Changed in: python-selenium (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like this feature has been added to linux kernel after v4.19.
Do you know how many levels of backlit the keyboard has?
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815663
Title:
package php7.0-common 7.0.33-0ubuntu0.16.04.1 failed to
install/upgrade: subprocess installed
And yes - there is no way to "permanently" edit the snapshots as their
metadata is meant to store the data of the time it was taken.
Actually lets keep the bug open for "virsh snapshot-edit" being unable to set a
different type.
virsh snapshot-edit disco-mt-zesty 1550137482
error: unsupported
I updated the description to de-confuse myself and others that might
come by.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802944
Title:
error: unsupported configuration: Target domain machine
Public bug reported:
During 18.04.2 iso testing, I have picked up the i386 Xubuntu isos for a
quick sanity-test on kvm. Even though the live-session tests have
succeeded (everything seemed to work as expected), I seem to be having
issues booting an installed system on kvm.
The Xubuntu system
Hello.
There is a similar raport about failed 'nvidia_304' module build on
latest '-proposed' v4.4.0-143-generic kernel:
✗ https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-304/+bug/1815858
Mentioned issue happened on both: amd64 and i385/i686 architectures.
Best regards.
--
>From log:
Feb 13 12:40:32 GoodWeather amavis[6939]: Starting amavisd: The value of
variable $myhostname is "GoodWeather", but should have been
Feb 13 12:40:32 GoodWeather amavis[6939]: a fully qualified domain name;
perhaps uname(3) did not provide such.
Feb 13 12:40:32 GoodWeather
Hi Guilherme,
Thanks for your response. I was under the impression that there would
also be fix in 'proposed' for Xenial-HWE.
I can confirm that the issue is fixed in 4.4.0-143 (and indeed present
in 4.4.0-142).
Best,
W;-)
--
You received this bug notification because you are a member of
Upstream comment
'smbc_new_context() calls smbc_setOptionUseCCache(context, True) if
LIBSMBCLIENT_NO_CCACHE environemnt variable is not defined. I suppose it
is not defined in your system, but can you please confirm it?
smbclient --kerberos --use-ccache doesn't work as it forces kerberos to
be
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu. Specifically it looks like your system has a misconfigured FQDN.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812387
Title:
tmux crashes on tpm init
To manage notifications about this bug go to:
^ Sorry, just to add clarity:
I am not demonstrating the exploit working from within a devmode snap. I
am demonstrating a devmode snap packaged inside the exploit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Did anyone manage to get a clue on where is that problem coming from?
Ubuntu? Nautilus? Gnome? and how to solve it?
It is very annoying!
I have
Ubuntu 18.04.2 LTS
Nautilus 3.26.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--- Comment From ifran...@de.ibm.com 2019-02-14 02:55 EDT---
I already did test this as a PPA (2.16-5ubuntu0.1) on Ubuntu 18.10, see a few
comments above. Do you want me to test it again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
wil not confirm that closing and reopening the document helps. That does
not have any effect in my case.
Op di 12 feb. 2019 om 11:25 schreef adam boncz
<1724...@bugs.launchpad.net>:
> Affects me often with LibreOffice 6.0.7.3 on Ubuntu 18.04 (Build ID:
> 1:6.0.7-0ubuntu0.18.04.2). Only help is
Public bug reported:
LibreOffice 6.0.2 shows truncated/cropped text on some options in the
contextual grouped menu (notebook bar). See attached. Notice words like
Italic, Underlined, Left, etc.
This with 96dpi on 1920x1080p resolution, Enabled anti-aliasing with
rgba/slight hinting in Plasma on
Hello.
It seems, that I'm experiencing exactly the same problem. During kernel
update process to v4.4.0-143.169 (from '-proposed') there was an error
message about some issues with 'nvidia' module etc.
'/var/lib/dkms/nvidia-304/304.135/build/make.log' file contains a full
build process
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
Public bug reported:
Whenever I try to shutdown my computer it hangs at umounting _netdev
mounted drives.
The reason looks as if NetworkManager is stopped and therefore
connection to the remote devices are lost.
Suggestion is that NetworkManager shutdown is put at the end of the
chain. Just as
Chris, I've just read your blog post at:
https://shenaniganslabs.io/2019/02/13/Dirty-Sock.html
There you install a snap in devmode, which does a bunch of things to
demonstrate that the snap can access system resources via the
vulnerability in <2.37. Just for the record, it's slightly undue to
II fact that's not an issue in 18.10, it was created in Debian by
dropping the exit 0 call
** Changed in: evolution-data-server (Ubuntu)
Importance: Undecided => Low
** Changed in: evolution-data-server (Ubuntu)
Status: New => Fix Released
--
You received this bug notification
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Note that when using python{,3}-selenium, the default path can be
overridden like that:
from selenium import webdriver
driver =
webdriver.Chrome(executable_path="/usr/lib/chromium-browser/chromedriver")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/prepare-package-lbm
Status: New => Invalid
** Changed in:
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu
Status: New => Invalid
** 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
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira
(halves)
** Changed in: makedumpfile (Ubuntu Bionic)
Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira
(halves)
** Changed in: makedumpfile
This bug was fixed in the package linux-raspi2 - 4.18.0-1009.11
---
linux-raspi2 (4.18.0-1009.11) cosmic; urgency=medium
* linux-raspi2: 4.18.0-1009.11 -proposed tracker (LP: #1811412)
* Cosmic update: 4.18.19 upstream stable release (LP: #1810820)
- [Config] Update config
The error looks like https://bugzilla.gnome.org/show_bug.cgi?id=770754
which should be fixed on newer versions, can you try on Ubuntu 18.04 if
that's still a problem?
** Bug watch added: GNOME Bug Tracker #770754
https://bugzilla.gnome.org/show_bug.cgi?id=770754
** Changed in: evolution-ews
Is that still an issue in newer versions?
** Changed in: evolution-ews (Ubuntu)
Importance: Undecided => Low
** Changed in: evolution-ews (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
*
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
*
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
*
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
*
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
*
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
*
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
*
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
*
Public bug reported:
During attach new interface to the instance, I have an error (from
dmesg):
[1387677.245725] audit: type=1400 audit(1550147444.575:10991):
apparmor="DENIED" operation="file_receive" profile="libvirt-fc5b1ccd-
6d5c-459e-8d6b-b98c26df504e" name="/dev/vhost-net" pid=36309
** Summary changed:
- linux-gcp-edge: -proposed tracker
+ linux-gcp-edge: 4.18.0-1007.8~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
Hi Daniel,
thank you for your report and your help making Ubuntu better.
Your workaround is exactly the right way flag your system for your special
local configuration.
In later releases there is a file at:
/etc/apparmor.d/local/abstractions/libvirt-qemu
Which shall help to add a rule without
[VERIFICATION BIONIC]
I can modprobe the mq-deadline, kyber and bfq schedulers but it looks
like doing a modprobe of the cfq and deadline schedulers doesn't list
them as choices in the available schedulers:
# uname -r
4.18.0-1009-azure
# modprobe bfq
# modprobe cfq-iosched
# modprobe
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
*
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
The new version has been uploaded as a SRU but it's going to take a bit
before it's review/accepted, meanwhile you get get the deb from that ppa
for testing if you want, https://launchpad.net/~ubuntu-
desktop/+archive/ubuntu/ppa
--
You received this bug notification because you are a member of
This bug was fixed in the package linux-raspi2 - 4.18.0-1009.11
---
linux-raspi2 (4.18.0-1009.11) cosmic; urgency=medium
* linux-raspi2: 4.18.0-1009.11 -proposed tracker (LP: #1811412)
* Cosmic update: 4.18.19 upstream stable release (LP: #1810820)
- [Config] Update config
This bug was fixed in the package linux-raspi2 - 4.18.0-1009.11
---
linux-raspi2 (4.18.0-1009.11) cosmic; urgency=medium
* linux-raspi2: 4.18.0-1009.11 -proposed tracker (LP: #1811412)
* Cosmic update: 4.18.19 upstream stable release (LP: #1810820)
- [Config] Update config
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
Public bug reported:
On Ubuntu 16.04.x, I have a perfectly working custom systemd service
file which sets username and group for the service as
[Service]
User=user
Group=domain users
where both group and user come from an AD domain joined to with winbind.
This is not working anymore on 18.04.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
** Description changed:
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
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
Hi
How will I make a fuller description if it does not generate report for
submission and that is what I am reporting?
In the description and pictures it contains all possible information for
improvement of Ubuntu 19.04 Disk, perhaps lack vision of who the program, no?
How do I report or
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** 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
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
** Changed in: makedumpfile (Ubuntu Trusty)
Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira
(halves)
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)
** Changed in: makedumpfile (Ubuntu Bionic)
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
tools/virsh-snapshot.c
-> cmdSnapshotCreate collects arguments and sets flags
-> virshSnapshotCreate does the handling then
- gets the xml in const char *from
- flags in unsigned int flags
-> virDomainSnapshotCreateXML gets xml and flags
-> impl callback
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
101 - 200 of 816 matches
Mail list logo
