** Description changed:
Regular update including new kernel images. After reboot, sound was not
working and only the dummy output is shown.
Description: Ubuntu 18.04.6 LTS
Release: 18.04
Package:linux-image-4.15.0-177-generic (also happens with 180-generic
+ Hardware:
This is related to linux-image-4.15.0-177-generic, but I cannot find
that package as an option.
** Package changed: alsa-driver (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Regular update including new kernel images. After reboot, sound was not
working and only the dummy output is shown.
Description:Ubuntu 18.04.6 LTS
Release:18.04
Package:linux-image-4.15.0-177-generic (also happens with 180-generic
Expected: Sound to
I confirm this bug with this package on ubuntu 20.04 too, not happening
when build from source
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916931
Title:
omshell returns inconsistent results or
pace, namespace)
File
"/usr/local/lib/python3.8/dist-packages/Mnemosyne-2.7.3-py3.8.egg/EGG-INFO/scripts/mnemosyne",
line 150, in
from PyQt5 import QtWebEngineWidgets # Needs to happen first for some
reason.
ImportError: /lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.15
Kernel release bisection:
cosmic: 4.18.0-26: incremental, dry-run: panic about 303GB
cosmic: 4.18.0-26: incremental, dry-run: panic about 21GB
cosmic: 4.18.0-26: incremental, dry-run: panic about 22GB
disco: 4.19.0-13: incremental, dry-run: testing: success
The first run using 4.18.0-26 that
@ishinberg0 I am having the same issue on an alienware aurora r6 after
the upgrade to 5.4.0-48
I would like to file a new bug report for this. How do I go about
generating any debug info when I have a blank screen after grub menu?
--
You received this bug notification because you are a member
groovy: 20.10: 5.8.0-19-generic: incremental, no dry-run: Success (no
panic).
Kernel version bisection:
cosmic: 18.10: 4.18.0-25-generic: incremental, dry-run: panic
disco: 19.04: 5.0.0-13-generic: incremental, dry-run: success. 105m19s
(*insanely* fast).
Attempted revision bisection
Within
Cannot upload crash dumps due to timeout presumably due to size (1.6Gb).
Here're links instead:
1. http://temp.karakhorum.com/dl/crash_202009120944.tar.bz2
2. http://temp.karakhorum.com/dl/crash_202009121459.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'll test the 5.8 kernel this weekend.
I'll upload a couple of tarballs next.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
Kernel Oops: Rsyncing to bcache device w/o backing cache
** Attachment added: "syslog entries showing several "blocked for more than 120
seconds" errors"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896521/+attachment/5413021/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Given these logical volumes on a Drobo 5D mounting will result in a
hang:
root@atx1:/var/log# lvs vg-drobo
LV VG Attr LSizePool Origin Data% Meta% Move Log
Cpy%Sync Convert
encrypted vg-drobo -wi-a- 1000.00g
Is there any workaround that allows os-prober to find the Windows
partitions? Or, failing that, a way to just run the part of os-prober
that prints out the appropriate grub config section (I know what the
partition is so if there's a way to just run something like "os-prober-
windows /dev/sdb1"
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410787/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410791/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410793/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410790/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410785/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410788/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410792/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410794/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410786/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410789/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410780/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
apport information
** Tags added: apport-collected
** Description changed:
Platform details:
1) version.log attached
2) lspci-vnvn.log attached
3) lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04
4) apt-cache policy bcache-tools
bcache-tools:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410779/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410781/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410784/+files/WifiSyslog.txt
** Description changed:
Platform details:
1) version.log attached
2) lspci-vnvn.log attached
3) lsb_release -rd
Description:Ubuntu
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410778/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410776/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410782/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410783/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410777/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1895563/+attachment/5410775/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "sudo lspci -vnvn > lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+attachment/5410773/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Platform details:
1) version.log attached
2) lspci-vnvn.log attached
3) lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04
4) apt-cache policy bcache-tools
bcache-tools:
Installed: 1.0.8-2ubuntu0.18.04.1
Candidate: 1.0.8-2ubuntu0.18.04.1
Version
This change also prevents BPF security programs from running (like those
we use at Netflix) making Ubuntu less secure.
In case I'm not being clear enough: this is the worst change I've ever
seen in operating systems.
Some people want lockdown? Let them opt in.
--
You received this bug
The relaxed BPF restrictions still break BPF tracing and other things,
making Ubuntu no longer meet the debugability requirements for an
enterprise OS.
Lockdown should not be enabled by default. It needs to be opt-in, not
opt-out.
Tyler -- please fix Ubuntu.
--
You received this bug
With python 3: ModuleNotFoundError: No module named 'mididings'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783337
Title:
mididings fails to start
To manage notifications about this bug go to:
Yeah I would, but with the 5.3.0-26 update, it's now working again. Do
you still want me to try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850099
Title:
Kernel 5.3.0-19 panic after upgrade to
Ran fsck from a bootable linux, no issues (this is a LUKS encrypted
volume):
root@kali:~# fsck /dev/mapper/xubuntu--vg-root
fsck from util-linux 2.34
e2fsck 1.45.4 (23-Sep-2019)
/dev/mapper/xubuntu--vg-root: clean, 1139039/30162944 files, 77548819/120621056
blocks
root@kali:~# echo $?
0
--
Using: linux-image-unsigned-5.4.0-050400rc5-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850099
Title:
Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo
To manage
Still panics. Looks like the same panic
** Attachment added: "20191028_230646.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+attachment/5301082/+files/20191028_230646.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
After upgrading to eoan ermine, my laptop (Dell Precision 5510) got an error
message stating
"Error: out of memory
Press any key to continue..."
After pressing a key, nothing changed. I left the room and came back to
see that there was a kernel panic. I'll attach picture
Public bug reported:
During the installation of Ubuntu from a USB stick, the installer
crashed trying to install the GRUB on my /sda5
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
Further to yesterday's comment, issue is occuring while installing
(using debian-installer), at the "Install the GRUB boot loader on a hard
disk" stage. Displayed error is: "Unable to install GRUB in
/dev/mapper/--vg-root"
I have worked-around by choosing not to use LVM (I am choosing the
This is still occurring on Ubuntu 18.04.2. Hardware RAID1 & RAID0.
Tried adding quick_boot=0 to /etc/grub.d/00_header, no difference. If I
remove RAID, works fine.
Also proceeds past the error if I select "Guided - use entire disk"
instead of "Guided - use entire disk and set up LVM", but then
@Ryan Lovett, did you find a solution to this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772556
Title:
Can't find apt-transport-https
To manage notifications about this bug go to:
I did the same, minus the -d flag. Not sure if this is the correct
procedure, but it unblocked my usage of apt, which was critical.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/180
Title:
@Alberto, you're right. After talking to him and getting more info I
understand he's using an old closed source driver he needs to update.
My apologies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A buddy asked me to add that he's also unable to build - Trusty
(14.04.5).
...
ld -r -o
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-modeset/nv-modeset-interface.o
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-modeset/nvidia-modeset-linux.o
LD [M]
Verified that this installed successfully (i.e. no DKMS build failures)
on trusty for both -142 and -143 kernels.
virtualbox-lts-xenial 4.3.40-dfsg-0ubuntu1.14.04.1~14.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same problem as arQon.
Logged as sub-issue of #1820526 (found this ticket after opening that).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818049
Title:
virtualbox dkms modules fail
Public bug reported:
Linux 14.04.6 LTS with HWE stack.
Am on 4.4.0-142, did a dist-update and 3.13.0-167 gets pulled in e.g.
# sudo apt-get install linux-signed-generic-lts-xenial Reading package lists...
Done
Building dependency tree
Reading state information... Done
The following extra
** Attachment added: "VirtualBox DKMS build log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1820526/+attachment/5247076/+files/make.log
** Description changed:
Linux 14.04.6 LTS with HWE stack.
Am on 4.4.0-142, did a dist-update and 3.13.0-167 gets pulled in
Public bug reported:
This bug is Ubuntu specific, I've tested in Fedora 28 with Firefox 63.0
and cannot reproduce. I've attached an example extension that triggers
the bug.
To reproduce:
1. Go to about:debugging and load test extension
2. Open extension popup and click on text field
3. Try to
Same issue here, running Ubuntu 17.10 on a Lenovo Thinkpad T440.
Touchpad + trackpoint move between these three states:
1) everything works fine: touch to click, touch pad, two finger
scroll/right-click and trackpoint
2) everything except for two-finger actions work
3) nothing works: touchpad +
Update:
I am able to get X video if I boot with the monitor plugged into GPU1
and then switch the cable to GPU0 (according to nvidia settings)
TTY/UEFI video only works with the cable plugged into GPU1 (since this is my
motherboard's first PCI slot)
X video only works with the cable plugged
Continuing to grasp at straws:
sudo nvidia-xconfig
WARNING: Unable to locate/open X configuration file.
Package xorg-server was not found in the pkg-config search path.
Perhaps you should add the directory containing `xorg-server.pc' to the
PKG_CONFIG_PATH environment variable
No package
After doing that I can no longer switch to tty1 and get video, so I'll
probably have to start over before trying some more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756226
Title:
Interestingly, my Motherboard's GPU0 is detected as GPU1 in nvidia-
xconfig, and vice versa.
Relevant lines from Xorg log:
[22.370] (EE) NVIDIA(GPU-0): The NVIDIA graphics device PCI:8:0:0 bound to
this SLI X
[22.370] (EE) NVIDIA(GPU-0): screen is not the SLI parent device. This
Interestingly, I didn't even have an xorg.conf before, apparently.
Running standard nvidia-xconfig autogenerates an xorg.conf with both of
the following:
Option "MultiGPU" "on"
Option "SLI" "on".
I tried removing the SLI bridge from my computer and having just
"MultiGPU" on but that didn't work
Update: I removed one GPU and the problem was resolved.
Therefore, the problem appears to be specific to multi-GPU systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756226
Title:
Exactly the same setup as @dbonner and have exactly the same results.
TTY cursor only.
xrandr outputs "Can't open display".
@albertomilone I also get "N."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Changing this works for me:
In /usr/share/themes/Ambiance/gtk-2.0/gtkrc line 346
Change:
style "menu" = "dark" {
To:
style "menu" = "white" {
And run gtk-theme-switch2 to apply the style change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here's gimp showing the issue - bottom left.
** Attachment added: "Screenshot from 2018-01-29 14-20-10.png"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743710/+attachment/5044775/+files/Screenshot%20from%202018-01-29%2014-20-10.png
--
You received this bug notification
Thanks for all your support, Joseph. I plan to donate to Ubuntu as a
result of your continued support on this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle
I too am desperate for a solution (100+ Docker containers each with a
veth)
How do we apply Sergey Tikhonov's patch to our local system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458322
Title:
That kernel still caused the panic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
isci_task_abort_task
To manage notifications
Hello again, I spoke too soon. Problem went away immediately after
installing `intel-microcode` but returned after suspend and resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722478
Title:
Hi, I am running Ubuntu 17.10 GNOME with Wayland using a Thinkpad T440
as well. Installing `intel-microcode` fixed the issue immediately. I'm
assuming this is proprietary code :\
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That last kernel works! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
isci_task_abort_task
To manage notifications about
That one is broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
isci_task_abort_task
To manage notifications about this bug go
That one works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
isci_task_abort_task
To manage notifications about this bug go to:
That one is broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
isci_task_abort_task
To manage notifications about this bug go
That one works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
isci_task_abort_task
To manage notifications about this bug go to:
That one caused the same panic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
isci_task_abort_task
To manage notifications about
Just to verify, I did go back and try the 4.14 kernel again, and the
panic still occurs on the fresh install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel
That last one works:
Linux lawl 4.11.0-041100-generic #201710271957 SMP Fri Oct 27 19:58:57
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
So I got into some situation where the backup kennel i had was removed
via apt-get autoclean. Now I can't boot into any kernel, even recovery.
I'll have to reinstall, but then I can try the next kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Gotcha.
That one also caused the panic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
isci_task_abort_task
To manage
That most recent one seems to be the culprit, hit the same panic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
Linux lawl 4.11.0-041100-generic #201710251811 SMP Wed Oct 25 18:14:00
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle
Public bug reported:
I was upgrading from 17.04 to 17.10 when this happened.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: perl-base 5.26.0-8ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Public bug reported:
on upgrade from 17.04 to 17.10 this happened after I waited a while to
press ok after the upgrade on this kvm vm.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libstdc++6:amd64 7.2.0-8ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux
Same panic with 4.12-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
isci_task_abort_task
To manage notifications about this
I lied. Just was able to get this testing in.
4.11 - Works
4.12 - Failed to boot with the same panic
4.13 - Didn't test since 4.12 failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Will do. This is my work computer so it may take me a day or so to
complete this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Unable to handle kernel NULL pointer dereference at
So I installed the mainline kernel, and the same issue happened. I
couldn't get a picture as it was truncated due to resolution being
lowered during boot.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
** Attachment added: "Photo of panic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+attachment/491/+files/20171023_123805.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+attachment/4988864/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726519
Title:
Public bug reported:
So I just upgrade from zesty zapus to artful aardvark. At boot, right
after I enter my drive encryption password, it kernel panics with the
above message.
It doesn't even get far enough along in the boot process for syslog to
log this panic, so the only info I have is a
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718781
Title:
qupzilla assert failure: *** Error in `qupzilla': double free or
corruption (out):
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719212
Title:
qupzilla assert failure: *** Error in `qupzilla': malloc(): memory
corruption
Just for posterity's sake, I was able to solve my issue of older
initrd's consuming all of the space in /boot by removing the ones whose
kernel had been purged.
I had a /boot partition that was quite small and nearly every kernel
upgrade would fail with "no space left on device" messages.
--
*** This bug is a duplicate of bug 1681144 ***
https://bugs.launchpad.net/bugs/1681144
** This bug has been marked a duplicate of bug 1681144
Clicking on URLs in Kubuntu Installer Slideshow does nothing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
To reproduce launch qupzilla then type in a second level domain such as
such as maps.google.com or linux.conf.au.
qupzilla:
Installed: 2.1.2~dfsg1-2ubuntu2
Candidate: 2.1.2~dfsg1-2ubuntu2
Version table:
*** 2.1.2~dfsg1-2ubuntu2 500
500
"Thanks Timo. Tag updated. Looks good, I got a successful build +
connect using xserver-xorg-dev and libx1font-dev" - yes I can confirm
enabling xenial-proposed resolves issue for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
To reproduce isntall the lubuntu next iso and during the installation
try clicking the website link. I can try multiple times and no
webbrowser opens with the lubuntu website which after it moved should be
http://lubuntu.me Instead I did not launch a window.
Description:
Public bug reported:
On a lubuntu next install I tried to install offline following this
testcase on an hp laptop that had previously worked with lubuntu and
secure boot.
ubiquity:
Installed: 17.10.2
Candidate: 17.10.2
Version table:
*** 17.10.2 500
500
1 - 100 of 3182 matches
Mail list logo
