/etc/crypttab
# Example crypttab file. Fields are: name, underlying device, passphrase,
cryptsetup options.
ubuntuDevice UUID=2b44dbfa-f195-4a27-b126-c895c31a1bd5 none
luks,initramfs,discard
swapDevice UUID=676be184-ca1a-464c-82f6-dfea11adb1b9 none
luks,initramfs,discard
--
You received thi
/etc/fstab
#
LABEL=ubuntu/ btrfs
defaults,compress=zstd,commit=120,ssd,subvol=@ubuntu0 1
LABEL=boot /boot ext4defaults
0 2
tmpfs /tmp
Public bug reported:
Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of
booting, after grub)
- does not even show the enter cryptsetup passphrase
- affected kernels:
# apt list --installed |grep linux-signed
WARNING: apt does not have a stable CLI interface.
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ro rootflags=subvol=@ubuntu
mem_sleep_default=deep acpi_backlight=vendor pcie_aspm=force acpi_osi=Linux
dm_mod.use_blk_mq=1 quiet kas
apport information
** Tags added: apport-collected bionic wayland-session
** Description changed:
Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of
booting, after grub)
- does not even show the enter cryptsetup passphrase
- affected kernels:
# a
> apport-collect 1829620
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run
this command, please add a comment stating that fact and change the bug status
to 'Confirmed'.
I have ran and uploaded the output from app
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1829620/+attachment/5264700/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Hi Simon,
> a coworker and myself , both on ubuntu , have been it by the same
problem
thanks for confirming the error! Could you state what HW are you
running? As the bug apparently does not hit everybody.
> if we try with a older kernel in the grub list it works the first time
and then it does
> uninstalling cryptsetup and running upgrade-grub seems to fix the
problem in my case
Awesome, thank you Simon!
For me this fixes the issue with non-ubontu kernel (I don't have the old
versions of official kernels to try on).
So the final workaround is:
- have non-ubuntu (or old?) kernel
- sp
Adding cryptsetup to the list of affected, as even for non-ubuntu
kernels, action is required (reinstall cryptsetup) to fix this.
** Description changed:
Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of
booting, after grub)
- does not even show the
> > Hardware
> We use a laptop Asus vivobook S15 (we both have the very same model)
This leads me to hypothesis: The bug affects only(?) ASUS with later
(Kaby lake) Intel CPUs ?
** Summary changed:
- cryptsetup stuck at loading initramfs
+ ASUS microcode/kernel stuck at loading initramfs
** Cha
hi TJ, thank you very much for the helpful debug instructions!
> I just realised your report isn't about cryptsetup being the problem
and you never reach the initialramfs shell.
Yes, this is the case. Still, checked the lsinitramfs and the image
files are OK, with all the cryptsetup binaries.
I
ASUS zenbook ux433fn CPU info on machine hit by this bug.
** Attachment added: "/proc/cpuinfo"
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+attachment/5265096/+files/zenbook14_ux433fn_cpuinfo.txt
--
You received this bug notification because you are a member of Ker
> I'm wondering if the recent Intel microcode updates and related kernel
patches could be responsible? Can you tell us what CPU the system has?
And BINGO!
This was my suspicion too, I found a way to disable microcode updates to verify
this:
WORKAROUND: disable intel microcode updates
>From this
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1829620/+attachment/5265098/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1829620/+attachment/5265097/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1829620/+attachment/5265099/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
** Tags removed: cryptsetup plymouth splash wayland-session
** Tags added: microcode
** Description changed:
Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of
booting, after grub)
- does not even show the enter cryptsetup passphrase
- affected kern
Confirmed
WORKAROUND 2: downgrade (and hold) intel-microcode to older version from
bionic/main
apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1
Q: How comes liquorix kernel boots with the current micorcode ok?
Problem scoped down to:
intel-microcode from HWE (18.04.2) causes
TJ,
> An additional kernel command-line option that might reveal more would be
> remove "quiet splash" and add "debug early_print=XXX" where XXX is vga for
> BIOS-mode or efi for UEFI mode boots.
You may find "earlycon"
no info provided using these options, still stuck at the initrd line
witho
Hi Steve,
no problem, thank you for digging into this!
> ith the affected processors report the output of:
iucode-tool -S
# iucode-tool -S
iucode-tool: system has processor(s) with signature 0x000806eb
> is it correct that you are *not* seeing this with 5.0 kernel from the
> linux-hwe-edge
> Also, do systems succesfully boot when 'mds=no' is passed on the
kernel command line with the problematic microcode in place?
no, this does not help
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Tyler,
> Can you try to boot with the latest Ubuntu kernel, with the
problematic microcode, using 'mds=off' on the kernel command line? (Note
that it is 'off' instead of 'no')
I tried with mds=off, but no avail.
> If that doesn't work, can you try to boot with 'mitigations=off'
passed on the ker
PS,
#dmesg | grep microcode
#
returns nothing on the ubuntu hwe-edge kernel with mitigations=off
(=problematic ucode otherwise loaded)
Actually, is the microcode loaded at all?
# cat /sys/devices/system/cpu/cpu0/microcode/version
cat: /sys/devices/system/cpu/cpu0/microcode/version: No such fi
I'm very sorry, made a mistake
> > on the other hand, mitigations=off did cut it!
> > I guess now we're to find which of the mitigations is causing it? Do
> > you have a hint? Which are all the params for turning kernel
> > mitigations,please?
>
> Oh, that is interesting.
I was NOT able to boot
>From non-ubuntu kernel:
# uname -a
Linux mmm-U2442 5.0.0-17.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix
5.0-17ubuntu1~bionic (2019-05-17) x86_64 x86_64 x86_64 GNU/Linux
# dmesg |grep microcode
#
# cat /proc/cmdline
audit=0 BOOT_IMAGE=/vmlinuz-5.0.0-17.1-liquorix-amd64
root=UUID=824505cb-a96
Is this two separate bugs?
One that mds=on mitigation fails with the new microcode on any kernel,
the other that microcode in my HW (ASUS, Kaby lake) fails to load on ubuntu
kernels?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
> We'll speak with Intel about this
thank you! Hope they manage to fix it soon.
Let me know if you need some more testing.
Cheers,
--
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/1829620
> Anyone here think that this:
https://bugs.launchpad.net/ubuntu/+bug/1829735 could be either a dupe of
this bug or related?
Hi Lei, thanks for reaching here! Very likely duplicate, as we have the
same HW and the people describe similar symptoms.
Duplicates:
https://bugs.launchpad.net/ubuntu/+bu
For anyone having a similar problem, try booting with microcode updates off:
add dis_ucode_ldr to the kernel command line (from GRUB if you cannot boot)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
> To avoid confusion, we need to be clear that the i7-8565U is a Whiskey
Lake processor (*not* a Kaby Lake)
yep, sorry, I got confused in the intel naming scheme, it's whiskey I'm
having problems with ;)
> This may be a bug in how the kernel is loading the microcode
can you review the liquori
> or you've recently installed a BIOS update which contains the latest microcode
revision and the kernel microcode loader didn't do anything.
Asus published BIOS version 302 for your laptop on 2019-04-02
(https://www.asus.com/Laptops/ASUS-ZenBook-14-UX433FN/HelpDesk_BIOS/).
I really have
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.17/
so I have tested with a kernel from this PPA and it did not help.
Tyler,
there's one strange thing I'd like to ask: the boot process behaves
stateful(?!), ie. I can get into a previous "clean"/"dirty" state (and at least
liquorix) ker
Also, I'm still able to boot any kernel (with no extra boot params) when
I force-downgrade the intel-microcode to 2018 version (from bionic/main)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
just heads up that the recent update to intel-microcode
(3.20190514.0ubuntu0.18.04.3) does not resolve the issue (probably
wasn't even expected to)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Can someone pin-point what the change is in HWE kernel rebuilds -20 and
-21?
--
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/1829620
Title:
intel-microcode on ASUS makes kernel stuck duri
Hey, I'm the OP,
I can confirm @felix-ticona 's finding, after the kernel upgrade
(atleast HWE to the -21 revision and the issue is "magically" done).
# uname -a
Linux xxx 4.18.0-21-generic #22~18.04.1-Ubuntu SMP Thu May 16 15:07:19 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
# dmesg | grep command
is it because of this? (is the file new?)
intel-microcode-blacklist.conf :
# The microcode module attempts to apply a microcode update when
# it autoloads. This is not always safe, so we block it by default.
blacklist microcode
--
You received this bug notification because you are a member of
> Per the above, are we safe to grab the latest kernel upgrades now and
do away with the dis_ucode_ldr workaround in grub at this point?
Hi, no, or at least problematic.
I don't know if/why it seemed to work for me at that time. Now I was NOT able
to boot ubuntu 5.0/4.18 kernels without the dis_
Added WORKAROUND 3: BIOS upgrade
Please note this workaround is permanent and cannot be reverted, unlike 1,2. So
I will not be able to test this bug anymore.
** Description changed:
Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of
booting, after gru
I am not sure if this is a kernel/FW issue, as the soundcard is recognized and
the sound playes at first.
On the other hand there were not changes/updates to alsa,pulseaudio and the
sound used to work ok before.
These problems started to appear cca a month ago(?) but usually "some
trick" made i
Public bug reported:
Issue: whichever sound-related action (sound +/- media keys, spotify song,
youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and
then stops and becomes silent.
The interesting thing is that when I stop playing the audio (ie close the
browser tab w
apport information
** Tags added: apport-collected bionic third-party-packages wayland-
session
** Description changed:
Issue: whichever sound-related action (sound +/- media keys, spotify song,
youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and
then stops and be
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1834782/+attachment/5274266/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1834782/+attachment/5274267/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1834782/+attachment/5274268/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.
Hi Daniel,
good riddance! Already the previous version of hwe-edge (which I had as
auto-backup in /boot) works ok.
> an you please try some older (or newer) kernel versions from here:
# uname -a
Linux mmm-U2442 5.0.0-19-generic #20~18.04.1-Ubuntu SMP Thu Jun 20 12:17:14 UTC
2019 x86_64 x86_64 x
> the last working version was linux-hwe-edge 5.0.0-19 and the first
broken version is linux-hwe-edge 5.0.0-20.
yes, correct.
> I'm a little confused because you reported this bug using kernel
4.18.0-25-generic. Was there another regression in the 4.18 series?
yes. Audio used to work on both hwe
This looks like it's a driver/kernel related issue, can you explain to
me how the sound could be working for a couple of seconds and then
stops?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchp
I'm suffering this after this update too. It is the latest in a
depressingly long list of Ubuntu updates that have ed up my system.
You really *need* better testing of updates. If you can't improve the
testing then there needs to be a way to roll-back the system to before
an update.
Instead of
Daniel,
Which part of what I wrote you do you another bug about? The fundamental
issue, gdm doesn't work, hence no login screen, after the latest
kernel/gdm update is the same as this bug, so why create a duplicate?
The previous issues were with past distribution versions so filing a bug
is not u
> which solves the problem
I don't consider switching to lightdm to be a solution the problem. It's a
workaround.
--
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/1779476
Title:
Ubuntu 18
Turns out lightdm is working after all, almost. If you wait patiently
when the black screen appears after the Ubuntu 5 dots boot screen,
possibly as much as 4 minutes, then the desktop eventually appears,
albeit somewhat messed up, with a message box asking you to "unlock the
login keychain" becaus
Daniel,
Installing haveged fixed my issue so I'm pretty sure its the same as
this one. Therefore I won't create a bug of my own.
Thanks for the help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
I agree with monkeybrain2012. The question that must then be raised is
how this breakage got into an Ubuntu software update for the masses
almost 2 months after it was known that a kernel change had broken gdm3
login, and after commits for the underlying issues had been created in
debian.
--
You
Reverting the fix for CVE-2018-1108 to get this to work is not necessary
and not a good idea. The root cause has been identified upstream in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572 and fixes
committed.
Turns out it was fontconfig generating a uuid that tripped over the CVE
fix. On
Bug #1779827 appears to be a duplicate of this.
--
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/1779476
Title:
Ubuntu 18.04: gdm3 does not switch to graphics after update
Status in gdm3
This appears to be a duplicate of bug #1779476.
--
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/1779827
Title:
failure to boot with linux-image-4.15.0-24-generic
Status in Ubuntu:
Conf
Re. comment #42, how do you install that download package on Ubuntu?
--
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/1779476
Title:
Boot process hangs indefinitely. Never finishes.
Statu
This still looks like the getrandom() hang described in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572. This was
caused by the fix in the kernel for CVE-2018-1108. Two complementary
fixes have been discussed in the Debian bug neither of which modify the
kernel. The first is a change to th
@mocnak, re. comment #78. Thanks. I reinstalled gdm3 but didn't think
about ubuntu-desktop. Anyway I've reverted to the existing Ubuntu
version of plymouth and got my system working again (with haveged).
Did you try the fixed Plymouth?
--
You received this bug notification because you are a memb
@m-tim-smith, comment #85, if none of the fixes/workarounds here are
working for you, perhaps you have a different problem with very similar
symptoms. For example bug #1779476.
@joverstreet1, comment #86, I have an SSD and my system's been running
fine with kernel 24 since I installed haveged.
--
@joverstreet1, kernel 24 was installed first, by Ubuntu Software
Updater. I then installed haveged to work around a kernel change to
getrandom(). My SSD is not Western Digital but the SSD has nothing to do
with the problem, at least not the one that is the focus of this bug
report.
The kernel chan
Public bug reported:
I am running a virtualbox with Lubuntu 18.04. I upgraded to this version
from the previous LTS through the software-updater, and everything
worked fine, except for the software updater- Whenever I run it manually
to see if there are updates, or when it pop-out automatically an
I ran update-manager in the terminal and made it crash as I mentioned,
however no useful input was shown in terminal :/ any idea?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
I tried that command but it asking me to authorize launchpad to access
on my behalf, which does not seem to be a very safe thing to do. What
info do you need?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
lspci -vvvnn output:
The apport bug report was attached
-
00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM
Registers [8086:1904] (rev 08)
Subsystem: Hewlett-Packard Company Skylake Host Bridge/DRAM Registers
[103c:80a4]
Control: I/O- Mem+
I think the issue regards Ubuntu 16.04.2 and its flavor Lubuntu, no idea
about the others, I am on 64bit.
I did as #12 suggested will let you know how I does.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Everything seems to be fixed now!
Don't know if it is still relevant but when the "broken" update came out the
system did not show up any warning on potential missing libs or that it was an
incomplete update. Thank you!
--
You received this bug notification because you are a member of Kernel
Pa
I did: sudo apt-get dist-upgrade and it fixed my issues.
--
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/1687623
Title:
linux-4.4.0-77.98 was a phased update in -updates only and may beco
Thanks for the fix Stefan! If I wasn't on dual-boot it would have been a
nightmare trying to fix it without internet.
I had no issue with screen resolution so I suppose not everyone is
affected in the same way.
Maybe ubuntu admins could post an announce on the home page of the forum
to warn users
Public bug reported:
fresh install of 20.04.1. Setting up FDE per
https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019. This
is my 4th system following those directions (2 devboxes, one other
laptop), I'm reasonably confident the steps are sound & I followed them
correctly.
after co
I am seeing a similar reproduction, but earlier at the FDE passphrase
screen. My system apparently (at least under liveusb) reports
/sys/class/dmi/id/chassis_type==31
Seems related, but i've posted a new bug due to the chassis type being
"correct" (?)
https://bugs.launchpad.net/ubuntu/+source/lin
Already posted in AskUbuntu: https://askubuntu.com/questions/1302234
/keyboard-not-working-at-initial-fde-passphrase-screen-20-04-1
However, as a developer myself, I feel this is mostly** unambiguously a
bug*** and hope it can be considered as such.
If I can get a timely response (specifically,
absent any advice here on triage steps, i figured it couldn't hurt to
attempt updating kernels.
not knowing enough about possible interactions between a much newer
kernel and whatever my problem was, I debated upgrading kernels via
`.deb`s directly from the ppa, versus HWE-edge stack. I decided t
hoping to eliminate any preception my setup is non-standard, I just went
ahead and did a full re-install. All default options (full format, etc)
except I selected "LVM + encryption"
upon reboot, I see nothing on the lcd at all.
--
You received this bug notification because you are a member of Ke
full re-install with no encryption also same result (boots to blank
screen, no discernible text or flashes) with a
Eg, full default options everywhere.
The only clicks besides "next/OK" were:
- I ran this twice, WITH & WITHOUT "use proprietary" checked
- select "erase disk and install ubuntu" ra
The blinking light bug still exists in Ubuntu 20.04.1 LTS 64bit.
Computer: HP Elitebook 8640W
The wifi on-off indicator light keeps blinking blue-red after a fresh
install.
The fix proposed by "Thomas Wagner (tomas-wagner) on 2012-07-27" does
fix the problem.
--
You received this bug notificat
would something like
https://www.amazon.com/dp/B07J5WFPXX/ref=cm_sw_r_cp_apa_fabt1_IciRFb2QMGBDJ
work?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1838151
Title:
Poor quality audio wi
Thank you for the advice! I'm going to purchase and see if it works with
my setup.👍
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1838151
Title:
Poor quality audio with modern Bluetooth
Public bug reported:
Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the
network manager stops working or better it behaves weird. I noticed 4
behaviors in different occasions:
1) Enable networking and enable wifi are toggled but the connection I
used before suspending is not sh
The bug is Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1719731
Title:
Suspending Lubuntu 16.04.3 result
Hello sorry for the late reply.
I am not familiar with playing around the upstream kernel, this is my
only machine and I cannot break anything :/
I have another kernerl version: Linux 4.4.0-93-generic I tried and it
has the same behavior.
Today I notice that Power Manager shows a GDBUS.Error, so
Also is there any chance that the error is linked to
https://ubuntuforums.org/showthread.php?t=2371537 where I reported that
I cannot connect to a specific wifi (I can on Windows 10 though) and a
specific router?
--
You received this bug notification because you are a member of Kernel
Packages, w
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1719731
Title:
Suspending Lubuntu 16.04.3 results in network manager s
** Description changed:
Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the
network manager stops working or better it behaves weird. I noticed 4
behaviors in different occasions:
1) Enable networking and enable wifi are toggled but the connection I
used before suspe
I managed to fix the bug in XFCE power manager (following a tutorial
online, just a string to edit), however the issue still persists.
On the internet I found out that I am not the only one to report this
issue:
https://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
after-16-04-up
4.13-rc4 - touchscreen is working. No go on touchpad, does not show up
with lsusb, lspci or lshw
--
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/1658345
Title:
Touchpad not recognized on
ApportVersion: 2.20.3-0ubuntu8.7
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2017-07-12 (29 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Package: linux (not installed)
Tags: yakkety
Uname: Linu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1658345/+attachment/4930748/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1658345/+attachment/4930746/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1658345/+attachment/4930747/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
This also affects me. And it's why people don't use linux, unfortunately
--
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/1589008
Title:
Bluetooth freezing video playback In Ubuntu/Kubuntu
Public bug reported:
When testing mainline kernels from http://kernel.ubuntu.com/~kernel-
ppa/mainline/ I noticed a problem which first appears with the 4.4-rc8
kernel package.
I opened a bug on the kernel bugzilla a few days ago, see
https://bugzilla.kernel.org/show_bug.cgi?id=110931
See that f
Looks like bug 1534647, "Collateral damage due to kernel configuration
change enabling CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)" covers the same
issue. There a sound card stopped working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I have one update.
I have exact the same situation with my Lenovo laptop.
Uname: 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Above is explained that this issue is fixed in kernel 3.14.0. So, waiting or
getting an upstream kerel is an solution.
A
Also affected: X201
--
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/1325298
Title:
Lenovo R61i: fan not speeding up on high temperatures
Status in “linux” package in Ubuntu:
Confirmed
Incomplete is a nice decription for "no one is caring.". Fact is that in
(K)Ubuntu's default installation this bug appears and is very annoying.
For me it is also a fact, that the problem can be solved, by the
procedure I have described. Unfortunately I can not tell which one did
the fix. But it me
@Philipp: With my "solution" which works for, there is no need to run
the fan on disengaged. At the moment e.g. the fan is not running at all
and I am happy with 44° Celsius which rather low. But when I am
stressing the system more, the temperature hardly ever rises above 60°
Celsius. Then the fan
John (or whoever receives this),
I downloaded and installed a package upgrade yesterday which appears to
have resolved the issue.
Thanks,
Mark
On 2/20/2014 9:37 AM, John Kim wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer
1 - 100 of 987 matches
Mail list logo
