Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=110187.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
** Changed in: oem-priority
Importance: High => Critical
** Changed in: oem-priority
Status: New => Triaged
** Changed in: oem-priority
Assignee: (unassigned) => Cyrus Lien (cyruslien)
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
** Package changed: cifs-utils (Debian) => linux (Debian)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1572132
Title:
SMBv2+ does not show all files when mounting a windows share
Stat
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc3 kernel [0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not f
Public bug reported:
Hello,
My touchpad worked yesterday, but today it is not working.
I tried to search all information about synaptics touchpad on my Xubuntu 16.04
but touchpad information are not listed with xinput and other command.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linu
This bug was fixed in the package mesa - 19.0.1-1ubuntu2
---
mesa (19.0.1-1ubuntu2) disco; urgency=medium
* i965-comet-lake.diff: Add support for CML. (LP: #1821863)
-- Timo Aaltonen Wed, 03 Apr 2019 10:58:06 +0300
** Changed in: mesa (Ubuntu Disco)
Status: New => Fix Re
** Attachment added: "devices"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1823126/+attachment/5252677/+files/devices
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Andrea Righi (arighi) => Khaled El Mously (kmously)
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Andrea Righi (arighi) => Khaled El Mously (kmously)
** Changed in: kernel-sru-workflow/prepare-package-signe
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Khaled El Mously (kmously) => Andrea Righi (arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Khaled El Mously (kmously) => Andrea Righi (arighi)
** Changed in: kernel-sru-workflow/prepare-package-signe
** Summary changed:
- linux-azure: -proposed tracker
+ linux-azure: 4.15.0-1042.46 -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-kern
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821820
Title:
Cannot boot or install - have to use n
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
** 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:
I also noticed this, my laptop's integrated Intel audio device is also
missing from pulseaudio(both as input and output), but I can see other
HDMI or USB sound devices I may have attached and I can switch to them
and they work as expected.
Interestingly the device works when playing a WAV file usi
FWIW, I think a better way to do this is to ask Realtek to implement
correct de-pop function for this platform.
Of course blacklisting is still a proper compromise.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
"enable_autosuspend=0" did not fix the issue for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
Status in linux
I also tested the d9ef158adf04b81772a7e9d682a054614ebac2fd commit. There
is a problem in it.
The commit 5113d730a1ee26bb13cbe38fdc10a7ebe7baf3cd could not be tested.
An error occurred: "fatal: reference is not a tree:
5113d730a1ee26bb13cbe38fdc10a7ebe7baf3cd".
There is no problem in the ed14acd31
kernel v4.10-rc8 boots until hang on bug under 16.04.2 LTS. I don't know
why the same kernel under 15.10 it is not, but it is freezed release and
not important.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Emiliano,
That means it's a different issue. Please file a new bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
--- Comment From schwe...@de.ibm.com 2019-04-04 05:48 EDT---
Just to make sure: This bugzilla does not apply to Network under DPM neither on
z13 nor on z14 machines.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package xorg-server - 2:1.20.4-1ubuntu3
---
xorg-server (2:1.20.4-1ubuntu3) disco; urgency=medium
* sync-i965-pciids.diff: Sync with mesa, add support for CML. (LP:
#1821863)
* dix-ensure-work-queues-are-cleared-on-reset.diff: Fix a race
condition
Public bug reported:
I cannot turn on Bluetooth in the settings, and `hcitool dev` doesn't
show devices. Bluetooth used to work before upgrading from 18.04 to
18.10.
lsb_release -rd:
Description:Ubuntu 18.10
Release:18.10
apt-cache policy bluez
bluez:
Installed: 5.50-0ubuntu1
Can
You have been subscribed to a public bug:
Hi,
I have ubuntu 18.04 server. I have installed iproute2 pkg
'4.15.0-2ubuntu1' . When I try creating a network namespace with the
command "ip netns add test", the command hangs and never completes.
---
root@b1v:~# uname -a
Linux b1v 4.15.0-45-g
This seems to be an issue with network namespaces, which I assume may
point to Linux. This report is about Ubuntu Kylin, a supported Ubuntu
flavor.
** Project changed: ubuntu-ubuntu-server => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1823146
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
see syslog?
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-17-generic 4.18.0-17.18
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
AudioDevicesInUs
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823161
Title:
fails to resume after suspend
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Fix Released => Confirmed
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Confirmed => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** 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
**
** 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
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: New => Fix Committed
** 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 workflo
--- Comment From mainam...@in.ibm.com 2019-04-04 07:18 EDT---
Any update on this? is this fix is integrated?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1741860
Title:
Drew Walton (drewwalton19216801), Thanks! it works.
Currently I run this command on startup using systemd.
Is there a simpler way?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813701
T
so why the peculiar behaviour that lightdm works when the partition
installed native grub boots the system
BUT not when a grub installed by another partition is used then lightdm
consistently crashes and the machine locks up..
BUT if i915 is added to /etc/modules in the offending partition it all
Commit c3cb424a0869 ("drm/amd/pp: Send khz clock values to DC for smu7/8
") is in mainline but mainline still has the issue?
Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu
--
You received this bug notification because you are a member of Kernel
Pa
Hi Mamatha, well, as you can see from Launchpad comment #6:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1741860/comments/6
we are still waiting for the feedback from IBM about the validation mentioned
in comment #5:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/174186
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** 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
unfortunately I've moved away from kernel work, for now at least, and no
longer have time to continue this bug; if anyone else would like to pick
up the work, I'm happy to answer questions.
** Changed in: linux (Ubuntu Xenial)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in:
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.15.0-1032.32 -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-t
Hi, Gustavo.
We have just missed the kernel freeze. So, we will need to SRU this
change. I am still waiting for your feedback, before I submit this for
review.
Thank you.
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.4.0-1080.90 -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-te
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
** 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 --
kernel-sta
--- Comment From grom...@br.ibm.com 2019-04-04 08:50 EDT---
Hi Cascardo!
(In reply to comment #42)
> Hi, Gustavo.
>
> We have just missed the kernel freeze. So, we will need to SRU this change.
> I am still waiting for your feedback, before I submit this for review.
I think it's fine to m
booting from
Linux raf-NG-A717-72G 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
solves the problem
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Fix Committed => 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 associate
Hi,
One more observation. We are facing this issue with four of our compute nodes.
When I rebooted one of them,
it seems to fix the issue. Nevertheless we dont think this is a viable
solution. Hence I will submit the apport file shortly from a defective server.
--
You received this bug notific
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821820
Title:
Cannot boot or install - have to use nomodeset
Yes I can sorta confirm the bug is in uswsusp. I removed the package
and pm-utils and used both "systemctl hibernate" and "echo disk >>
/sys/power/state" to hibernate. It seems to succeed and shuts down, I
am just not able to resume from it, which seems to be a classical
problem solved just by set
Created attachment 282117
boot-sequence
Okay I found a way to get it working and there was also a huge mistake
on my last boot-config, the resume was commented :P
I basically followed this: https://askubuntu.com/a/1064114
but changed to:
resume=/dev/disk/by-uuid/70d967e6-ad52-4c21-baf0-01a813ccc6a
Created attachment 282113
pm-suspend.log
Okay, I reinstalled pm-utils and make sure uswsusp was removed (apt
remove --purge uswsusp).
# fdisk -l | grep swap
/dev/sda8 439762944 473214975 3345203216G Linux swap
root@matheus-Inspiron-15-7000-Gaming:/home/matheus# blkid /dev/sda8
/dev/sda8: U
Created attachment 282119
Screenshot at 2019-04-03 16-42-48.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328727
Title:
[Asus 1000HE] s2disk/hibernate hangs during saving of image
Created attachment 282115
boot-sequence
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328727
Title:
[Asus 1000HE] s2disk/hibernate hangs during saving of image data
Status in Linux:
On Wednesday, April 3, 2019 11:34:32 AM CEST Jan Kara wrote:
> On Tue 02-04-19 16:25:00, Andrew Morton wrote:
> >
> > I cc'ed a bunch of people from bugzilla.
> >
> > Folks, please please please remember to reply via emailed
> > reply-to-all. Don't use the bugzilla interface!
> >
> > On Mon, 16
** 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
has already
https://bugs.freedesktop.org/show_bug.cgi?id=110199
** Bug watch added: freedesktop.org Bugzilla #110199
https://bugs.freedesktop.org/show_bug.cgi?id=110199
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Hi Jochen, not sure if I got that right - so let me rephrase according
to our needs:
Does that mean - and can you conform - that this unique MAC address
patch for PXE boot applies to a z14 in DPM mode with a certain level
(tbd) of firmware code?
--
You received this bug notification because you
and https://bugs.freedesktop.org/show_bug.cgi?id=102646
** Bug watch added: freedesktop.org Bugzilla #102646
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
fixed by downloading linux firmware from
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
then after copy files from nvidia folder to /lib/firmware/nvidia/ everything
become work.
Small story about "warninings" not even relating my videocard killing
everything around
** Changed in: iproute2 (Ubuntu)
Status: New => Invalid
** Changed in: iproute2 (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: iproute2 (Ubuntu Xenial)
Status: New => In Progress
** Changed in: iproute2 (Ubuntu Xenial)
Assignee: (unassigned) => Stefan Bader
Public bug reported:
shiftfs transparently translates the on-disk ids of an underlaying
filesystem into valid ids in a given user namespace. This is wanted in
Ubuntu for LXD and Anbox and is targeted for inclusion in Disco.
The main advantage of shiftfs is that it provides signficiant
performance
summary for workaround via kernel parameter to blocker loading:
modprobe.blacklist=hibmc_drm
**prevent load during install
To add "modprobe.blacklist=hibmc_drm" kernel parameter in grub when boot from
d-i iso (press ‘e’ key and then press F10 or ctrl+x ( those key was noticed on
the screen)
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.15.0-1036.38 -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-t
Hi,
I tried running apport but it seems that it never completes the
collection. It is running from a long time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823146
Title:
network nam
So if this was committed 3-28 we can expect an update on May 13th? Is
that correct?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1814069
Title:
kernel linux-image-4.15.0-44 not booting
Marking "In Progress" for disco, as a patch was submitted:
https://lists.ubuntu.com/archives/kernel-team/2019-March/099315.html
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1820187
Title:
Huawei Hi1822 NIC has poor performance
Stat
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
** 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:
** 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
**
** Changed in: kernel-sru-workflow/prepare-package
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:
https
I believe this issue was due to "legacy suspend" rather than "modern
suspend" selected in UEFI. After a couple suspends I am no longer seeing
the problem, but will reopen if it happens again.
** Changed in: bluez (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification
** Summary changed:
- lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 (using "foreign grub")
--
You received this bug
Scratch that; the first couple suspend operations did work, and then
they stopped again. I'll do more testing and report back. I did rule out
mouse movement by using the hardware power switch on the mouse.
** Changed in: bluez (Ubuntu)
Status: Invalid => Incomplete
--
You received this bu
Further info:
This happens even if I start my "tail -f" process or "read -t 1" loop
within a chroot environment running a completely different distro, under
an Ubuntu 18.04 terminal. The distro in question (really a custom from-
scratch distro) has never had this problem when running as the real
** 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 1822790 (bionic/li
here we have a normal journalctl boot log .. notice the size .. more
entries .. about 1 minute start to finish source the partition that
always works lightdm starts normally plymouth appears on screen etc.
this one was booted by grub installed by zlink4 - on sda6 ..
** Attachment added: "zlink1 /
Not working also on 4.18.0-17-generic kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796582
Title:
Internal microphone not working on Lenovo Ideapad 330S-15ARR
Status in Linux:
** 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 1822832 (trusty/li
** 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 1822795 (bionic/li
** 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 1822817 (xenial/li
here is the journalctl boot log for sda6 /zlink4 booted by it's own
install of grub (self grub)
(it was reinstalled for this purpose .. to show it works .. however
plymouth does not show on the screen at all on boot but does on shutdown
)
now one change is addition of a vt.handoff=1 to the end o
** 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
I installed Ubuntu Studio and experienced same with amd64 platform,
vmlinuz-5.0.0-8-lowlatency. After installing generic kernel, usb mouse
performance returned to normal. I had this also with the live version
18.xx last fall, and never installed.
--
You received this bug notification because you
** 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
**
** Changed in: kernel-sru-workflow/prepare-package
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:
https
Mine is Ubuntu Studio 19.04 beta, attaching dmesg with
vmlinuz-5.0.0-8-lowlatency.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787743/+attachment/5252847/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, whi
** 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
whoops added the wrong attachment above it is the one including the
grub-update dialog .. instead of being the bot after the command
** Attachment added: "this one is after the grub-update .. accidental switch"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/525
okay generated the default grub.cfg via sda6 grub-install boot instance
.. vt.handle=1 is set by default for self root boot about a minute to
boot
no change .. still no plymouth on boot but there is a flicker with
lightdm .. which restarts once video mode switch has happened ..
note all grub in
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-
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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-
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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
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 'verifica
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 'verifica
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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
Looks like my problem was unrelated to this issue, it was actually
caused by timidity blocking the physical sound device.
This workaround fixed it: https://askubuntu.com/questions/1085174/no-
sound-after-upgrade-to-18-10-only-a-dummy-device-is-shown
--
You received this bug notification because
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 'verifica
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 'verifica
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 'verifica
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 'verifica
1 - 100 of 246 matches
Mail list logo
