Any idea when Focal will be completed ?
Regards,
Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcard pam config needs to be updated for
(I have ping sil2100 internally for him to provide his 2 cents on this
bug.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcard pam config
Lukasz (sil2100) can we have your SRU team input on this bug with regard
to Bionic/18.04lTS ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
** Changed in: gdm3 (Ubuntu Groovy)
Importance: Medium => High
** Also affects: pam (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: gdm3 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Bionic)
Importance: Undecided
Sponsored by dgadomski. Unsubscribing sts-sponsor team.
Thanks for your contribution Seyeong.
Thanks for the sponsoring Dariusz.
- Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Changed in: network-manager (Ubuntu Bionic)
Status: Confirmed => In Progress
** Tags added: sts-sponsor-dgadomski
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
@xtrusia,
Is this ready for sponsorship ?
I'll have a look when ready.
- Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to
** Description changed:
+
+ [Impact]
+ [Test Case]
+ [Potential Regression]
+
+ [Other informations]
+
+ * Upstream bug[0] and fix[1]:
+
+ https://bugzilla.redhat.com/show_bug.cgi?id=1575944
+ https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35
+
+ * Only affectinb
Thanks for reporting the outcome of your test.
We will start the SRU process in order to update network-manager package
next week.
Regards,
Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
This look like a similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1575944
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35
A test package (including the above fix) is available on my PPA:
sudo add-apt-repository ppa:slashd/lp1794478
sudo apt-get update
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1843044
Title:
firefox crashes on a FIPS enabled machine
Status in Mozilla Firefox:
New
Status in
** Changed in: network-manager (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to
Setting 'bionic' from "Fix Released" to "Confirmed" since 2 different
persons stated the problem still exist (supported with reproducer
testing)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Changed in: network-manager (Ubuntu Bionic)
Status: Fix Released => Confirmed
** Changed in: network-manager (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
The netplan.io (arm64) autopkgtest failure (due to timeout) has been retried
today, it passed:
http://autopkgtest.ubuntu.com/packages/n/netplan.io/bionic/arm64
No more failure reported in pending sru page.
- Eric
--
You received this bug notification because you are a member of Desktop
** Tags removed: sts-sponsor-slashd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1848210
Title:
ghostscript: ensure update of cups-filter
Status in cups-filters package in
$ pull-lp-source cups-filters xenial
debian/control:
.
Package: cups-filters
Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends},
cups-filters-core-drivers (>= ${binary:Version}),
bc,
ghostscript (>= 9.02~),
imagemagick (>= 6.4~),
poppler-utils
$ pull-lp-source
$ pull-lp-source cups-filters xenial
debian/control:
.
Package: cups-filters
Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends},
cups-filters-core-drivers (>= ${binary:Version}),
bc,
ghostscript (>= 9.02~),
imagemagick (>= 6.4~),
poppler-utils
$ pull-lp-source
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1848210
Title:
ghostscript: ensure update of cups-filter
Status in cups-filters package in
I will be more favourable to do the other way around by adding a
"Depends:" in cups-filters package for ghostscript version "X" ?
Especially if cups-filters always needs ghostscript ?
It will force ghostscript to get updated instead of making the package
install to fails/breaks.
At least it's
I will be more favourable to do the other way around by adding a
"Depends:" in cups-filters package for ghostscript version "X" ?
Especially if cups-filters always needs ghostscript ?
"Depends: ghostscript (>= CUPS_FILTER_VERSION)"
to force ghostscript to get updated instead of making the
Public bug reported:
As requested by SRU verification team:
https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1589289/comments/33
As for xenial's chromium-browser test failures - could you please file a
bug about the failing architectures? I would then include the bug number
in the
Sponsored for Bionic.
* Patch already found in Cosmic onwards.
* Patch has been tested pre-SRU with an impact user.
* Nitpick: I have added the upstream bug link in the DEP3 header ->
+Bug-Upstream: https://github.com/ibus/ibus/issues/2002
Thanks Matthew !
** Bug watch added:
** Description changed:
[Impact]
The following has been seen in a VMware Horizon VDI. I cannot reproduce this
issue myself.
When a user interacts with any password field in Firefox, gnome-shell
and Firefox both freeze and the system becomes unusable. If you ssh into
the system
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx
The testing phase where the kernel will land in bionic-proposed pocket is due
around :
08-Jul - 19-Jul Bug verification & Regression testing
This is where I'll need you guys to test the proposed kernel and confirm
it still work as expected for you.
- Eric
--
You received this bug notification
Just got the 2 required ACK from kernel team for the patch I have submitted.
Everything looks good for the patch to be part of the next kernel cycle as
described in previous comment.
- Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Todd, The fix will land in the next kernel cycle.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx using bionic kernel 4.15
Status
kernel-team archive ML:
https://lists.ubuntu.com/archives/kernel-team/2019-June/101489.html
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland,
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
Ok, including my own testing we got 4 positive feedback.
With that being said, I have just submitted the patch to our kernel team a few
minutes ago.
This will be part of the next cycle 01-July through 21-July.
Thanks for the pre-SRU testing, we will need you guys one more time
during the
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
Great for the quick feedback.
I have until June 26th to submit the patch for the next cycle[0]
It's giving me a couple of more days to get other impacted users
feedback.
[0] - https://kernel.ubuntu.com/
- Eric
--
You received this bug notification because you are a member of Desktop
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Bionic)
Importance: Critical => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Detailled instructions on how to use my ppa :
$ sudo add-apt-repository ppa:slashd/kernel-builder
$ sudo apt-get update
$ sudo apt install linux-image-unsigned-4.15.0-53-generic
linux-modules-4.15.0-53-generic linux-modules-extra-4.15.0-53-generic
then reboot, and once login you can confirm if
** Description changed:
+ [Impact]
+
+ With most recent version of mutter installed.
+ If running kernel is in the 4.15 serie (using the vmwgfx video kernel drive)
and if the login screen uses wayland, then the login prompt doesn't appears.
+ All we see is the purple background with ubuntu at
After building and testing:
"
9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
"
the above seems to do the trick ^ which will make the SRU easier (only one
commit).
I just don't know why the kernel git bisect testing found another commit, but
I already did that test ^ using the upstream kernel with 37efe80ce85f
being the HEAD, but "37efe80ce85f" - 1 was working as well, so I didn't
continue to pursue that commit, since it wasn't the first introduction
of the fix.
But based on last duflu update, I as I said I will now give a try again
Will also build a kernel 4.15 with 37efe80ce85f and see the outcome.
Should be able to provide an update by EOD.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login
My reproducer:
1) I used virtualbox 6.0.0 on disco (my desktop machine) # I guess it doesn't
really matter but I prefer giving more details than less ;)
2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
3) Make sure in the VM setting that the display uses 'VMSVGA' which will force
the OS
To continue on my comment #59 ... One user has been impacted on a
physical machine (non-vmware) with the same symptom but can't provide
public details unfortunately, but I witnessed the problem from my own
eye via remote session, and again upgrading to 4.18 kernel did the
trick.
So it really
as an fyi ...
It has been brought to my attention that this could impact other system
(outside vmware context)
so I still suspect a userspace change (possibly mutter) that introduce
behaviour change and break the interaction with certain part of the 4.15 kernel.
Do we know if the recent point
or if we identify the offending userspace change, then we can look at
the kernel again with and try to find what bit are missing, and if we
limit the kernel change then maybe the side-effect might not be present
again. (assumption here)
I think the next step is really to find what userspace
of if we identify the offending userspace change, then we can look at
the kernel again and try to find what bit are missing, and if we limit
the kernel change then maybe the side-effect won't be present too.
I think the next step is really to find what userspace change started
all this so we can
Daniel van Vugt (vanvugt),
Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?
I have strong believe, that something userspace has been changed and no
longer interact well with the vmware driver since then.
Just to look at our
The patchset is significant already without knowing yet what is missing to
address the side-effect.
I would need kernel team review/approval before thinking to SRU this into
Ubuntu 4.15.
I can't SRU this as-is, now knowing this will introduce a regression.
I'll keep you guys posted.
- Eric
Do you have the same display resizing situation with the hwe kernel 4.18
?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
My test kernel can be found here, if one want to test:
sudo add-apt-repository ppa:slashd/kernel-builder
sudo apt-get update
version: 4.15.0-53.57+hf231164v20190618b9
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
It's working if I apply the whole chain of commit on top of Ubuntu-4.15
I'll need to talk with kernel team and see if this is feasible for an
SRU.
52a59da2c439 drm/vmwgfx: Send the correct nonblock option for atomic_commit
cfffdaad3db9 drm/vmwgfx: Move the stdu vblank event to atomic function
This commit has most likely other 'drm/vmwgfx' commit deps. I'll work at
finding what other bits are missing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login
I have applied the good fix on top of current branch 4.15.0-53.57
---
c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
---
Build the kernel and I got the same problem still. Need to investigate
why it works fine using upstream
I have applied the good fix on top of current branch 4.15.0-53.57
---
c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
---
Build the kernel and I got the same problem still. Need to investigate
why it works fine using upstream
I'll do my best to provide a test kernel by tomorrow, for impacted user
to test, and confirm it works before I submit it to the Ubuntu kernel
team.
Stay tuned.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
904efd9e3f4c8f288b1279a316eed8e177190c8f doesn't.
So the kernel bisection is completed and found the right good commit
which is:
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
ac3069e67f5659131d7ac5f54d966005bbc40af8 doesn't.
So the kernel bisection is completed and found the right good commit
which is:
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx
wbug: With Bug
wnbug: With No Bug
git bisect start '--term-old=wbug' '--term-new=wnbug' '--'
'drivers/gpu/drm/vmwgfx'
# wbug: [62e9ccfaaedffd057e921fca976f9f7f71c9b254] Linux 4.16.18
git bisect wbug 62e9ccfaaedffd057e921fca976f9f7f71c9b254
# wnbug: [37efe80ce85f76b3b30d7b4ea40550e6a5a5b71a]
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
"20fb5a635a0c" also works just fine on my side, will continue with the
kernel bisect.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on
Building a kernel with "37efe80ce85f drm/vmwgfx: use monotonic event
timestamps" being the HEAD doesn't exhibit the issue.
I'm now building and about to test 37efe80ce85f^1 (AKA 20fb5a635a0c) to confirm.
In theory it should fails with "20fb5a635a0c" if "37efe80ce85f" is the one.
- Eric
--
You
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appe
Testing upstream kernel, I can tell this situation is not a Ubuntu kernel
specific issue.
I can reproduce using upstream kernel.
This is where I'm at the moment:
BAD kernel : v4.16.18
GOOD kernel : v4.17-rc1
Leaving us to the following 'vmwgfx' commits to bisect:
$ git log
Thanks Pat.
Glad you had the same result as I did.
I will start the kernel bisect to find out the commit which introduce the fix
and confirm my potential good candidate that I found by doing a git log
inspection.
Will keep you guys posted.
--
You received this bug notification because you
I marked this bug affecting the kernel 'linux', but I can't 'target to
series' and choose Bionic. It's not in the option list anymore
(something went wrong with that bug I think, but we can figure this out
later (when/if an SRU is needed)):
The only option I have available are:
Ff-series
Disco
I marked this bug affect the kernel 'linux' project, but I can't 'target
to series' and choose Bionic, it's not in the option list (something
went wrong with that bug I think, but we can figure this out later
(when/if an SRU is needed)):
The only option I have available are:
Ff-series
Disco
can someone impacted try v4.18 hwr kernel ? and let me know if it works
fine (without workarounds) just like it did for me ? I will perform the
kernel bisect next week to see what v4.15 is missing that 4.18 has to
fix this bug.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1832138 ***
https://bugs.launchpad.net/bugs/1832138
Only when using v4.15, if I use the hwe kernel 4.18 on Bionic it passes.
I have strong belief this kernel fix to be a potential good candidate,
but I need to run a bisection to confirm my assumption :
I reported the exact same problem and was able to reproduce.
Only using v4.15, if I use the hwe kernel 4.18 on Bionic it passes.
I have strong belief this kernel fix to be a potential good candidate,
but need to run a bisection to confirm my assumption :
commit
my bug report :
https://bugs.launchpad.net/bugs/1832903
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but setting
I was able to reproduce the problem with 4.15.0-51, but problem seems to
be gone using the hwe kernel 4.18.0-21-generic.
I'll do a kernel bisection and try to find the commit which fixes the situation.
I'll also ask another impacted user to confirm if v4.18 works fine too, to
double-check my
Public bug reported:
After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login
screen doesn't work if 'Wayland' is in use (default) and if video kernel
driver is 'vgwfx'.
It looks like the login screen got stuck, doesn't exit, and doesn't
fallback to 'x11' by itself in case of
FAIL: 12 warning messages, expected 8.
W [13/May/2019:13:53:19.857395 +] No JobPrivateAccess defined in policy
default - using defaults.
W [13/May/2019:13:53:19.857412 +] No JobPrivateValues defined in policy
default - using defaults.
W [13/May/2019:13:53:19.857428 +] No
I re-run a few test myselfs, and was able to clean them up.
Only remaining blocker is the FTBFS situation in Xenial for s390x arch which
seems to fails at override_dh_auto_test.
# Pending SRU:
cups
s390x: Failed to build
Sponsored for D/C/B/X.
Thanks Victor !
-Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1822062
Title:
Race condition on boot between cups and sssd
Status in cups package in
Sponsored for 'Eoan'. Let's start the SRU once cups land in eoan-
releases (Fix Released).
Thanks Victor !
- Eric
** Changed in: cups (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: cups (Ubuntu Disco)
Status: New => In Progress
** Changed in: cups (Ubuntu
This MIR request has been abandoned a support point of view.
** Changed in: libnfs (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => (unassigned)
** Changed in: libnfs (Ubuntu Cosmic)
Assignee: Eric Desrochers (slashd) => (unassigned)
** Changed in: libnfs (Ubuntu
There is a debian->ubuntu sync right now in eoan-proposed.
I'll sponsor it once the actual sync is completed and found in eoan-
releases.
Meanwhile, could you please report a bug and forward the patch to debian
to make sure the problem is fix to prevent re-introducing the issue at
next
** Changed in: cups (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: cups (Ubuntu Eoan)
Status: New => In Progress
** Changed in: cups (Ubuntu Eoan)
Assignee: (unassigned) => Victor Tapia (vtapia)
--
You received this bug notification because you are a member of
** Tags added: sts
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1637988
Title:
gvfsd-nfs not present in gvfs-backends, why?
Status in gvfs package in Ubuntu:
Fix Released
Bug
@cyphermox,
It was "Fix Released" for disco only[1], can we complete it for stable
releases ?
[1] - rmadison
libnfs | 1.2.0-3| precise/universe | source
libnfs | 1.3.0-2ubuntu1 | trusty/universe | source
libnfs | 1.9.8-1| xenial/universe | source
libnfs | 2.0.0-1~exp1 |
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
- 2.1) Modify /etc/gdm3/custom.conf
+
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1817738
Title:
Can't change virtual terminal when auto-login
Public bug reported:
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
Hi osomon,
Do we have enough testing to consider a copy into bionic-updates soon ?
I haven't dig but I saw a few ADT regressions in pending sru page.
Are they a blocker ? or known failures ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
The new stable version indicate the fix mentioned by seb128 is there but
no indication has been made in the debian/changelog to automatically
change the status, which breaks the SRU machinery for this particular
bug.
--- network-manager-1.10.6/src/nm-manager.c 2018-03-12 08:59:48.0
** Also affects: gdm3 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gdm3 (Ubuntu Cosmic)
Importance: Medium
Assignee: Dariusz Gadomski (dgadomski)
Status: In Progress
** Also affects: gdm3 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: resource-agents (Ubuntu)
Assignee: Eric Desrochers (slashd) => Mario Splivalo (mariosplivalo)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1749283
Ti
** Changed in: resource-agents (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: postgresql-common (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: postgresql-common (Ubuntu Xenial)
Status: In Progress => Won't Fix
** Changed in: p
** Also affects: resource-agents (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1749283
Title:
configured
It has been brought to my attention by a community user, that the
workaround (change scale from 200% to 100%) found in comment#14 works.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
** Tags removed: sts-sponsor-slashd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1749283
Title:
configured stats_temp_directory does not get created after reboot
Status
** Changed in: gnome-themes-standard (Ubuntu Artful)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: gnome-themes-standard (Ubuntu Xenial)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: gnome-themes-standard (Ubuntu Artful)
Status:
** Tags removed: sts-sponsor
** Tags added: sts-sponsor-slashd
** Changed in: postgresql-common (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: postgresql-common (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: postgresql-common (Ubuntu Bionic)
Importance:
Seyeong,
The SRU for LP: #1740892 is not started yet, but base on nacc's comment, It
should start soon :
https://bugs.launchpad.net/charm-hacluster/+bug/1740892/comments/47
I would suggest to wait for LP: #1740892 SRU to be completed first since
it affects package upgrade (corosync/pacemaker
** Also affects: postgresql-common (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: postgresql-common (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: postgresql-common (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You
** Also affects: gnome-themes-standard (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: unity-control-center (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: gnome-themes-standard (Ubuntu Bionic)
Importance: Undecided
Status: New
Seyeong/ddstreet,
As long as this critical bug (LP: #1740892) affecting corosync/pacemaker
relation is not fix, I would be reluctant to sponsor this bug for the
following reasons :
- To make sure it won't block potential pacemaker sru to fix this critical bug
by start this one here.
- To make
** Also affects: unity-control-center (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1644662
Title:
Icons
Public bug reported:
# gnome-disk-utility3.26.2-0ubuntu1 (Proposed)
Bionic gnome-disk-utility is expecting a Build-Depends version for
libudisks2-dev higher than what Ubuntu currently has in the archive.
#amd64/buildlog
** Tags removed: sts sts-sponsor-slashd-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1729910
Title:
lp ignores ~/.cups/lpoptions in 17.10
Status in cups package in Ubuntu:
Fix
1 - 100 of 136 matches
Mail list logo
