Any idea when Focal will be completed ?
Regards,
Eric
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcard pam config needs to be updated for Ubuntu and instal
(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 Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcard pam config needs to be updated
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 Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcard pam config ne
I unfortunately don't have a smartcard device handy to test/debug/
but if I compare with RHEL which is known to be working...
Redhat has the following configuration "gdm-smarcard" which includes
"smartcard-auth", a symlink pointing to "smartcard-auth-local"
I think we should 'mimic' this (at
# git clone https://gitlab.gnome.org/GNOME/gdm.git
# find . -name "gdm-smartcard*"
./data/pam-arch/gdm-smartcard.pam
./data/pam-redhat/gdm-smartcard.pam
./data/pam-exherbo/gdm-smartcard.pam
./data/pam-lfs/gdm-smartcard.pam
It seems like Ubuntu/Debian will have to start by having a 'compatible'
PA
** 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
** Changed in: gdm3 (Ubuntu Groovy)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcard pam config needs to be updated for Ubuntu
It has been brought to my attention by a UA customer that they are
suffering from which seems a similar situation:
"
Our only currently working SmartCard access from Linux, over SSSD, to AD, is on
RHEL7.
I was able to get SSH access on Ubuntu 20.04LTS, after adding
"ad_gpo_access_control = permi
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgf
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 Ubuntu
Desktop Bugs, which is subscribe
Todd, The fix will land in the next kernel cycle.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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
To man
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 wh
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 testin
** 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 wh
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 Ubuntu
Desktop Bu
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.ne
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 y
** 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 t
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
anyw
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 Ubuntu
Desktop Bugs, 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 t
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 seems
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 r
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 f
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 change
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but ins
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
b8d
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login scr
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 wh
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 bu
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://
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/904efd9e3f4c8f288
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
904efd9e3f4c8f288b1279a316eed8e177190c8f doesn't.
So the kernel bisection is completed and found the right good commit
which is:
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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] dr
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but i
"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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmw
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 r
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen ne
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 --o
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 ar
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
C
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
*** 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 :
comm
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 Ubu
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 140bcaa23a1c37b694910424075a15e00
my bug report :
https://bugs.launchpad.net/bugs/1832903
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but setting WaylandEnable=
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 test
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
https://launchpad.net/ubuntu/+source/gdm3/+publishinghistory
Deleted Bionic proposedmaingnome 3.28.3-0ubuntu18.04.5
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1817738
@vicamo,
Seems like you are experiencing the same problem as I experience when being on
VT-1.
Which was part of the reason why we SRU'd this change to avoid gmd3 to use VT-1
by default.
The problem can't be reproduce using other VT.
Seems like something acquires VT-1 (systemd ? gdm3 ?) and prev
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1637988
Title:
gvfsd-nfs not present in gvfs-backends, why?
To manage notifications about this bug go to:
https://bu
Uploaded in bionic by desktop team. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1817738
Title:
Can't change virtual terminal when auto-login is enabled
To manage notificat
Note: Desktop team kindly offered to update the vcs and do the upload in
bionic on my behalf.
Thanks !
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1)
** 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
# E
** 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
# E
** 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
# E
** 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
# E
** 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
# E
** 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
# E
** 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
# E
** 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
+ 2.
I was able to reproduce the bug, and this upstream fix[1] look
promising.
On my test machine, using a test package containing this patch on top of
current gdm3 bionic, chvt doesn't hang anymore, and work as expected.
I'd would like more feedback before I proceed with an SRU.
[1] - 39fb4ff6 manag
** 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
+ # E
** Changed in: gdm3 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: gdm3 (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: gdm3 (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1817738
Title:
Can't change virtual terminal when auto-login
$ cat /proc/5222/stack
[<0>] __vt_event_wait.isra.3.part.4+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd34/0x1150
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] ksys_ioctl+0x75/0x80
[<0>] __x64_sys_ioctl+0x1a/0x20
[<0>] do_syscall_64+0x5a/0x120
[<0>] entry_SYSCALL_64_af
# gdb attach
(gdb) bt F
#0 0x7fd01e9c65d7 in ioctl () at ../sysdeps/unix/syscall-template.S:78
No locals.
#1 0x55fbea90bce1 in main (argc=2, argv=) at chvt.c:45
fd = 3
num =
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
https://gitlab.gnome.org/GNOME/gdm/issues/466
** Description changed:
- 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.prel
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1817738
Title:
Can't change virtual terminal when auto-login is enabled
To manage notifications about th
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)
openat(
** Changed in: gdm3 (Ubuntu Xenial)
Status: New => In Progress
** Changed in: gdm3 (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: gdm3 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: gdm3 (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: gdm3 (Ubuntu Bionic)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a me
Hi Dariusz,
Before I sponsor the patch in Ubuntu, did you submitted (or at least
forwarded) the patch to gdm3 debian ?
I couldn't find a debian bug about it.
If one exist great, but if none, could you please file one against gdm3
(debian).
This will prevent gdm Ubuntu package to re-introduce th
** 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
-
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 Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs
I set both back to 'Confirmed'.
** Changed in: casper (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: systemd (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd
So all the remaining jobs are basically waiting for friendly-recovery to
exit to start due to the "oneshot" instruction, which make xnox patch
(revno 152) not working.
Some waiting jobs are units in which the desired network services in revno 152
depends on.
I totally understand why "oneshot" is
Public bug reported:
This bug has been introduced by the fix of (LP: #1682637) in Bionic.
I have notice a block in Bionic when choosing 'Enable Network' option in
recovery mode on different bionic vanilla system and I can reproduce all
the time.
I also asked colleagues to give it a try (for a se
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1755863
Title:
netbooting the bionic live CD over NFS g
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 rel
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 su
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
https://launchpadlibrarian.net/348142968/buildlog_ubuntu-bionic-amd64.gn
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718966
Title:
Cannot install snaps on Ubuntu 14
** Also affects: systemd (Ubuntu Artful)
Importance: Medium
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: N
** Also affects: open-iscsi (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: High
Assignee: Nish Aravamudan (nacc)
Status: Confirmed
*
92 matches
Mail list logo
