Launchpad has imported 8 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=100158.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
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
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
[Expired for network-manager-openvpn (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: network-manager-openvpn (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Running Gimp under Ubuntu 19.04. I used David's Batch Processor, files
were not opened yet. Unexpectedly i've got this crash message
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1723181
Title:
shotwell crashed with SIGSEGV in g_menu_model_get_n_items()
To manage notifications about this
I have regular snapshots of my ESXi virtual machines and so using a
snapshot before updating packages, I was able to install as many
packages as I could before login broke in the way everyone is
describing. I got down to the following packages:
gir1.2-mutter-2/bionic-updates
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
Eric,
I installed the 4.18 kernel on one of my Ubuntu 18.04 VMs by doing 'sudo apt
install linux-generic-hwe-18.04'
As further evidence that you may be onto something...
The system boots up fine, presents a GUI login prompt, and I am able to login
and use the system as expected (without having
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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
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
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 :
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
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 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
Public bug reported:
Every time you click on a desktop icon to do something (open it, open
the menu context, etc) the icon gets selected and the selection won't
disappear until you click elsewhere in the desktop. The behavior is
against the usual expectation that the thing gets selected just to
Public bug reported:
You should watch my video: https://photos.app.goo.gl/1TY6YWcw1UZEwKfNA
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.1
ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
Public bug reported:
Details in my video: https://photos.app.goo.gl/rNfzi9W4WJPbVc329
///Add
I won't see this bug, if other windows is appeared.
I want to compliment Ubuntu developers. Firefox have worked excellent after few
updates. Gno-menu animation become more beautiful. But I see sticking
Hi Daniel,
Sorry for the delay.
As requested, I reproduced the bug.
- I SSH'd into the VM
- /var/crash was empty
- 'pidof gnome-shell' returned a pid of 1423
- I ran 'sudo kill -ABRT 1423'
- two crash reports/files appeared in /var/crash
-rw-r- 1 gdm whoopsie 20574823 Jun 15 06:12
20 matches
Mail list logo
