This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
--
You
** Bug watch added: Debian Bug tracker #889811
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889811
** Also affects: gosa (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889811
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubu
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
--
You
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubu
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubu
This bug is believed to be fixed in cloud-init in 18.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubu
Public bug reported:
Steps to reproduce:
1. Try to make delayed screenshot of area with `gnome-screenshot --area --delay
10`
Expected results:
User is able to set delay when taking screenshot of area
Actual results:
User is unable to set delay when taking screenshot of area because of options
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glib2.0 (Ubuntu Trusty)
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/1750741
Titl
Eventually those apparmor changes will hit the backported PPA builds
too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751005
Title:
libreoffice cannot open a document not within $HOME
To manage
How about: create a OneShot service that just polls to see if the zfs
mount is done, and have it be RequiredBy and Before the snap mount
units.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750059
Ti
Thanks Emily!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723900
Title:
unbound systemctl (re)start fails due to Apparmor profile issue
To manage notifications about this bug go to:
https://bugs
gosa: https://github.com/gosa-project/gosa-core/issues/12
** Bug watch added: github.com/gosa-project/gosa-core/issues #12
https://github.com/gosa-project/gosa-core/issues/12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Bug watch added: GNOME Bug Tracker #793736
https://bugzilla.gnome.org/show_bug.cgi?id=793736
** Also affects: gnome-screenshot via
https://bugzilla.gnome.org/show_bug.cgi?id=793736
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a memb
** Tags added: kernel-bug-exists-upstream
** Tags removed: kernel-bug-exists-upstream resume suspend
** Tags added: kernel-fixed-upstream
** Tags removed: kernel-fixed-upstream
** Tags added: kernel-bug-exists-upstream suspend
** Tags removed: suspend
** Tags added: suspend-resume
** Tags remov
** Tags added: kernel-bug-exists-upstream
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749826
Title:
[LENOVO 20A8S
On 22 February 2018 at 20:20, Bryan Quigley wrote:
> @xnox
> "The journald daemon has limits set for logs, meaning they will be rotated
> and discarded and should not cause out of disk-space errors."
>
> What are they? AFAICT it only has limits on the number of files, but
> not how big they can
On 22 February 2018 at 21:11, Bryan Quigley wrote:
> @markstos
> Sorry, yea, I meant our defaults, not the journal config options itself.
> SystemMaxUse= is unset in the config in bionic (although it's all commented
> out, but I believe that's supposed to indicate our defaults?)
>
> Re:disk writ
** Description changed:
- After an upgrade from Xenial to Bionic the session fails to start and
- returns immediately to the login screen.
+ [Testcase]
+
+ 1. Launch xenial lxd container
+ 2. install x11-common upstart
+ 3. do-release-upgrade to bionic
+ 4. Upgrade to bionic removes upstart
+ 5.
Thanks Joseph for your help. I have always had this problem with this
machine.
I installed the new kernel v4.16 [0] and now the computer hibernates and
resumes successfully. But in the suspend process the computer does not
get resume. The computer never gets out of the suspend state.
---
[0] http
On Thu, Feb 22, 2018 at 08:33:19PM -, sean wrote:
> I feel that sssd_be spiraling out of control (spawning hundreds to
> thousands of processes) and consuming all of the available RAM would be
> considered a "High-impact" bug, when that same behavior is not observed
> in 14.04.
Indeed, which i
Public bug reported:
Steps to reproduce:
1. Launch gnome-screenshot interactively with `gnome-screenshot -i`
2. Click on "Select are to grab" for taking screenshot of area
3. Try to set delay
Expected results:
User is able to set delay when creating screenshot of area
Actual results:
User is una
> Is /efi/ubuntu/grubx64.efi on your EFI System Partition definitely the
> Canonical-signed image from grub-efi-amd64-signed?
I presume so? dpkg says it is:
ubuntu@xwing:/boot/efi/EFI/ubuntu$ dpkg -S grubx64.efi
grub-efi-amd64-signed: /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed
That's the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: avidemux (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/1673566
Title:
[
** 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/1749826
Title:
[LENOVO 20A8S0UU00] hibernate/resume failure
To manage notifications about this bug go to:
https:/
Thanks Joseph for your help. I have always had this problem with this
machine.
I installed the new kernel v4.16 [0] and now the computer hibernates and
resumes successfully. I edited the tags and I put 'kernel-fixed-
upstream' and "Confirmed" in the status, is that right?
** Changed in: linux (U
On Thu, Feb 22, 2018 at 11:06:51PM -, Jeff Lane wrote:
> > Is /efi/ubuntu/grubx64.efi on your EFI System Partition definitely the
> > Canonical-signed image from grub-efi-amd64-signed?
> I presume so? dpkg says it is:
> ubuntu@xwing:/boot/efi/EFI/ubuntu$ dpkg -S grubx64.efi
> grub-efi-amd64-s
The kernel also has the bug.
Please keep doing the bisect and I will gladly keep trying them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751098
Title:
Ubuntu hangs shortly after booting with ke
Dimitri, could you split the duplication issue into a separate bug?
(On that topic, see also https://community.ubuntu.com/t/no-rsyslog-in-
default-desktop-install/4169 )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
AFAICS there has been no attempt in the archive to rebuild this package
for the new libindi soname. Please point to the reason this is a
removal request instead of a no-change rebuild request.
** Changed in: indi-sbig (Ubuntu)
Status: New => Incomplete
--
You received this bug notificati
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment to this bug report it
seems that there may be a problem with your hardware. I'd recommend
performing a back up and then investigating the situation. Measures you
might take include
$ remove-package -m "Ubuntu-specific, FTBFS; LP: #1750716" indi-sbig -y
Removing packages from bionic:
indi-sbig 1.0-0ubuntu11 in bionic
indi-sbig 1.0-0ubuntu11 in bionic amd64
indi-sbig 1.0-0ubuntu11 in bionic i386
Comment: Ubuntu-specific, FTBFS; LP: #17507
Thanks, build failures seen here.
https://launchpad.net/ubuntu/+source/indi-sbig/1.0-0ubuntu12
** Changed in: indi-sbig (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Wow, that is ugly. This should definitvely be a release blocker...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748028
Title:
Flashing text at bottom of grub menu
To manage notifications about th
This is a debdiff for Bionic applicable to 7.6p1-4. I built the binary packages
in pbuilder
and they build, upgraded and installed successfully.
Tested that the ifup hook was removed on upgrade, and also on install it
was never installed.
I went through a series of tests on a laptop with a wirel
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751140
Title:
nss-pem needs additional headers, static libs to build
To manage notifications about this bug go to:
https://bugs.l
Not only same video issue as others on Trusty with Nvidia 340.102 driver
for GEForce 8400GS, but am also unable to log in.Entering PW just keeps
flipping me back to "Enter PW box". Old 112 kernel works just fine so I
will stick with that until a fix is available.
--
You received this bug notifica
The attachment "openssh-7.6p1-4ubuntu1.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" t
Add me to the List of People with this problem, nvidia 384.111 worked
great until this kernel now same problem as original poster. Had to go
back to 112 to get it to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
What to do now, please?
On Feb 23, 2018 3:21 AM, "Brian Murray" wrote:
This is not a bug with the release upgrader rather with some other
package that was upgraded during the upgrade process.
** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu
--
You received this bug notification b
** Package changed: ubuntu => debian-installer (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751151
Title:
Installing via IPv6 results in invalid netplan yaml
To manage notifications abou
Public bug reported:
each installation with many linux os had seem well ; but at the first boot
never start well.
at the third installation to day there is the report of bug
i used ubuntu, bodhi, and never reboot just stay hibernation or veille ...
and every things go well.
but a day : i'hd for
Hi Dimitri,
> On Feb 22, 2018, at 8:32 AM, Dimitri John Ledkov
> wrote:
>
> john-center - I believe mdadm is used by default, instead of dmraid.
> However, I'm not sure if we do correctly activate Intel Raids with
> mdadm. I have not done an install with either 16.04 or 18.04. Or I guess
> at l
This happens my Mint too. Bluetooth keyboard is working after resume from
suspend but mouse (Logitech M720 Triatlon) is not. bluetoothctl says Connected:
yes .. no .. yes .. no
But bluetoothctl: agent off/on helps (no need to use power and pair commands).
--
You received this bug notification
iBART, dmesg @ YEPO 737A (obtained after closing the cover and opening
it back after preliminary login - touchpad works with fully workable
mouse and both buttons after that) is attached.
I used next cmds in order to automatically enter into
4.16.0-041600rc1-lowlatency after reboot:
yep ~ # wget
This brings a good point. What I didn’t test, which will do tomorrow, is
what happens if I kill Maas and let the same system boot from disk. I
wonder if it will boot.
On Thu, Feb 22, 2018 at 6:20 PM Jeff Lane
wrote:
> > Is /efi/ubuntu/grubx64.efi on your EFI System Partition definitely the
> > C
Now, SAI crashs on Wine 3.2
0009:fixme:htmlhelp:HtmlHelpW HH case HH_INITIALIZE not handled.
002c:fixme:appbar:SHAppBarMessage unknown msg: 4
0028:fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub
0028:fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR,
hwnd
Public bug reported:
Ubuntu 16.04.3
Package: libluajit-5.1-common
I expected it to install when I clicked on OK or ENTER.
It didn't do anything, at all, even after waiting for
a couple of hours.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libluajit-5.1-common 2.0.4+dfsg-1
ProcVersio
Hello Umer, can you provide some more information?
Thanks
** Information type changed from Private Security to Public Security
** Changed in: unity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Talked to Timo on IRC, 1.0.0-3 (pending an upstream update) will be
published before feature freeze and will enable the tests. Verifying
with cyphermox on IRC that that's ok from a MIR team perspective :)
I will approve it once I hear back from Mathieu.
** Changed in: libglvnd (Ubuntu)
Sta
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
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 #1748450, so is being marked as such.
On Thu, Feb 22, 2018 at 6:28 PM, Steve Langasek
wrote:
> On Thu, Feb 22, 2018 at 11:06:51PM -, Jeff Lane wrote:
>> > Is /efi/ubuntu/grubx64.efi on your EFI System Partition definitely the
>> > Canonical-signed image from grub-efi-amd64-signed?
>
>> I presume so? dpkg says it is:They look the s
@osomon: are you looking for sponsorship for the debdiff? The patch
looks good to me and I assume you've tested it?
** Changed in: libepubgen (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Changed in: mate-desktop
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751141
Title:
mate-screenshot does not allow to set delay when taking screenshot of
area wi
FWIW, I did a bit of extra testing. I killed maas' rackd (which provides
PXE). Rebooted the machine and I saw:
1. It attempted to PXE boot multiple times (like a lot)
2. It eventually gave up and booted from disk
So it successfully booted into the deployed OS.
I noticed that the curtin installat
On Thu, Feb 22, 2018 at 7:55 PM, Jeff Lane
wrote:
> On Thu, Feb 22, 2018 at 6:28 PM, Steve Langasek
> wrote:
> > On Thu, Feb 22, 2018 at 11:06:51PM -, Jeff Lane wrote:
> >> > Is /efi/ubuntu/grubx64.efi on your EFI System Partition definitely the
> >> > Canonical-signed image from grub-efi-am
Upstream discussion with cakephp maintainers implies we should drop
cakephp (and re-sync if Debian does fix this):
https://github.com/cakephp/cakephp/pull/11643
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Changed in: nss (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751140
Title:
nss-pem needs additional headers, static libs to build
To manage notifications
** Changed in: gosa (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749745
Title:
php7.2 has removed the mcrypt module
To manage notifications about this bug g
There are a number of outstanding bugs in Debian with zoneminder, so I
think we hsould just remove it as well.
** Also affects: zoneminder (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cakephp (Ubuntu)
Status: Incomplete => New
--
You received this bug notification
The problem only occurs using Wayland, using Xorg it works normally.
That is why it works by default (Xorg) in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750443
Title:
sudo nautilus or ge
Please clarify exactly which kernel versions you have tested. It will
help us to narrow down the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750379
Title:
Distortion Realtek ALC887
To m
On Fri, Feb 23, 2018 at 01:13:42AM -, Andres Rodriguez wrote:
> > bladernr@critical-maas:/var/lib/maas/boot-resources/
> > current/bootloader/uefi/amd64$
> > ll
> > total 2328
> > drwxr-xr-x 2 maas maas4096 Feb 22 17:34 ./
> > drwxr-xr-x 4 maas maas4096 Feb 22 17:34 ../
> > -rw-r--r-- 2
** Description changed:
Error message the virtual machine Ubuntu 17.10:
---
No protocol specified
Unable to init server: Could not connect: Connection refused
(nautilus:2377): Gtk-WARNING **: cannot open display: :0
---
- Note that it
** Attachment added: "Gigabyte R120 (ACPI mode ThunderX)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5060797/+files/submission_2018-02-23T00.42.57.591881.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "Cavium CRB (ThunderX) results"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5060796/+files/submission_2018-02-23T00.42.54.821054.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
P.S. Nothing has been committed or even proposed to Ubuntu yet. So not
Fix Committed yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751086
Title:
Xorg assert failure: Xorg: ../src/evdev-mt-touc
Interesting it's a different assertion to bug 1750664. But hopefully the
same fix applies?
** Changed in: libinput (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
The failure mentioned in Comment #15 is a test suite bug - see LP:
#1751167. I applied a hot-fix, re-ran the test, and it passed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749040
Title:
KPTI-en
\o/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751070
Title:
mutter 3.28 transition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1
I'm talking about changing the driver in the guest, on the assumption
this bug was reported from the guest (which is what we need). However
now that you mention it, you probably reported this from the host so the
above logs would be misleading and probably irrelevant...
If that's correct then unfo
Public bug reported:
Since upgrading to Ubuntu 17.10, Rhythmbox does not record the metadata
entered in the "Extract" interface when converting CDs to FLAC files. (I
have not checked to see if the same is true with mp3.)
Expected behaviour: I load a CD, and Rhythmbox loads the metadata for
the al
** Tags added: artful trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246981
Title:
Bluetooth mouse fails to re-connect after sleep.
To manage notifications about this bug go to:
https://bugs
** Changed in: gnome-screenshot
Status: Unknown => Confirmed
** Changed in: gnome-screenshot
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751157
Title:
gno
Public bug reported:
Currently any invocation of curtin that incurs an exception during the
'install' phase will trigger a path which runs the error log collection
code.
THere's a bug there which runs sys.exit() in the non-main body of the
code; Instead only subcommands _main_ methods should use
** Summary changed:
- nvidia-304 kernel module failed to build with new bionic kernel
+ nvidia-304 kernel module failed to build with new bionic kernel [error:
implicit declaration of function ‘init_timer’; did you mean ‘init_timers’?]
--
You received this bug notification because you are a mem
upstream did set /var/lib/zabbix as home directory (but not created it).
I suggest using this directory and ensuring it exists. This would be in
line with other daemons like postfix or snmp. Vote for the above
mentioned bug report to have it fixed upstream.
--
You received this bug notification b
** Tags added: originate-from-1734269 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748853
Title:
Intel 9462 A370:42A4 doesn't work
To manage notifications about this bug go to:
https:/
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750732
Title:
grub package will change the boot order for MaaS deployed system
To manage notifications about this bug
I've removed the verification-failed-xenial tag.
The problem reported in bug 1750732 may be related to a grub upgrade, but
surely is not related to this specific grub upgrade.
Please see the changes
http://launchpadlibrarian.net/354651271/grub2_2.02~beta2-36ubuntu3.16_2.02~beta2-36ubuntu3.17.di
A good first step would be for someone to check that the bug is fixed in
bionic, as the package has been updated there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title:
[SRU] [xeni
Verified the hwe kernel 4.13.0-36.40~16.04.1, including the fix patch.
The WestenXT is able to be controlled by pm-runtime normally.
Jerry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742759
Title:
** Changed in: gnome-screenshot
Status: Unknown => Confirmed
** Changed in: gnome-screenshot
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751161
Title:
"Gr
Public bug reported:
Description:Ubuntu 17.10
Release:17.10
:~$ apt-cache policy pkgname
N: Unable to locate package pkgname
I was running sudo apt upgrade.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: gdm3 3.26.1-3ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generi
** 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/1751182
Title:
package gdm3 3.26.1-3ubuntu3 failed to install/upgrade: subprocess
installed pre-removal script r
No, I never found a solution for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637749
Title:
Ctrl+Super+Right shortcut key is not working
To manage notifications about this bug go to:
https:
If plymouth needs this font, this package should be a dependency.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751184
Title:
Plymouth initramfs hook needs missing dependancy fonts-dejavu-core so
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1751184
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
Missing font dependency --> plymouth initramfs hook fails --> update-
initramfs fails --> new kernel failed to install.
Bionic Lubuntu alternate 20180221
update-initramfs -c -k all
It gives an error:
Rebuilding ramfs...be patient
update-initramfs: Generating /boot/initrd.i
Hi.
I've confirmed this fix by using curtin's "vmtest" test harness.
I've applied the attached patch to curtin at 82622f129b.
The patch does:
a.) remove the work arounds we had in place to make zfs root work on xenial.
b.) enable proposed
Then I've run an install of a system that does a installat
** Attachment added: "first boot console log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/+attachment/5060822/+files/boot-serial.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Attachment added: "installation console log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/+attachment/5060821/+files/install-serial.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
>From the install log you can see that we install grub2 at
>2.02~beta2-36ubuntu3.17.
..
Unpacking grub2-common (2.02~beta2-36ubuntu3.17)
..
'dpkg-reconfigure grub-pc' and 'grub-install /dev/vda' are run
And also:
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-116-g
Currently at 2.3Gb ram up 11 days(ubuntu Studio)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736067
Title:
panel-6-indicat app memory leak
To manage notifications about this bug go to:
https://b
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928
the same problem with me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748835
Title:
package libsane1 1.
** 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/1751187
Title:
package python-apt 1.1.0~beta1build1 failed to install/upgrade:
subprocess installed post-install
Public bug reported:
I don't know what happen
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-apt 1.1.0~beta1build1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
curl: Instal
Getting this fixed in cloud-init is tricky.
In ifupdown (/etc/network/interfaces) world, we just took the "global dns"
entries and put them on the loopback device (lo). Since that device would
always be brought up, and never really brought down, it served its purpose.
That is what Ryan tried ab
Approving MIR with the understanding that Timo will do a future upload
in Bionic (ideally synced from Debian) with the build-time tests.
** Changed in: libglvnd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
601 - 700 of 765 matches
Mail list logo
