** Changed in: mesa (Ubuntu Bionic)
Importance: Medium => High
--
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/1753776
Title:
Graphics corruption just before login animation to
*** This bug is a duplicate of bug 1672297 ***
https://bugs.launchpad.net/bugs/1672297
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1672297, so it is being marked as such. Please
Public bug reported:
Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.
Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get
- Why did this not fail the build?
Because then the build wouldn't work! I mentioned this in the MIR
description under Quality Assurance.
- Why did this fail?
I don't know. Once we know how to get the tests to pass, I'll be happy
to make test failures fail the build. (Currently, they're ignored
With this commit, I now get this error:
"Error creating passphrase-encrypted packet: GPGME: Bad passphrase"
https://salsa.debian.org/utopia-team/volume-key/commit/42207b3d
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to volume-key
I mean this part of the log seems like it's obviously not going to work.
---
To begin, type keys on the keyboard until this progress meter
is full. DO NOT USE THE AUTOREPEAT FUNCTION ON YOUR KEYBOARD!
Continue typing until the
I'm not sure but this seems to suggest "yes" (?):
https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS
--
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/1756877
Title:
Input latency in
Thanks, but that's not a usable log. Please try this:
dmesg | grep -v apparmor > kernel.txt
--
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/1756092
Title:
Screen freeze for some time
We know Wayland sessions in Gnome Shell have a lot of performance
problems. And that's one of the reasons why we default to, and recommend
Xorg sessions.
** Summary changed:
- Minecraft makes Ubuntu GNOME extremely slow
+ Minecraft makes Ubuntu GNOME extremely slow (in Wayland sessions only)
**
Alex,
You shouldn't ever have to run synclient manually again. See comment
#36:
"Once you know the synclient syntax you want you can apply it
automatically at login by running 'gnome-session-properties'."
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I think the question is whether the lid problem occurs _after_ cold
boots or warm boots only.
A cold boot is from power-on. A warm boot is a reboot.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
This bug was fixed in the package update-manager - 1:18.04.9
---
update-manager (1:18.04.9) bionic; urgency=medium
* Keep PEP 8 checks happy
-- Balint Reczey Wed, 21 Mar 2018 17:53:59 +
** Changed in: update-manager (Ubuntu)
Status: In Progress
I have the same error, only when I click on the shutdown icon. A command
line shutdown does not get this error. I am running Mint 18.3 on oracle
virtualbox.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
The tests run during the build failed on my machine yet the build did
not fail:
Error creating passphrase-encrypted packet: Unknown error getting encryption
result
FAIL tests/packet_roundtrips.sh (exit status: 1)
** No longer affects: adwaita-qt (Ubuntu)
** No longer affects: akonadi4 (Ubuntu)
** No longer affects: alsoft-conf (Ubuntu)
** No longer affects: alt-key (Ubuntu)
** No longer affects: amarok (Ubuntu)
** No longer affects: amora-server (Ubuntu)
** No longer affects: ams (Ubuntu)
** No
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-software. This problem was most recently seen with package version
3.22.7-0ubuntu3.17.04.8, the problem page at
https://errors.ubuntu.com/problem/93062809d69f17048a0a09102f1367ce115b437e
I posted the bug 3 years ago in 2015 and yesterday the bug expired
because nobody saw it, what a irony
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
** Changed in: canonical-devices-system-image
Assignee: HECTOR DAVID (hektve) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1567250
Title:
ssh signin
Nobody notice this bug so far and after 3 years I posted it:
https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-
it-might-not-be-fixed-for-ubuntu-18-04-lts
** Changed in: gnome-shell (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because
The irony on all this is that the bug expired the same day that
omgubuntu posted this news
--
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/1423773
Title:
Gnome-Shell don't free
*** This bug is a duplicate of bug 1570938 ***
https://bugs.launchpad.net/bugs/1570938
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 #1570938, so is being marked as such.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1720224
Title:
cannot arrange the
Bug confirmed as fixed with file-roller 3.28.0-1ubuntu1
Marking as Fix Released
** Changed in: file-roller (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
Public bug reported:
This occurred after running do-release-upgrade on Ubuntu 16.04 on the
Linux Subsystem Windows. After the upgrade has failed, there are now
dependency problems with udev and libudev1, but I do not know whether
these are connected.
ProblemType: Package
DistroRelease: Ubuntu
Attached a dmesg right after the issue occurred
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5086281/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
Ubuntu on Xorg works great, just like Unity. No performance problems
there.
--
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/1751653
Title:
Minecraft makes Ubuntu GNOME
** Branch linked: lp:~3v1n0/ubuntu-themes/list-theming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1757471
Title:
Remove local theme changes
To manage
** Package changed: nautilus (Ubuntu) => gnome-control-center (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1757471
Title:
Remove local theme changes
To
*** 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.
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/25
Upstream MR:
https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/15
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
Public bug reported:
To reproduce:
1. Remove an online account
2. Close the window (without waiting for the notification to be dismissed)
3. Start g-c-c again
4. Open the online-account panel
Current behavior:
The account has NOT been removed.
Expected result:
The account has been removed.
**
Using this patch:
diff --git a/test/gvfs-test b/test/gvfs-test
index 4537d8a5..c82e13a8 100755
--- a/test/gvfs-test
+++ b/test/gvfs-test
@@ -278,7 +278,7 @@ class GvfsTestCase(unittest.TestCase):
ml = GLib.MainLoop()
-mount.unmount_with_operation(Gio.MountUnmountFlags.NONE,
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
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/1708409
Title:
kdump service does not start after
** Changed in: gnome-control-center
Status: Unknown => Confirmed
** Changed in: gnome-control-center
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell
(Ubuntu)
--
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/1757298
Title:
GNOME Shell is consuming most of
The attachment "gnome-control-center-remove-white-lists.patch" 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,
You have been subscribed to a public bug:
gnome shell is consuming most of my laptop's memory, i.e. ~700 MB / 3.8 GB.
Currently using Ubuntu 17.10 >> Artful Aardvark.
RAM consumption is pretty high even if you compare it to Chrome, having 5 tabs
open and running simultaneously.
Please solve
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)
** Bug watch added: GNOME Bug Tracker #780167
https://bugzilla.gnome.org/show_bug.cgi?id=780167
** Also affects: gnome-control-center via
https://bugzilla.gnome.org/show_bug.cgi?id=780167
Importance: Unknown
You have been subscribed to a public bug:
Hi
If I activate the Night Light mode with an external monitor connected,
the mode is only on the external monitor activated.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic
Public bug reported:
Remove temporary patch for theme changes
** Affects: nautilus (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Tags: patch
--
You received this bug notification because you are a member of Ubuntu
Desktop
This will be handled by https://code.launchpad.net/~3v1n0/ubuntu-themes
/list-theming/+merge/341003
** Patch added: "gnome-control-center-remove-white-lists.patch"
My Lenovo logs me off when Android device plugged out from PC
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/980519
Title:
Random log off in Ubuntu 12.04 LTS
To manage
@Kai-Heng Feng, I have no idea what you mean. This issue is upon closing
and re-opening lid. It does not occur upon boots, whether "cold" or
"re".
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Much better, thanks Robert!
I think we can live with the installed snaps requests for now.
--
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/1756184
Title:
Search making
I think I've solved the mystery. I was very bothered that I was the
only/first one having it, given the ubiquity of my hardware. I believe
this theory also explains why it sometimes awoke just fine from lid
closed, but sometimes was all broken.
I believe my setting for "what to do when lid
Hi all,
I am also affected by this bug (this cannot be a feature, right?).
I was wondering what went wrong during my 17.04 to 17.10 upgrade.
Why on earth was type-ahead removed?
It makes nautilus useless for any user that make use of the keyboard.
Please, reactivate this feature.
In the
I'm trying to look at this, but LP: #1750465 is making the upgrade fail
too. I see Steve has uploaded a fix for that, so once it migrates I'll
come back to this bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-menus in
@Jeremy Bicha: In the meantime Firefox wayland support has arrived
(still not enabled by default. callable with --enable-default-toolkit
=cairo-gtk3-wayland) and Chromium wayland ozone builds are quite stable.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
This bug was fixed in the package systemd - 229-4ubuntu21.2
---
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP
This bug was fixed in the package systemd - 229-4ubuntu21.2
---
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP
This bug was fixed in the package systemd - 229-4ubuntu21.2
---
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP
This bug was fixed in the package systemd - 229-4ubuntu21.2
---
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP
This bug was fixed in the package systemd - 229-4ubuntu21.2
---
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP
This bug was fixed in the package systemd - 229-4ubuntu21.2
---
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP
This bug was fixed in the package systemd - 229-4ubuntu21.2
---
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP
This bug was fixed in the package systemd - 229-4ubuntu21.2
---
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix
Same problem with gtk3:
$ sudo apt install libgtk-3-dev:amd64 libgtk-3-dev:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
libgtk-3-dev is already the newest version (3.22.28-1ubuntu3).
Some packages could not be installed. This may mean that you have
** Description changed:
Hi All,
I recently upgraded to Ubuntu 18.04 (Bionic), which contains mutter 3.28
since some days.
Now there are 2 big issues with gnome-shell and mutter on Wayland.
One of the issues is that the gdm3 greeter is black when my second external
screen is
Public bug reported:
Hi All,
I recently upgraded to Ubuntu 18.04 (Bionic), which contains mutter 3.28 since
some days.
Now there are 2 big issues with gnome-shell and mutter on Wayland.
One of the issues is that the gdm3 greeter is black when my second external
screen is connected.
Now when I
No, it was gone completely. The entire WiFi option was gone from the
menu too, you could only configure it by opening control center. That
said, have not seen it anymore recently, so closing for now. Will open
it again if it does happen again.
** Changed in: gnome-shell (Ubuntu)
Status:
Please do not assign bugs to udev source package, it has been long time
merged into systemd source package.
Yeah, I can cherry-pick this for SRUs.
** No longer affects: udev (Ubuntu)
** No longer affects: udev (Ubuntu Xenial)
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Daniel,
There is a small inconvenience with 'synclient' command - I have to run
it not just at startup, but also every time I restart gnome-shell (after
installing an extension, for example). But anyway, it looks like
libinput 1.10.2 resolved the problem with hysteresis on my touchpad, so
I can
Do I have to disable secure boot for the proprietary driver to work?
--
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/1756877
Title:
Input latency in 18.04
To manage
Gnome 3.28.0: without the overview
** Attachment added: "gnome-shell.maximized.pdf"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757088/+attachment/5085696/+files/gnome-shell.maximized.pdf
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1748450, so it is being marked as such. Please
Gnome 3.28.0: with the overview.
** Attachment added: "gnome-shell.overview.pdf"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757088/+attachment/5085697/+files/gnome-shell.overview.pdf
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Maybe a full kernel log (from dmesg) to see if USB or some other device
type is causing a hang in the kernel.
--
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/1756092
Title:
Screen
** Tags removed: need-amd64-retrace
--
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/1757362
Title:
gnome-shell crashed with signal 5
To manage notifications about this bug go
Done. Is there any more info I can provide on the original machine?
--
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/1756092
Title:
Screen freeze for some time when unlocking
To
Public bug reported:
just report bug
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
Let me reach out to xnox to see if he's planning another systemd SRU
after the current one migrates into -updates. If yes, maybe we can have
him bundle up this change. If not, we can just release this one fix
then.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
**
Without the overview.
** Attachment added: "gnome-shell.user-maximized.pdf"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757088/+attachment/5085669/+files/gnome-shell.user-maximized.pdf
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
With the overview.
** Attachment added: "gnome-shell.user-overview.pdf"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757088/+attachment/5085670/+files/gnome-shell.user-overview.pdf
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Here's a fix.
** Patch added: "mesa_18.0.0~rc4-1ubuntu4_v1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/+attachment/5085668/+files/mesa_18.0.0~rc4-1ubuntu4_v1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-calendar (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
This is on my list and will probably land next week (it needs testing,
see which context should be applied where).
Sorry, but late feature requests is taking precedence, and this is why
there is this timeline. However, I got it opened as a TODO :)
--
You received this bug notification because
** Changed in: mesa (Ubuntu Bionic)
Assignee: Timo Aaltonen (tjaalton) => Daniel van Vugt (vanvugt)
** Changed in: mesa (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1757290
Title:
gnome-control-center crashed with SIGABRT in g_assertion_message()
** Tags added: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1757290
Title:
gnome-control-center crashed with SIGABRT in g_assertion_message()
To
Public bug reported:
New with 1:3.27.92-1ubuntu1 and still exists in 3.28
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-control-center. This problem was most recently seen with package version
1:3.28.0-0ubuntu1, the problem page at
** Summary changed:
-
/usr/bin/gnome-control-center:11:g_hash_table_remove_all_nodes:g_hash_table_remove_all_nodes:g_hash_table_unref:gtk_css_node_style_cache_unref:gtk_css_node_ensure_style
+ gnome-control-center (11) g_hash_table_remove_all_nodes →
g_hash_table_remove_all_nodes →
92 matches
Mail list logo