Fix Released. This crash stopped happening around 17.04.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => 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/1584961
Title:
Hello,
Yes, I confirm that the problem still occurs, but randomly.
Under Ubuntu 16.04 LTS up to date and Calibre 3.29 in any case.
I just upgraded Calibre version 3.30 at the moment, so I do not have
enough perspective for it.
Of course, I would like this concern to be solved, because when the
Fix Released. This crash stopped happening after 16.04 ...
https://errors.ubuntu.com/problem/d52c455f2b5e1b73719feb542e0f73b0dd9cdcec
** Changed in: xorg-server (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks Trent for the extra verification.
Tests also look good so far, but currently since a lot got uploaded due to
feature freeze some tests take a while.
We should have that in cosmic soon and then can pick the same for Bionic.
Thanks also for your thoughts on a better long term solution.
--
In reply to #105
Have tested reverting that fix and it just re-introduces the bug
"After locking screen there is no input field to type password for unlock"
Having no input field is worse.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks Hans for the pre-triage!
@Lukas - I have seen a few cases when booting from size-minimized images
that even if the universe repository is enabled there never was an "apt
update" run (The data packed into the image would be stale anyway, so
there is no reason to bloat it), and therefore no
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788752
Title:
linux-gcp: 4.15.0-1019.20 -proposed tracker
To
Sometimes the empty list is only shown, but if to agree with
installation, then something is installed. This time linux-kernel came
and the upgrades size was about 60 MB. Before this time the attempt to
install invisible updates did not lead to anything
--
You received this bug notification
Hi Alexey,
I agree - I can reproduce the error and see just the same.
Bionic - reload hangs and then fails, eventually the service is fully restarted
due to the kill after timeout
Cosmic - working fine and reports:
The logs contain a few unrelated warnings as I run it in a container, but one
Default Comment by Bridge
** Attachment added: "console log"
https://bugs.launchpad.net/bugs/1788782/+attachment/5180079/+files/Bug_fadump_dlpar_mem_add_remove.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Default Comment by Bridge
** Attachment added: "console log"
https://bugs.launchpad.net/bugs/1788782/+attachment/5180081/+files/Bug_fadump_dlpar_mem_add_remove_2.txt
** Changed in: ubuntu
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Package
Public bug reported:
== Comment: #0 - PAVITHRA R. PRAKASH - 2017-07-25
06:18:00 ==
---Problem Description---
Ubuntu 16.04.03: Fadump fails when dump is triggered after dlpar
operation. Machine keeps rebooting with oops message even after reboot.
---Environment--
Kernel Build: Ubuntu 16.04.03
Default Comment by Bridge
** Attachment added: "sosreport"
https://bugs.launchpad.net/bugs/1788782/+attachment/5180080/+files/sosreport-tuleta4u-lp9-20170725061730.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I agree with the sentiment that 5 seconds feels too long, however as a
workaround I decided I would just copy the existing timeout. I certainly
would not want to make it longer since this is in the critical boot
path.
I would generally agree that in general a DNS request should fail faster
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.15.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team)
Public bug reported:
I installed ubuntu and grub won't load. I even tried installing ubuntu
on a flash drive so that when I make my bios boot loader show up my
computer will be forced to load ubuntu cause of course that's all the
flash drive contains. Also my computer boots from the live cd
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788750
Title:
linux-aws: 4.15.0-1021.21 -proposed tracker
To
** Summary changed:
- linux-gcp: -proposed tracker
+ linux-gcp: 4.15.0-1019.20 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team)
Public bug reported:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Codename: xenial
installed https://github.com/ValveSoftware/Proton/
git clone https://github.com/ValveSoftware/Proton.git proton
cd
An upload of ubiquity to bionic-proposed has been rejected from the
upload queue for the following reason: "should be re-uploaded with
console-setup 1.178ubuntu2.7".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
An upload of ubiquity to bionic-proposed has been rejected from the
upload queue for the following reason: "should be re-uploaded with
console-setup 1.178ubuntu2.7".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this should be closed due to the time involved, and 10.04/12.04
no longer being maintained.
How can this be closed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010625
Title:
named logs
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.15.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team)
To be fair, it's also possible that I did something like the following
in my previous test container and forgot about it. ;-)
cat << EOF > maas.xml
maas
EOF
virsh net-define maas.xml
rm maas.xml
virsh net-start maas
virsh net-autostart maas
--
You received this bug notification
$sudo apt-get install schroot
$schroot -c test
terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_create_c_locale name not valid
$export LC_ALL=C
$schroot -c test
W: No chroots are defined in '/etc/schroot/schroot.conf' or
'/etc/schroot/chroot.d'
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788744
Title:
linux: 4.15.0-34.37 -proposed tracker
To manage
** Description changed:
According to Samba4 documentation, there is a vfs module that is
supposed to work hand in hand with zfs, called zfsacl. The documentation
for this (for 4.7.6) can be found listed here:
https://www.samba.org/samba/docs/4.7/man-html/vfs_zfsacl.8.html
However,
** Summary changed:
- linux: -proposed tracker
+ linux: 4.15.0-34.37 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) =>
** 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/1788777
Title:
package libavutil55 7:3.4.2-2 failed to install/upgrade: dpkg-deb
--fsys-tarfile subprocess
Public bug reported:
package libavutil55 7:3.4.2-2 failed to install/upgrade: dpkg-deb
--fsys-tarfile subprocess returned error exit status 2
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libavutil55 7:3.4.2-2
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux
Public bug reported:
According to Samba4 documentation, there is a vfs module that is
supposed to work hand in hand with zfs, called zfsacl. The documentation
for this (for 4.7.6) can be found listed here:
https://www.samba.org/samba/docs/4.7/man-html/vfs_zfsacl.8.html
However, when attempting
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Nothing has changed regarding privileged vs. unprivileged settings.
I just set this up again with a privileged container, and I believe the
cause of the regression to actually be in libvirt. I think it must have
silently ignored the bridge configuration error before and marked the
network active
[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: 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/1778368
Title:
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The issue still exits on Debian 9
Please help, thanks so much
** Attachment added: "Screenshot at 2018-08-24 11-17-00.png"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1629632/+attachment/5180073/+files/Screenshot%20at%202018-08-24%2011-17-00.png
--
You received this bug
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+
+ backports: bug 1788767
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Can you try 4.15.0-33 in -proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788583
Title:
Cannot resume HP ProBook 470 G4 after suspending or hibernating
To manage notifications about this
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
I had (I think, I can't quite remember) the filesystem.squashfs from a
live server ISO mounted when the kernel was updated. A menu entry for
this OS-resembling device is now in my grub.cfg:
menuentry 'Ubuntu 18.04.1 LTS (18.04) (on /dev/loop35p1)' --class ubuntu
--class
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1788767 (linux-aws), bug
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+
+ backports: bug 1788754
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1788765
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
** Affects:
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-precise
** Tags removed: block-proposed
--
You received this bug notification because
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
3.13.0-157.207~precise1 - generic
Regression test CMPL, RTB.
27 / 28 tests were run, missing: ubuntu_boot
Issue to note in amd64:
ubuntu_qrt_kernel_security - CONFIG_RETPOLINE=y in kernel (bug 1786894)
26 / 27 tests were run, missing: ubuntu_boot
Issue to note in i386:
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725826
Title:
rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
To manage notifications about this bug go to:
Ubuntu does enable unprivileged userns by default (at least on desktop
installs?), but there's at least one exception to watch out for: the
lightdm "guest session" option applies an AppArmor policy that allows
CLONE_NEWUSER but denies any use of the resulting capabilities; see also
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
*** This bug is a duplicate of bug 1725826 ***
https://bugs.launchpad.net/bugs/1725826
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 #1725826, so is being marked as such.
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
This bug was fixed in the package fscrypt - 0.2.2-0ubuntu2.1
---
fscrypt (0.2.2-0ubuntu2.1) bionic-security; urgency=medium
* SECURITY UPDATE: Privilege escalation via improperly restored
supplementary groups in libpam-fscrypt (LP: #1787548)
- CVE-2018-6558.patch: Save the
Tested working! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about
** Information type changed from Private Security to Public
** Package changed: gdm3 (Ubuntu) => ubuntu-release-upgrader (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788740
Title:
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781895
Title:
Bluetooth: Redpine: Bionics: L2test transfer is
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: kernel-sru-workflow
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782070
Title:
[Redpine] Upgrades to improve throughput and
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788742
Title:
linux: -proposed tracker
To manage notifications about this bug go to:
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787544
Title:
linux-oem: 4.15.0-1017.20 -proposed tracker
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: linux (Ubuntu)
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: linux (Ubuntu)
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
@mpontillo Bionic has always suffered from this bug. The patch set has
only been backport to Cosmic and the fixes have not yet been backported
to Bionic.
Have you, by chance, recently reconfigured your container to be an
unprivileged container when it was previously a privileged container? (I
Next, please remove all extensions and see if the problem persists after
that:
b'org.gnome.shell' b'enabled-extensions' b"['dash-to-
d...@micxgx.gmail.com', 'refresh-w...@kgshank.net', 'user-theme@gnome-
shell-extensions.gcampax.github.com', 'workspace-
g...@mathematical.coffee.gmail.com',
Were you maybe using a privileged container before? Those aren't
affected by the /sys ownership issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784501
Title:
libvirtd is unable to configure
I don't think you need to worry about #3 if you're using cosmic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788691
Title:
[Cosmic] gnome-shell crashes when windows key pressed
To manage
@raphael-fáistonpc: I have been having this and other GDM3 related
issues hitting the laptops I administer and its a showstopper here, too.
My current "solution" has been to give up on GDM3 and just 'sudo apt
install lightdm'. Perhaps that will let your robotics team get back to
work without
This seems to be a regression on bionic; I have been using libvirtd
inside a container for several weeks; today when I tore down and rebuilt
the container I hit this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In bug 994921 it suggests commenting out line 23 of
/etc/apport/crashdb.conf. However the crashdb.conf file on my Cosmic
system does not have a line containing 'poblem_types'.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you
** Changed in: linux (Ubuntu Bionic)
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/1786352
Title:
Bionic update: upstream stable patchset 2018-08-09
To
1. No crash files i /var/crash.
2. Nothing recent at https://errors.ubuntu.com.
3. Will give this a try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788691
Title:
[Cosmic] gnome-shell crashes
*** This bug is a duplicate of bug 1698270 ***
https://bugs.launchpad.net/bugs/1698270
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 1698270, so it is being marked as such. Please
Public bug reported:
This started the same day I did the upgrade from 16.04LTS to 18.04LTS.
Package/system information below:
lsb_release -crid
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
apt-cache policy gdm3
gdm3:
Installed:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
That's a good point, so "Won't Fix" is an accurate answer.
** Tags added: xenial
** Changed in: gnome-session (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1788592 ***
https://bugs.launchpad.net/bugs/1788592
** This bug has been marked a duplicate of bug 1788592
ubuntu-session should recommend gnome-initial-setup and ubuntu-report
--
You received this bug notification because you are a member of Ubuntu
If you have a crash file then please always use 'ubuntu-bug' to send it:
ubuntu-bug _usr_bin_gnome-shell.1000.crash
That will create a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's dmesg with 4.15.0-30-generic #33~lp1783906DEBUG running for 10 mins:
https://paste.ubuntu.com/p/Qc9Kpb62ch/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783906
Title:
Linux 4.15 and
Not strictly related to the original issue, but I just went through the
included abstractions, and someone more familiar with akonadi will
easily spot opportunities for additional restrictions. For example I
would be surprised if mysqld needs netlink or the net_bind_service
capability, which leak
1 - 100 of 871 matches
Mail list logo
