@Maarten: Maybe spotify will install and work from its flatpak? It's the
second flatpak app listed here: https://www.omgubuntu.co.uk/2017/07/7
-flatpak-apps-can-install-right-now-flathub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
== Comment: #0 - JENIFER HOPPER - 2018-03-14 16:20:47 ==
+++ This bug was initially created as a clone of Bug #163375 +++
---Problem Description---
All KVM guest cpu utilization is being reported as sys% time in the host.
It turns out Guest time
--- Comment From shriy...@in.ibm.com 2018-03-15 01:00 EDT---
Updating for reference :
===
Also verified on bionic kernel : 4.15.0-10-generic #11-Ubuntu
and Perf version is : perf version 4.15.3
root@ltc-boston122:~# perf list | grep pm_
power:dev_pm_qos_add_request
** Summary changed:
- linux-lts-xenial: -proposed tracker
+ linux-lts-xenial: 4.4.0-117.141 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790
** This bug has been marked a duplicate of bug 545790
package PACKAGE failed to install/upgrade: error writing to '': Success
--
You received this bug notification because you are a member of Ubuntu
I fixed this in qa-r-t differently, I'd prefer to know the exact config used in
each kernel version:
https://git.launchpad.net/qa-regression-testing/commit/?id=9ea99cecf8f023478c64d3e66b88dbba24738649
Closing. Thanks for the report!
** Changed in: linux (Ubuntu)
Status: Triaged =>
*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790
** This bug has been marked a duplicate of bug 545790
package PACKAGE failed to install/upgrade: error writing to '': Success
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790
** This bug has been marked a duplicate of bug 545790
package PACKAGE failed to install/upgrade: error writing to '': Success
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "StacktraceSource.txt"
https://bugs.launchpad.net/bugs/1755974/+attachment/5079979/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755974
Title:
StacktraceTop:
gvdb_table_new (filename=filename@entry=0x7f00d0026790
"/home/karma/.cache/tracker/ontologies.gvdb", trusted=trusted@entry=1,
error=error@entry=0x7f00d8477ab0) at gvdb-reader.c:166
tracker_ontologies_load_gvdb (filename=filename@entry=0x7f00d0026790
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1755974/+attachment/5079980/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1755974/+attachment/5079968/+files/CoreDump.gz
** Changed in: gjs (Ubuntu)
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1755974/+attachment/5079978/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755974
Title:
gjs-console
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742318
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
this is an automated bug report.
$ lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gjs 1.51.91-1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1755970
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a
very bad inconsistent state; you should reinstall it before attempting
configuration
I have reinstalled it but getting same error every time I tried to install any
package.
ProblemType: Package
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755973
Title:
package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package
is in a very bad
Upstream:
https://gitlab.gnome.org/GNOME/mutter/issues/69
** Summary changed:
-
/usr/bin/gnome-shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured:_gdk_x11_display_error_event
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_writer_default() from
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.26.2-0ubuntu3, the problem page at
https://errors.ubuntu.com/problem/df612c581e95e649eeea7cceb17eb7551ff961c6
contains
Public bug reported:
I'm using Xubuntu 18.04, the iso uploaded at 2:19 UTC, 15/3/2018(as of
posting, the latest release), running in Virtualbox 5.28 host on a newly
installed Xubuntu 18.04 system using the Beta 1 ISO.
I was running through the QA testing for a new install, and got to the
point
same issue with kubuntu-18.04-beta1-desktop-amd64.iso.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755968
Title:
Failed to install ubuntu 18.04 desktop 64bit latest daily build image
in ESXi.
Public bug reported:
Failed to install ubuntu 18.04 desktop 64bit latest daily build image in
ESXi. It seems like installer crash at the starting point.
Error message is below:
[ ***] S start job is running for Ubuntu live CD installer (2min 9s / no limit)
dbus-daemon[754]: [session uid=999
Thanks.
It looks like your issues might be caused by these unsupported package
versions you have installed:
ii libavcodec-extra 7:3.3.3-2~ubuntu16.04.1~ppa1
all FFmpeg library with extra codecs
(metapackage)
ii
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755473
Title:
Some strings of Ubuntu Dock settings are not
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
With the test triggered yesterday on the same box, the system has passed with
the enosys test:
12:33:56 DEBUG| [stdout] enosys STARTING
12:34:01 DEBUG| [stdout] enosys RETURNED 0
Also the file-ioctl test:
12:34:41 DEBUG| [stdout] file-ioctl STARTING
12:34:46 DEBUG| [stdout] file-ioctl
This bug was fixed in the package stress-ng - 0.09.20-1
---
stress-ng (0.09.20-1) unstable; urgency=medium
* Makefile: bump version
* stress-procfs: remove debug (LP: #172)
* stress-madvise: fix build issue for HPPA (LP: #171)
* stress-dev: add missing FIBMAP to block
This bug was fixed in the package stress-ng - 0.09.20-1
---
stress-ng (0.09.20-1) unstable; urgency=medium
* Makefile: bump version
* stress-procfs: remove debug (LP: #172)
* stress-madvise: fix build issue for HPPA (LP: #171)
* stress-dev: add missing FIBMAP to block
I have updated Bug #1661869 with an SRU template and new updates to fix
this issue, plus the issue in that bug.
The fix is simply to update /etc/avahi/avahi-daemon.conf and comment out
the entire [rlimits] section. You can do this yourself (but the package
update will do it for you).
It'd be
Trusty is technically not directly affected by the container proc issue
as there was an Ubuntu patch dropped in xenial to skip setting rlimit-
nproc when /run/container_type=lxc
Could happen if that doesn't exist though, and the memory issue can
still occur, so still recommend upload.
**
** Patch added: "lp1661869-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661869/+attachment/5079950/+files/lp1661869-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1661869-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661869/+attachment/5079949/+files/lp1661869-artful.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1661869-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661869/+attachment/5079951/+files/lp1661869-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
*** This bug is a duplicate of bug 1754059 ***
https://bugs.launchpad.net/bugs/1754059
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP:
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
*
** Changed in: openafs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364544
Title:
Openafs Not Building on arm64
To manage notifications about this bug go
This bug was fixed in the package debian-installer - 20101020ubuntu534
---
debian-installer (20101020ubuntu534) bionic; urgency=medium
* Move master kernels to 4.15.0-12. LP: #1754059
-- Dimitri John Ledkov Thu, 15 Mar 2018 00:14:05
+
** Changed in:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755652
Title:
Martin,
Can you please reproduce the problem with Wayland and then:
journalctl -b0 > todays-journal.txt
and attach the resulting file here?
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: gnome-control-center (Ubuntu)
Status: New => Invalid
** Changed in: gnome-bluetooth (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can't see any sql messages in my log on 18.04. And I can't see any sql
use in the source code of either gnome-shell or mutter.
Are you using any non-standard extensions with gnome-shell?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug
Please do this:
1. Apply the workaround from bug 994921.
2. Reproduce the crash.
3. Look in /var/crash for new files, and if found run:
ubuntu-bug /var/crash/YOURFILE.crash.
4. When the new bug is created, let us know here what that bug ID is.
** Changed in: gnome-shell (Ubuntu)
*** This bug is a duplicate of bug 1691701 ***
https://bugs.launchpad.net/bugs/1691701
** This bug has been marked a duplicate of bug 1691701
gnome-shell crashed with SIGTRAP in XSync() from meta_pre_paint_func() from
_clutter_run_repaint_functions() from master_clock_update_stages() from
Please find attached a debdiff applying the upstream patch and necessary
packaging adjustments. While this is expected in the next upstream
release, that is not expected to happen in time for bionic, making this
change useful to adopt in advance of Debian, but only for release
scheduling reasons
171d8b9363725e122b164e6b9ef2acf2f751e387 looks good. The next test is
with 4681ee21d62cfed4364e09ec50ee8e88185dd628.
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12.0-041200rc1 #201803141333 - relatively good (1 of 217 -
See also bug 1755779.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691701
Title:
gnome-shell crashed with SIGTRAP in XSync() from meta_pre_paint_func()
from _clutter_run_repaint_functions()
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691701
Title:
** Description changed:
+ https://gitlab.gnome.org/GNOME/mutter/issues/68
+
+ ---
+
Frequently, but not always, the mouse cursor is invisible in the login
screen. I can move it, as when passing over a button it lights up, but I
can't see where the cursor is.
Once on the desktop, the
Looks like bug 1691701. Only the stack trace changed a little in 18.04
so we have this new bug.
** Information type changed from Private to Public
** Summary changed:
- gnome-shell crashed with signal 5
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_writer_default() from
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755302
Title:
Ubuntu 17.10 freezes randomly
To manage
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755576
Title:
package base-files 9.4ubuntu4.6 failed to install/upgrade: package
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755562
Title:
package libwinpr-sspi0.1:amd64
Upstream bug report:
https://gitlab.gnome.org/GNOME/mutter/issues/70
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754949
Title:
gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
The crash occurs on this line of code:
g_warning ("Failed to set CRTC mode %s: %m",
crtc->current_mode->name);
As crtc is not NULL it must be current_mode or name that has an invalid
value.
** Tags added: wayland wayland-session
** Description changed:
+
** Description changed:
- The bug, and workaround, are clearly described in this mailing list
- thread:
+ [Original Description]
+ The bug, and workaround, are clearly described in this mailing list thread:
https://lists.linuxcontainers.org/pipermail/lxc-
users/2016-January/010791.html
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755562
Title:
package libwinpr-sspi0.1:amd64
1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to
** Changed in: cheese
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710370
Title:
Cheese crashes on launch in Ubuntu 17.10 if no camera device is
present
To
I wonder if this is related:
mars 13 10:33:52 hostname gnome-software[2180]: Creating pipes for
GWakeup: Too many open files
Thanks
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: subversion (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525373
Title:
libsvn-java.postinst
To manage notifications about this bug
Hello, your logs show more errors than I'm accustomed to seeing;
consider running fwts or fwts-frontend, or looking for firmware updates
from your system vendor.
Thanks
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of
This bug is about the Firefox case only now.
If you have any other problems then please open a new bug.
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Changed in: firefox (Ubuntu)
Status: New => Fix Released
** Changed in: gnome-shell (Ubuntu)
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755193
Title:
package mariadb-server-10.0 10.0.34-0ubuntu0.16.04.1 failed to
*** This bug is a duplicate of bug 1754791 ***
https://bugs.launchpad.net/bugs/1754791
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 #1754791, so is being marked as such.
1 - 100 of 720 matches
Mail list logo