** Changed in: gnome-software (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1806697
Title:
Status of interface
** Changed in: gnome-software (Ubuntu Disco)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1806697
Title:
Status of interface
Sounds like a fix is on the way:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/626
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #643
https://gitlab.gnome.org/GNOME/mutter/issues/643
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/643
It also sounds like VirtualBox might allow me to reproduce the bug...
** Changed in: mutter (Ubuntu Bionic)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Because it was mentioned in comment #15 & #34 that this bug cannot be
reproduced, I decided to create a VMWare VM from scratch which managed
to be affected on my first attempt.
I started with ubuntu-18.04.1-desktop-amd64.iso
(19e10acddd14af9a9150399d876b02933c0ee724) and created a snapshot with
** Changed in: mutter (Ubuntu Bionic)
Status: Won't Fix => Incomplete
--
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
** Changed in: mutter (Ubuntu Bionic)
Importance: Undecided => 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.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
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
> Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?
Technically it was a whole point release. The trigger could be any
change that went into mutter 3.28.4 as well as any Ubuntu patch. As
mentioned in comment #31, my suspicion
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: gnome-bluetooth (Ubuntu)
Status: Incomplete => Invalid
** Changed in: gnome-shell (Ubuntu)
Status:
** Also affects: gnome-software (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: gnome-software (Ubuntu Disco)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: gnome-software (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in:
Thank you for your bug report. Could you add your 'journalctl -b 0' log after
getting the issue?
When you say that the screen goes black, are you speaking about the settings
part of the session? Does it come back after a while?
** Changed in: gnome-control-center (Ubuntu)
Importance:
** Changed in: gnome-shell
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1705369
Title:
Ubuntu boots to blank screen when using Nvidia (on
Public bug reported:
Ubuntu 19.04 fresh upgrade
Hotspot was working on Elitebook 740G2 on Ubuntu 16.04
was no longer working on Ubuntu 18.04
When Wifi is enabled, I can connect to wifi router. So wifi works
When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to
Turn on or
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
This bug was fixed in the package evince - 3.28.4-0ubuntu1.2
---
evince (3.28.4-0ubuntu1.2) bionic-security; urgency=medium
* apparmor-profile: apply hardening from Ubuntu 18.10
- add preamble for expectations of the profile
- evince{-previewer}: restrict access to DBus
This bug was fixed in the package evince - 3.18.2-1ubuntu4.5
---
evince (3.18.2-1ubuntu4.5) xenial-security; urgency=medium
* apparmor-profile: apply hardening from Ubuntu 18.10
- add preamble for expectations of the profile
- evince{-previewer}: restrict access to DBus
Kai-Heng: thanks for the suggestion, bluetooth now switches on & I can
pair with devices.
Output of "dmesg | grep -i bluetooth" looks healthier too:
martin@martin-N15-17RD:~$ dmesg | grep -i bluetooth
[ 18.577708] Bluetooth: Core ver 2.22
[ 18.577724] Bluetooth: HCI device and connection
Hi Daniel & Kei-Heng, thanks for the suggestions.
rfkill doesn't do much
> martin@martin-N15-17RD:~$ rfkill unblock 0
> rfkill: invalid identifier: 0
I'll try the kernel you suggested next.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Hello Iain, or anyone else affected,
Accepted glib2.0 into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.60.4-0ubuntu0.19.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package gnome-settings-daemon -
3.32.1-1ubuntu1
---
gnome-settings-daemon (3.32.1-1ubuntu1) eoan; urgency=medium
* New upstream version
Media-keys:
- Fix MPRIS issues with disconnecting clients (lp: #1832374)
* Merge with Debian. Remaining
*** This bug is a duplicate of bug 1822195 ***
https://bugs.launchpad.net/bugs/1822195
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 #1822195, so is being marked as such.
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/3.32.1-1ubuntu1
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are
Public bug reported:
* Impact
There is a new bugfix GNOME update available with some bugs fixed, details on
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/blob/gnome-3-32/NEWS
* Test case
Log into a Ubuntu/GNOME session and make sure that the session has the
correct theme, that the
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Xiaofeng Wang (xiaofengw)
** No longer affects: evince (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
This bug was fixed in the package ibus-libpinyin -
1.11.0-1ubuntu0.18.10.1
---
ibus-libpinyin (1.11.0-1ubuntu0.18.10.1) cosmic; urgency=medium
* Backport of the disco version as an SRU in an attempt to reduce the
number of crashes (LP: #1768166).
-- Gunnar Hjalmarsson Wed,
This bug was fixed in the package libpinyin - 2.2.2-1~ubuntu18.04.1
---
libpinyin (2.2.2-1~ubuntu18.04.1) bionic; urgency=medium
* Backport of the disco version as an SRU in an attempt to reduce the
number of crashes (LP: #1768166).
-- Gunnar Hjalmarsson Mon, 22 May 2019
This bug was fixed in the package libpinyin - 2.2.2-1~ubuntu18.10.1
---
libpinyin (2.2.2-1~ubuntu18.10.1) cosmic; urgency=medium
* Backport of the disco version as an SRU in an attempt to reduce the
number of crashes (LP: #1768166).
-- Gunnar Hjalmarsson Mon, 22 May 2019
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
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rhythmbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
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
Still not fixed in latest Ubuntu release.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1764156
Title:
Make all gnome-session-properties AppStream strings translatable
To manage
Thanks for reporting it upstream, they haven't rolled out an update with
the fix yet but they will do it now
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Description changed:
Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
with an unused Intel GPU).
WORKAROUNDS (you only need one):
* Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf
* Disable integrated graphics/GPU in your BIOS
* Add
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/gdm3/+git/gdm3/+merge/369024
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1705369
Title:
** Changed in: mutter (Ubuntu)
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1705369
Title:
Ubuntu boots to blank screen when using
According to upstream, the fix is in 3.32.1 not in 3.32.0.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1832374
Title:
Media keys stop working due to missing
Oops. It appears upstream already fixed this bug. And we removed their
fix in Ubuntu (revert_nvidia_wayland_blacklist.patch in gdm3). If you
revert that revert then the bug is fixed.
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gdm3
It was clear that the sync was what I was going for (comment #1), so it
would have been nice if the SRU would have been accepted by the way.
Brian could have synced it if necessary as well. Now we have to wait for
another go-round.
--
You received this bug notification because you are a member
It's there now. The sync must have failed.
--
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/1832457
Title:
[SRU] 2.60.4
To manage notifications about this bug go to:
yanp.b...@gmail.com: Why did you reopen this task without any comment
explaining the reason? See comment 201?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1245473
Hi! I have the same issue i would like to know the solution
Castro B,
gratisdatingsite.nl
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1245473
Title:
Binding
45 matches
Mail list logo
