The best solution I've found is to uncomment the "Timed login" options
on the custom.gdm as shown here https://askubuntu.com/questions/1136457
# Enabling timed login
TimedLoginEnable = true
TimedLogin = username
TimedLoginDelay = 10
--
You received this bug notification because you are a member
Forgot to add: this is on disco with budgie* 10.5-0ubuntu1.1 and gsd
3.32.1-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759462
Title:
Keyboard shortcuts not operational on 18.04
To mana
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1837569 (bionic/li
Public bug reported:
Pacemaker is currently failing autopkgtests for Eoan. Excuses show:
pacemaker (1.1.18-2ubuntu1 to 2.0.1-4ubuntu2)
Maintainer: Ubuntu Developers
0 days old
autopkgtest for booth/1.0-162-g27f917f-2: amd64: Pass, arm64: Regression ♻ ,
armhf: Always failed, i386: Always failed,
Just to note: since one of the kernel upgrades, this issue is not
present anymore. I'm not sure which version fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773184
Title:
Starting a KVM gu
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
F
This issue is fixed in both, pacemaker and corosync. Other regressions
are being investigated at:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1838024
** Changed in: pacemaker (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a
Last autopkgtest that succeed shows:
autopkgtest [07:14:15]: test pacemaker: [---
+ sleep 60
+ crm_mon -1
+ hostname -s
+ fgrep -20 Online: [ autopkgtest ]
Stack: corosync
Current DC: autopkgtest (version 1.1.18-2b07d5c5a9) - partition WITHOUT quorum
Last updated: Tue Jul 16 07
I'll rewrite both, corosync and pacemaker simple tests, and give it a
try in new package versions. It will have more output (to debug possible
issues) and will try to wait for an event, instead of waiting for time
only.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Now that 18.10 is EOL, the upgrade path from 18.04 now points to 19.04.
I've just checked on my own 18.04 installation and I've been offered an
upgrade with the following text displayed:
"The software on this computer is up-to-date."
"However, Ubuntu 19.04 is now available (you have 18.04)."
I th
** Tags added: id-5d39d20d64e1ea1822b8d25d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837443
Title:
[Power9][Witherspoon dd2.3] unable to set hwclock
To manage notifications about this bug go t
** Summary changed:
- bionic/linux-oem-osp1: 5.0.0-1016.17 -proposed tracker
+ bionic/linux-oem-osp1: 5.0.0-1016.18 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837575
Title:
bi
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow s
Related bug:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1838024
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837064
Title:
corosync migration failed autopkgtests
To manage notifica
Related bug:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1837064
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838024
Title:
pacemaker migration failed autopkgtests
To manage notifica
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(o
Ok, sorry, I see the description of your problem now. It was mixed in
with the automatically collected information, so I missed it initially.
However I still don't really see anything in the logs to explain the
symptoms you're reporting. Could you check the /var/log/kern.log* files
and see if you
** Changed in: kernel-sru-workflow/promote-to-proposed
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/1837613
Title:
bionic/linux-kvm: 4.15.0-1040.40 -prop
He means that you are running a kernel from eoan-proposed, despite your
saying that you do not have updates from the -proposed pocket enabled.
This report contains no useful information about the crash you are
seeing. I see no indication of a kernel panic or anything like that in
the logs, despite
Hi Hari, thanks for clarifying! I can now understand, seems we need to
wait for Cascardo's input, to see if he already implemented the systemd
reset-failed thing or not.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
Massimeddu: The fix is already in progress and waiting for the SRU team
to ack the change before it can go to proposed repository
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834583
Title:
[eoan][
Installing go using `snap install go --classic` installs go version
1.12.7
Probably it is better do use snap here and drop the go provided by apt
completely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Possibly relevant code in chromium: ui/base/cursor/cursor_loader_x11.cc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838008
Title:
[snap] cursor theme isn't respected
To manage notifications abou
See also bug #1838008.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833611
Title:
[snap] mouse pointer on Ubuntu flavours is retro-looking when hovering
over links
To manage notifications about
Public bug reported:
`journalctl` is a common interface on to a system's logs, and it would
be good if I could use journalctl to access cloud-init's logs in the
same way I do all(/most) other units running on the system.
(This is particularly desirable when trying to line up cloud-init's logs
wit
See also bug #1833611.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838008
Title:
[snap] cursor theme isn't respected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
*** This bug is a duplicate of bug 1837575 ***
https://bugs.launchpad.net/bugs/1837575
** This bug has been marked a duplicate of bug 1837575
bionic/linux-oem-osp1: 5.0.0-1016.18 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
*** This bug is a duplicate of bug 1837593 ***
https://bugs.launchpad.net/bugs/1837593
** This bug has been marked a duplicate of bug 1837593
bionic/linux-oem: 4.15.0-1048.55 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
*** This bug is a duplicate of bug 1837593 ***
https://bugs.launchpad.net/bugs/1837593
** This bug is no longer a duplicate of bug 1836172
bionic/linux-oem: 4.15.0-1047.52 -proposed tracker
** This bug has been marked a duplicate of bug 1837593
bionic/linux-oem: 4.15.0-1048.55 -proposed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
F
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(o
*** This bug is a duplicate of bug 1837593 ***
https://bugs.launchpad.net/bugs/1837593
** Summary changed:
- linux-oem: 4.15.0-1046.51 -proposed tracker
+ bionic/linux-oem: 4.15.0-1046.51 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Incomplete => New
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Andy Whitcroft (apw) => Ubuntu Stable Release Updates Team
(ubuntu-sru)
--
You received this bug notification because you are a member of
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
Thanks for the report. I can add the module to the udebs, unless it
makes more sense to just make it built-in.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notificatio
** This bug is no longer a duplicate of bug 1837575
bionic/linux-oem-osp1: 5.0.0-1016.18 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836856
Title:
bionic/linux-oem-osp1: 5.0.
Please also test with the default 19.04 kernel (ideally the installer,
too), can you get graphical output there using amdgpu.dc=0 ?
While running from the installed system, if possible using the default (after
updates) kernel image, with amdgpu.dc=0 set, please run:
apport collect-logs 1837945
What do I need to do? Should I write to HP support?
пт, 26 июл. 2019 г., 14:29 Artyom Pozharov :
> I have been completing all needing actions (install Windows 10, update
> UEFI-BIOS to F52 version), but problem with grub-installer also repeats. I
> even create an apport with refresh information.
I think the question is; why don't we log to syslog by default. I think
historically cloud-init is run in many OSes which may or maynot have
syslog capabilities so it defaults to writing it's own log directly.
At least for local testing, it's easy enough to update
/etc/cloud/cloud.d/05_logging.cf
** Summary changed:
- cloud-init should emit its logs to the systemd journal
+ cloud-init should emit all of its logs to the systemd journal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838032
Titl
** Description changed:
`journalctl` is a common interface on to a system's logs, and it would
be good if I could use journalctl to access cloud-init's logs in the
- same way I do all(/most) other units running on the system.
+ same way I do all(/most) other units running on the system. As th
The solution in #4 worked for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786822
Title:
Pinta constantly crashes in Ubuntu 18.04 fresh install
To manage notifications about this bug
The issue is solved in v5.3-rc1.
Let's wait for eoan kernel switches to v5.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836986
Title:
Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wirele
Public bug reported:
(initially reported at https://forum.snapcraft.io/t/chromium-does-not-
work-with-local-mdns-avahi-name-resolution/12483)
The current chromium snap does not allow to open any .local urls.
This is most likely caused by https://forum.snapcraft.io/t/no-mdns-
support-in-snaps-sho
I re-installed ubuntu 19.04 and the amdgpu.dc=0 fixed it in the
installer, also I tested with the default kernel (latest update) and can
confirm amdgpu.dc=0 works on default kernel as well, so it isnt related
to the kernel version.
The apport command doesnt run, it returns a command not found erro
** Summary changed:
- bionic/linux-gke-5.0: -proposed tracker
+ bionic/linux-gke-5.0: 5.0.0-1012.12~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Ke
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1837568 (gke-ker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Tags removed: kernel-block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837474
Title:
xenial/linux-snapdragon: 4.4.0-1121.127 -proposed tracker
To manage notifications about this bug
Apologies, the correct command is:
apport-collect 1837945
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837945
Title:
AMD RX 570 Black Screen at boot
To manage notifications about this bug go t
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
python3.6. This problem was most recently seen with package version
3.6.8-1~18.04.1, the problem page at
https://errors.ubuntu.com/problem/bd0aa7a47ea20c0202743e084bdd225bcd76cd26
contains more
All failed tests have done so before (just were not hinted), overriding
status.
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
ht
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a memb
** Patch added: "Proposed fix"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1838045/+attachment/5279422/+files/dkms-xenial-fix.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838045
Public bug reported:
In Ubuntu 16.04/Xenial the dkms command (2.2.0.3-2ubuntu11.7) ignores
the provided kernel source directory and then fails by not finding the
headers.
This was fixed upstream in 2.2.0.3-5 and landed in 18.04/Bionic.
Proposing to backport the additional line of code into Xenial
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pillow (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/1837196
Title:
Una
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
*** This bug is a duplicate of bug 1837575 ***
https://bugs.launchpad.net/bugs/1837575
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
I'm testing on my laptop with the avahi daemon running, and `python3 -m
http.server 8000`, and the chromium snap correctly resolves
http://bribon.local:8000, so it seems to be working.
I wonder whether this test is not meaningful?
--
You received this bug notification because you are a member of
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
*** This bug is a duplicate of bug 1837575 ***
https://bugs.launchpad.net/bugs/1837575
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
h
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
Here is a collection of crash reports in the Ubuntu Error Tracker about
this specific crash:
https://errors.ubuntu.com/bucket/?id=/usr/share/cinnamon/cinnamon-
settings/cinnamon-settings.py%3AAttributeError%3A/usr/share/cinnamon
/cinnamon-settings/cinnamon-
settings.py%40608%3A__init__%3A/usr/shar
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
**
*** This bug is a duplicate of bug 1837196 ***
https://bugs.launchpad.net/bugs/1837196
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
cinnamon. This problem was most recently seen with package version 3.8.8-1,
the problem page at
https:/
*** This bug is a duplicate of bug 1837196 ***
https://bugs.launchpad.net/bugs/1837196
** This bug has been marked a duplicate of bug 1837196
Unable to start cinnamon-settings because of "AttributeError: module
'PIL.Image' has no attribute 'VERSION'"
--
You received this bug notification
** Changed in: cinnamon (Ubuntu)
Status: New => Confirmed
** Changed in: cinnamon (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837196
Title:
Unabl
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
---
linux-oem-osp1 (5.0.0-1015.16) bionic; urgency=medium
* linux-oem-osp1: 5.0.0-1015.16 -proposed tracker (LP: #1836856)
* System does not auto detect disconnection of external monitor (LP: #1835001)
- drm/i91
Public bug reported:
I have autofs set to mount two cifs partitions
one from a local server, the second from a virtualbox machine in my laptop
when I stop the virtual machine and try to suspend, I got a message saying:
Freezing of task failed after xx seconds
after ~10 seconds, the screen goes of
Interesting that System 76 mentioned as it creates the initial boot disk
but is NOT the target system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838048
Title:
[chtrt5645 - chtrt5645, playback]
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Invalid
** Changed in: kernel-sru-workflow/security-signoff
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
101 - 200 of 441 matches
Mail list logo
