[Bug 1976160] Re: Sound card not detected (Dummy Output) after update to kernel 4.15.0-177-generic or 4.15.0.180-generic
** 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: Dell XPS 13 with Intel HD onboard sound (Realtek HD ALC3246) Expected: Sound to work, mic to work, sound card recognised in settings. What happened instead: Dummy sound only available card, sound does not work, mic does not work Tried: Restarting pulse audio, grepping lsmod for a sound card (nothing listed) Workaround: Everything works fine if I boot into 4.15.0-176-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976160 Title: Sound card not detected (Dummy Output) after update to kernel 4.15.0-177-generic or 4.15.0.180-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1976160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976160] Re: Sound card not detected (Dummy Output) after update to kernel 4.15.0-177-generic or 4.15.0.180-generic
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. https://bugs.launchpad.net/bugs/1976160 Title: Sound card not detected (Dummy Output) after update to kernel 4.15.0-177-generic or 4.15.0.180-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1976160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976160] [NEW] Sound card not detected (Dummy Output) after update to kernel 4.15.0-177-generic or 4.15.0.180-generic
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 work, mic to work, sound card recognised in settings. What happened instead: Dummy sound only available card, sound does not work, mic does not work Tried: Restarting pulse audio, grepping lsmod for a sound card (nothing listed) Workaround: Everything works fine if I boot into 4.15.0-176-generic ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976160 Title: Sound card not detected (Dummy Output) after update to kernel 4.15.0-177-generic or 4.15.0.180-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1976160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916931] Re: omshell returns inconsistent results or segfaults
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 segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925093] [NEW] Mnemosyne won't launch
Public bug reported:
Error from command line launch:
Log body:
An unexpected error has occurred.
Please forward the following info to the developers:
Traceback (innermost last):
File "/usr/local/bin/mnemosyne", line 4, in
__import__('pkg_resources').run_script('Mnemosyne==2.7.3', 'mnemosyne')
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 665, in
run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1463,
in run_script
exec(code, namespace, 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' not
found (required by
/home/brendan/.local/lib/python3.8/site-packages/PyQt5/QtCore.abi3.so)
Lenovo Yoga 720
Ubuntu 20.10 Groovy
Mnemosyne v 2.7.2+
I expected the program to launch.
The program didn't launch.
** Affects: mnemosyne (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925093
Title:
Mnemosyne won't launch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mnemosyne/+bug/1925093/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
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 was able to get to 303GB before panic is intriguing (it's why I ran it twice). All previous panics when doing an incremental rsync were ~20-22GB in (ala the subsequent two runs). The only thing we can say with certainty is the problem did not reproduce using 4.19.0-13. If the problem is a stack overflow then any changes in stack size, or different paths which use less stack, would result in the problem being less visible using the amount of data I'm copying (~1.4TB). ** Attachment added: "crash files from weekend of 10/3/20" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+attachment/5417903/+files/crash_201003.tar.bz2 -- 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 kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45
@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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894378 Title: Cannot boot after updating kernel to version 5.4.0-45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
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 disco tree:
git checkout -b mybisect origin/master
git bisect start
git bisect good Ubuntu-4.18.0-12.13
git bisect bad Ubuntu-5.0.0-10.11
This set my HEAD to:
commit 94710cac0ef4ee177a63b5227664b38c95bbf703 (HEAD, tag: v4.18)
Author: Linus Torvalds
Date: Sun Aug 12 13:41:04 2018 -0700
Linux 4.18
I then did a 'Kernel made' e.g.
cp -a /boot/config-`uname -r` .config
make oldconfig
make clean
custom=bbb01
make -j $(nproc) deb-pkg LOCALVERSION=-${custom}
The resulting kernel would boot but I could not ssh to it. systemctl
would return error about not being able to connect to dbus.
I assumed there are Ubuntu specific bits to the kernel which systemctl
requires so aborted.
** Attachment added: "dmesg from 4.18.0-25-generic panic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+attachment/5414734/+files/dmesg.202009261751
--
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 kernel panic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
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 kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896521] Re: Mounting a logical volume on a Drobo 5D will hang
** 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 to Ubuntu. https://bugs.launchpad.net/bugs/1896521 Title: Mounting a logical volume on a Drobo 5D will hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896521] [NEW] Mounting a logical volume on a Drobo 5D will hang
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
persistent vg-drobo -wi-a- 600.00g
timber vg-drobo -wi-ao1.50t
timber2vg-drobo -wi-ao1.00t
root@atx1:/var/log# mount /dev/vg-drobo/timber /mnt/drobo-timber/
# hangs
I expect the mount to succeed without hanging.
This bug is not present in 16.04 / 16.04.1 (latest is
linux-4.4.0-189-generic).
Release bisection revealed it showed up in u16.04.2:
linux-4.8.0-36-generic from LiveCD.
I found it when finally upgrading a 16.04 host which was using 4.4
kernel to 18.04 which uses 4.15 (LTS) / 5.4 (HWE) kernels.
After further commit bisection I found the commit which introduced this
behavior is: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?id=5b91dfe187bbe3a8116432016375f39fff91a237
$ git show 5b91dfe187bb
Mon Apr 18 13:09:10 2016 +0300 5b91dfe187bb usb: storage: scsiglue: limit USB3
devices to 2048 sectors [Felipe Balbi]
diff --git a/drivers/usb/storage/scsiglue.c b/drivers/usb/storage/scsiglue.c
index 9da1fb3d0ff4..88920142e375 100644
--- a/drivers/usb/storage/scsiglue.c
+++ b/drivers/usb/storage/scsiglue.c
@@ -133,6 +133,11 @@ static int slave_configure(struct scsi_device *sdev)
* let the queue segment size sort out the real limit.
*/
blk_queue_max_hw_sectors(sdev->request_queue, 0x7F);
+ } else if (us->pusb_dev->speed >= USB_SPEED_SUPER) {
+ /* USB3 devices will be limited to 2048 sectors. This gives us
+* better throughput on most devices.
+*/
+ blk_queue_max_hw_sectors(sdev->request_queue, 2048);
}
/* Some USB host controllers can't do DMA; they have to use PIO.
I built kernels with this change commented out and confirmed I can
successfully mount the LV from the Drobo using 4.8 and 4.15 kernels.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-117-generic 4.15.0-117.118
ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not
found.
Date: Mon Sep 21 12:37:39 2020
HibernationDevice:
#RESUME=UUID=64794be3-24a0-49f9-9239-371624a3d193
RESUME=none
InstallationDate: Installed on 2020-09-20 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
enp0s31f6 no wireless extensions.
lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic
root=/dev/mapper/vg--ssd2tb-u18040 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.15.0-117-generic N/A
linux-backports-modules-4.15.0-117-generic N/A
linux-firmware 1.173.19
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3802
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII RANGER
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896521
Title:
Mounting a logical volume on a Drobo 5D will hang
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896521/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848496] Re: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS
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" that would be perfect). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848496 Title: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1848496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Lspci.txt
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: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcInterrupts.txt
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. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] UdevDb.txt
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: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcEnviron.txt
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 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] CRDA.txt
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: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Lsusb.txt
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: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcModules.txt
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 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] WifiSyslog.txt
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 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] CurrentDmesg.txt
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. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcCpuinfoMinimal.txt
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. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcEnviron.txt
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 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
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: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Sep 13 12:53 seq + crw-rw 1 root audio 116, 33 Sep 13 12:53 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.17 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command
[Bug 1895563] ProcCpuinfoMinimal.txt
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. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcInterrupts.txt
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. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] WifiSyslog.txt
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 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 table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno
[Bug 1895563] ProcCpuinfo.txt
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 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Lspci.txt
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: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcModules.txt
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 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] UdevDb.txt
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: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Lsusb.txt
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: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] CurrentDmesg.txt
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. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
** 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. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] [NEW] Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
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 table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kernelcrash bionic uec-images ** Attachment added: "cat /proc/version_signature > version.log" https://bugs.launchpad.net/bugs/1895563/+attachment/5410760/+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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1863234] Re: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863234 Title: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863234] Re: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863234 Title: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783337] Re: mididings fails to start
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: https://bugs.launchpad.net/ubuntu/+source/mididings/+bug/1783337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo
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 eoan ermine from disco dingo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo
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 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850099] [NEW] Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo
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 as I couldn't copy/paste the console output. Description:Ubuntu 19.10 Release:19.10 linux-image-5.3.0-19-generic I expect the kernel to load without a panic. The kernel panicked. After rebooting and selecting an older kernel, I was able to boot and load the old kernel without issue (5.0.0-32-generic) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lost 1947 F pulseaudio CurrentDesktop: XFCE Date: Mon Oct 28 00:52:26 2019 HibernationDevice: RESUME=UUID=0dba346e-043c-4e62-95a4-911a6a65e626 InstallationDate: Installed on 2016-06-17 (1227 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0WVDX2 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd10/03/2019:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA07:cvnDellInc.:ct9:cvr: dmi.product.family: Precision dmi.product.name: Precision 5510 dmi.product.sku: 06E5 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan ** Attachment added: "Picture of the panic." https://bugs.launchpad.net/bugs/1850099/+attachment/5300793/+files/20191027_234215.jpg -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842915] [NEW] installer crashed during installation of Ubuntu 19.04 from USB stick
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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 Date: Thu Sep 5 12:08:10 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842915 Title: installer crashed during installation of Ubuntu 19.04 from USB stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1842915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1274320] Re: Error: diskfilter writes are not supported
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 "Guided - use entire disk" option), which reduces disk manageability. I'm left with the impression installing Ubuntu on enterprise-grade hardware is a bit alpha. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274320 Title: Error: diskfilter writes are not supported To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1274320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1274320] Re: Error: diskfilter writes are not supported
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 fails to reboot\boot. Grub is v2.02-2ubuntu8.12. Any suggestions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274320 Title: Error: diskfilter writes are not supported To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1274320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772556] Re: Can't find apt-transport-https
@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: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1772556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822220] Re: package libnvidia-compute-410 (not installed) failed to install/upgrade: package libnvidia-compute-410:i386 (418.56-0ubuntu1) with field 'Multi-Arch: no' is not co-installable with l
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: package libnvidia-compute-410 (not installed) failed to install/upgrade: package libnvidia-compute-410:i386 (418.56-0ubuntu1) with field 'Multi-Arch: no' is not co-installable with libnvidia- compute-410 which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
@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. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
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] /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-modeset.o /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c: In function ‘nvidia_drm_lock_user_pages’: /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:140:5: warning: passing argument 6 of ‘get_user_pages’ makes pointer from integer without a cast [enabled by default] pages_pinned = NV_GET_USER_PAGES(address, pages_count, write, force, ^ In file included from include/linux/scatterlist.h:7:0, from include/linux/dma-mapping.h:10, from include/drm/drmP.h:37, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-os-interface.h:32, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:27: include/linux/mm.h:1222:6: note: expected ‘struct page **’ but argument is of type ‘int’ long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:140:5: warning: passing argument 7 of ‘get_user_pages’ from incompatible pointer type [enabled by default] pages_pinned = NV_GET_USER_PAGES(address, pages_count, write, force, ^ In file included from include/linux/scatterlist.h:7:0, from include/linux/dma-mapping.h:10, from include/drm/drmP.h:37, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-os-interface.h:32, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:27: include/linux/mm.h:1222:6: note: expected ‘struct vm_area_struct **’ but argument is of type ‘struct page **’ long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:140:5: error: too many arguments to function ‘get_user_pages’ pages_pinned = NV_GET_USER_PAGES(address, pages_count, write, force, ^ In file included from include/linux/scatterlist.h:7:0, from include/linux/dma-mapping.h:10, from include/drm/drmP.h:37, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-os-interface.h:32, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:27: include/linux/mm.h:1222:6: note: declared here long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ make[2]: *** [/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.o] Error 1 make[2]: Target `__build' not remade because of errors. make[1]: *** [_module_/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel] Error 2 make[1]: Target `modules' not remade because of errors. make[1]: Leaving directory `/usr/src/linux-headers-4.4.0-143-generic' make: *** [modules] Error 2 ERROR: The nvidia kernel module was not created. ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com. ** Attachment added: "nvidia-installer log file for -143 kernel" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+attachment/5249523/+files/nvidia-installer.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818049] Re: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’]
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. https://bugs.launchpad.net/bugs/1818049 Title: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1818049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818049] Re: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’]
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 to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1818049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820526] [NEW] linux-signed-generic-lts-xenial 4.4.0-143 depends on linux-generic instead of linux-generic-lts-xenial
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 packages will be installed:   linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic   linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic   linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic Suggested packages:   fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed:   linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic   linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic   linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic   linux-signed-generic-lts-xenial 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/60.2 MB of archives. After this operation, 275 MB of additional disk space will be used. Do you want to continue? [Y/n] apt-cache policy linux-signed-generic-lts-xenial shows dependency on linux-generic instead of linux-generic-lts-xenial. What I expected to happen is that the 3.x kernel bits wouldn't be installed. This may also be why building VirtualBox DKMS module is broken: Processing triggers for linux-image-4.4.0-143-generic (4.4.0-143.169~14.04.2) ... /etc/kernel/postinst.d/dkms: Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) Consult /var/lib/dkms/virtualbox/4.3.36/build/make.log for more information. ** Affects: linux-meta-lts-xenial (Ubuntu) Importance: Undecided Status: New ** 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 e.g. # sudo apt-get install linux-signed-generic-lts-xenial Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following extra packages will be installed: - linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic - linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic - linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic +   linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic +   linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic +   linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic Suggested packages: - fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools +   fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed: - linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic - linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic - linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic - linux-signed-generic-lts-xenial +   linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic +   linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic +   linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic +   linux-signed-generic-lts-xenial 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/60.2 MB of archives. After this operation, 275 MB of additional disk space will be used. - Do you want to continue? [Y/n] + Do you want to continue? [Y/n] apt-cache policy linux-signed-generic-lts-xenial shows dependency on linux-generic instead of linux-generic-lts-xenial. What I expected to happen is that the 3.x kernel bits wouldn't be installed. + + This also breaks building VirtualBox DKMS module: + + Processing triggers for linux-image-4.4.0-143-generic (4.4.0-143.169~14.04.2) ... + /etc/kernel/postinst.d/dkms: + Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) + Consult /var/lib/dkms/virtualbox/4.3.36/build/make.log for more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820526 Title: linux-signed-generic-lts-xenial 4.4.0-143 depends on linux-generic instead of linux-generic-lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1820526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820526] Re: linux-signed-generic-lts-xenial 4.4.0-143 depends on linux-generic instead of linux-generic-lts-xenial
** 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 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 packages will be installed:   linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic   linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic   linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic Suggested packages:   fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed:   linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic   linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic   linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic   linux-signed-generic-lts-xenial 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/60.2 MB of archives. After this operation, 275 MB of additional disk space will be used. Do you want to continue? [Y/n] apt-cache policy linux-signed-generic-lts-xenial shows dependency on linux-generic instead of linux-generic-lts-xenial. What I expected to happen is that the 3.x kernel bits wouldn't be installed. - This also breaks building VirtualBox DKMS module: + This may also be why building VirtualBox DKMS module is broken: Processing triggers for linux-image-4.4.0-143-generic (4.4.0-143.169~14.04.2) ... /etc/kernel/postinst.d/dkms: Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) Consult /var/lib/dkms/virtualbox/4.3.36/build/make.log for more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820526 Title: linux-signed-generic-lts-xenial 4.4.0-143 depends on linux-generic instead of linux-generic-lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1820526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803631] [NEW] Clicking an field in a webextension popup will cause popup to close
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 input text Expected behavior: My input shows up in text field Actual behavior: Extension popup closes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 63.0+build2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mymindstorm 1349 F pulseaudio BuildID: 20181023214826 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Nov 15 18:51:36 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-11-15 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.122.1 dev ens3 proto dhcp metric 100 169.254.0.0/16 dev ens3 scope link metric 1000 192.168.122.0/24 dev ens3 proto kernel scope link src 192.168.122.13 metric 100 IwConfig: lono wireless extensions. ens3 no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=63.0/20181023214826 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: ?-20180531_142017-buildhw-08.phx2.fedoraproject.org-1.fc28 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.11 dmi.modalias: dmi:bvnSeaBIOS:bvr?-20180531_142017-buildhw-08.phx2.fedoraproject.org-1.fc28:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.11 dmi.sys.vendor: QEMU ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Example webextension" https://bugs.launchpad.net/bugs/1803631/+attachment/5213238/+files/bug-example.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803631 Title: Clicking an field in a webextension popup will cause popup to close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1803631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550270] Re: Touchpad stops working randomly
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 + trackpoint unresponsive All of this seems to happen at random. Putting the machine into suspend and waking it up again will put it in a random state of working/not working. This behavior was not observed when running 17.04 or 16.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550270 Title: Touchpad stops working randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756226] Re: nvidia-driver-390 fails to start GUI
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 into GPU0. -- 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: nvidia-driver-390 fails to start GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756226] Re: nvidia-driver-390 fails to start GUI
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 'xorg-server' found' -- 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: nvidia-driver-390 fails to start GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756226] Re: nvidia-driver-390 fails to start GUI
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: nvidia-driver-390 fails to start GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756226] Re: nvidia-driver-390 fails to start GUI
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 configuration [22.370] (EE) NVIDIA(GPU-0): is not currently supported. Please add 'BusID [22.370] (EE) NVIDIA(GPU-0): "PCI:67:0:0"' to the SLI "Device" section in the X [22.370] (EE) NVIDIA(GPU-0): configuration file. [23.555] (EE) NVIDIA(GPU-0): Only one GPU will be used for this X screen. So I added that line to Xorg.conf, and now my screen keeps turning on and off. -- 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: nvidia-driver-390 fails to start GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756226] Re: nvidia-driver-390 fails to start GUI
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 either. So far nothing has resulted in video output. Will keep trying. -- 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: nvidia-driver-390 fails to start GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756226] Re: nvidia-driver-390 fails to start GUI
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: nvidia-driver-390 fails to start GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756226] Re: nvidia-driver-390 fails to start GUI
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. https://bugs.launchpad.net/bugs/1756226 Title: nvidia-driver-390 fails to start GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743710] Re: Ubuntu 16.04: since 2018 all dropdown menus black and unreadable
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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743710
Title:
Ubuntu 16.04: since 2018 all dropdown menus black and unreadable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1743710/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743710] Re: Ubuntu 16.04: since 2018 all dropdown menus black and unreadable
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743710 Title: Ubuntu 16.04: since 2018 all dropdown menus black and unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1743710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 kernel NULL pointer dereference at isci_task_abort_task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
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: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
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: Two-finger scrolling no longer works after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
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. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 NULL pointer dereference at isci_task_abort_task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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: Unable to handle kernel NULL pointer dereference at isci_task_abort_task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 isci_task_abort_task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 kernel NULL pointer dereference at isci_task_abort_task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727172] [NEW] package perl-base 5.26.0-8ubuntu1 failed to install/upgrade: package perl-base is already installed and configured
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 AptdaemonVersion: 1.1.1+bzr982-0ubuntu17 Architecture: amd64 Date: Mon Oct 23 17:18:08 2017 DuplicateSignature: package:perl-base:5.26.0-8ubuntu1 Unpacking libxml-parser-perl (2.44-2build3) over (2.44-2build2) ... dpkg: error processing package perl-base (--configure): package perl-base is already installed and configured ErrorMessage: package perl-base is already installed and configured InstallationDate: Installed on 2017-03-31 (207 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: dpkg Title: package perl-base 5.26.0-8ubuntu1 failed to install/upgrade: package perl-base is already installed and configured UpgradeStatus: Upgraded to artful on 2017-10-24 (1 days ago) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727172 Title: package perl-base 5.26.0-8ubuntu1 failed to install/upgrade: package perl-base is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1727172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727171] [NEW] package libstdc++6:amd64 7.2.0-8ubuntu3 failed to install/upgrade: package libstdc++6:amd64 is already installed and configured
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 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 AptdaemonVersion: 1.1.1+bzr982-0ubuntu17 Architecture: amd64 Date: Mon Oct 23 17:18:12 2017 Dependencies: gcc-7-base 7.2.0-8ubuntu3 libc6 2.26-0ubuntu2 libgcc1 1:7.2.0-8ubuntu3 ErrorMessage: package libstdc++6:amd64 is already installed and configured InstallationDate: Installed on 2017-03-31 (207 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: dpkg Title: package libstdc++6:amd64 7.2.0-8ubuntu3 failed to install/upgrade: package libstdc++6:amd64 is already installed and configured UpgradeStatus: Upgraded to artful on 2017-10-24 (1 days ago) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727171 Title: package libstdc++6:amd64 7.2.0-8ubuntu3 failed to install/upgrade: package libstdc++6:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1727171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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: Unable to handle kernel NULL pointer dereference at isci_task_abort_task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 isci_task_abort_task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
** 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. 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task
** 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: Unable to handle kernel NULL pointer dereference at isci_task_abort_task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726519] [NEW] Unable to handle kernel NULL pointer dereference at isci_task_abort_task
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 photo of the panic. In short, I can't boot using the latest artful aardvark kernel, and I have to boot with the latest zesty zapus kernel. :~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 linux-image-4.13.0-16-generic I expect this isn't normal and I should be able to boot with the new kernel, which I can't. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lost 2071 F pulseaudio /dev/snd/controlC2: lost 2071 F pulseaudio /dev/snd/controlC0: lost 2071 F pulseaudio CurrentDesktop: XFCE Date: Mon Oct 23 12:52:20 2017 HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6 InstallationDate: Installed on 2016-11-01 (355 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 11361Q0 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic root=/dev/mapper/xubuntu--vg-root ro quiet RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A3KT57AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: 573921 dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE: dmi.product.name: 11361Q0 dmi.product.version: ThinkStation C30 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful ** Attachment added: "lspci log" https://bugs.launchpad.net/bugs/1726519/+attachment/4988847/+files/lspci-vnvn.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: Unable to handle kernel NULL pointer dereference at isci_task_abort_task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718781] Re: qupzilla assert failure: *** Error in `qupzilla': double free or corruption (out): 0x00005609d7ba86d0 ***
** 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): 0x5609d7ba86d0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qupzilla/+bug/1718781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719212] Re: qupzilla assert failure: *** Error in `qupzilla': malloc(): memory corruption (fast): 0x0000556e0467d280 ***
** 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 (fast): 0x556e0467d280 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qupzilla/+bug/1719212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152756] Re: stale files in /var/lib/initramfs-tools after removing kernel
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/152756 Title: stale files in /var/lib/initramfs-tools after removing kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/152756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709492] Re: lubuntu-next has broken website link in the slideshow
*** 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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709492 Title: lubuntu-next has broken website link in the slideshow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1709492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713836] [NEW] qupzilla crashes upon entering second level domains in the address bar
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 http://archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status Description:Ubuntu Artful Aardvark (development branch) Release:17.10 I expected this to go to the second level domain website instead I had it start to load the page and then crash two second later. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: qupzilla 2.1.2~dfsg1-2ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: LXQt Date: Tue Aug 29 21:41:50 2017 LiveMediaBuild: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 (20170829) SourcePackage: qupzilla UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qupzilla (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713836 Title: qupzilla crashes upon entering second level domains in the address bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qupzilla/+bug/1713836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707691] Re: [xenial] xserver-xorg-dev should depend on libxfont1-dev
"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 Ubuntu. https://bugs.launchpad.net/bugs/1707691 Title: [xenial] xserver-xorg-dev should depend on libxfont1-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/1707691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709492] [NEW] lubuntu-next has broken website link in the slideshow
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:Ubuntu Artful Aardvark (development branch) Release:17.10 ubiquity-slideshow-lubuntu: Installed: 127 Candidate: 127 Version table: *** 127 500 500 http://archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status I expected the the installer to launch a webbrowser instead I did not get the launch of a webbrowser. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity-slideshow-lubuntu 127 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: LXQt Date: Tue Aug 8 15:28:48 2017 Dependencies: LiveMediaBuild: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 (20170808) PackageArchitecture: all SourcePackage: ubiquity-slideshow-ubuntu UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity-slideshow-ubuntu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709492 Title: lubuntu-next has broken website link in the slideshow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1709492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706789] [NEW] installer crashed grub-efi signed not installed
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 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Description:Ubuntu Artful Aardvark (development branch) Release:17.10 I expected this install to work with secure boot like it should instead it did not install a signed version of grub so no bootloader points to the new install meaning the new install cannot immediately be booted into. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.6-0ubuntu4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: LXQt Date: Wed Jul 26 14:52:35 2017 LiveMediaBuild: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706789 Title: installer crashed grub-efi signed not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1706789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
