StacktraceTop:
QMessageLogger::fatal(char const*, ...) const () from
/tmp/apport_sandbox_hRTQ09/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
qt_assert(char const*, char const*, int) () from
/tmp/apport_sandbox_hRTQ09/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
UbuntuOpenGLContext::~UbuntuOpenGLContex
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1606375/+attachment/4707350/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606375
Title:
Scopes just r
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584557
Title:
Seagate external drive causes SCSI bus resets when UAS enabled
To
This time, it's a laptop. Old one with amd cpu and 911 nvidia GPU.
Nvidia driver 340.
Gnome-software opens and asks for update so every package can be
displayed.
I installed updates, removed nvidia driver (nouveau is more stable on
this old machine), installed vlc, ffmpeg, libavcodec-extra, libav
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS clie
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS clie
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: acce
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: acce
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS clie
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS clie
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: acce
*** This bug is a duplicate of bug 1069133 ***
https://bugs.launchpad.net/bugs/1069133
Reviewing the files from your upgrade attempt you seem to have enabled a
PPA that provides Xorg packages. This will prevent the upgrade as that
PPA contains different versions of packages essential to Ubuntu
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: acce
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
*** This bug is a duplicate of bug 1588946 ***
https://bugs.launchpad.net/bugs/1588946
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: a
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
You're right, I had mistakenly installed that specific kernel image from
the kernel ppa, but never booted into it. Is that why it decided to
install the i386 metapackage?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: acce
*** This bug is a duplicate of bug 1069133 ***
https://bugs.launchpad.net/bugs/1069133
Reviewing the files from your upgrade attempt you seem to have enabled a
PPA that provides Xorg packages. This will prevent the upgrade as that
PPA contains different versions of packages essential to Ubuntu
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS clie
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: acce
This bug was fixed in the package debian-installer - 20101020ubuntu467
---
debian-installer (20101020ubuntu467) yakkety; urgency=medium
[ dann frazier ]
* arm64/cdrom: add virtio-modules for QEMU installs (LP: #1605407)
[ Adam Conrad ]
* Move master kernels to 4.4.0-33.
--
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
*** This bug is a duplicate of bug 1605716 ***
https://bugs.launchpad.net/bugs/1605716
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[
*** This bug is a duplicate of bug 1605709 ***
https://bugs.launchpad.net/bugs/1605709
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: a
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS clie
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
I tried an install with manual partitioning, and made a seperate 1 GB
ext2 /boot/ partition. Interestingly enough, the automatically created
/etc/yaboot.conf worked fine!
Are there any known issues regarding yaboot & ext4 & partition size?
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1605715 ***
https://bugs.launchpad.net/bugs/1605715
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu:
*** This bug is a duplicate of bug 1069133 ***
https://bugs.launchpad.net/bugs/1069133
Reviewing the files from your upgrade attempt you seem to have enabled a
PPA that provides Xorg packages. This will prevent the upgrade as that
PPA contains different versions of packages essential to Ubuntu
I have noticed the same problem for the first time today at work (so no
commercial USA ISP).
I tried to strace the process to see what it does:
sudo strace -T -p 13921
strace: Process 13921 attached
restart_syscall(<... resuming interrupted poll ...>
But I got no insight.
--
You received this bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-system-compositor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523
The file /var/log/dist-upgrade/apt-term.log would be useful too.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586789
Public bug reported:
Brand new install of unity8, login and scopes/dash restart every few
seconds. It never stabilizes.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: unity8 8.13+16.10.20160714-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generi
We don't use a shim version that currently carries this commit; why are
you using a new shim? Is there another issue for which you require a
patch?
Please include the full output of 'efibootmgr -v' on an affected system
so we can make sure that the boot entry is correctly configured to do
the firm
Hello Dave, or anyone else affected,
Accepted debian-installer into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu318.40 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Not sure how to submit the SRU request. The page linked above talks
about verifying patches, and there are none attached to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606030
Title:
Sys
See bug 1509305 for some background regarding the
"_get_linux_metapackage" function.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Description changed:
So, this is what happenes:
1) Set an alarm
2) When it goes on, press snooze
3) Delete the alarm
4) after the 10 minutes from the original time, it rings again
+
+
+ It looks also strange that even if alarm is Snoozed then it looks like to be
turned off.
**
In VarLogDistUpgradeMainlog.txt we can see the following:
2016-05-29 11:36:01,240 INFO installing linux metapackage: linux-generic:i386
2016-05-29 11:36:01,241 DEBUG Installing 'linux-generic:i386' (linux
metapackage may have been accidentally uninstalled)
The function "_get_linux_metapackage" f
That might not really be the useful bit - but rather the xapian data in
/var/cache/app-info. Can you just tar up the whole directory and attach it?
On Mon, Jul 25, 2016, 14:05 ZHANG Erkang wrote:
> I didn't find yamls, this is the xml file of fwupd
>
>
>
>
>
> com.dell.uefi124c207d.firm
> solved like this.
> /usr/lib/python3/dist-packages/provisioningserver/utils/sshkey.py:149:
> ("setsid", "-w", "ssh-keygen", "-i", "-f", str(keypath)),
FWIW, this exact fix is in ppa:maas/next. Not sure where else it's meant
to be right now.
--
You received this bug notification because you are
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561912
Title:
package libgsettings-qt1 0.1+14.10.20140807-0ubuntu4 failed to
install/upgrade: subprocess instal
*** This bug is a duplicate of bug 1069133 ***
https://bugs.launchpad.net/bugs/1069133
Reviewing the files from your upgrade attempt you seem to have enabled a
PPA that provides Xorg packages. This will prevent the upgrade as that
PPA contains different versions of packages essential to Ubuntu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606367
Title:
package guitarix-common 0.35.0-1 failed to install/upgrade: trying to
overwrite '/usr/share/gx_he
So the panic does not happen anymore with the 4.4.0-31 kernel?
Can you open a new and separate bug report for your wireless issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605731
Title:
Kerne
** Branch linked: lp:ubiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560162
Title:
Xenial: scaling is horribly out on xps13 install session
To manage notifications about this bug go to:
htt
** Package changed: ubuntu-release-upgrader (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/1589975
Title:
Ubuntu 16.04 has Networking problems
To manage notifications about this b
In theory this is fine, but in practice will need more work.
For instance, in your examples grubx64.efi is being installed as the EFI
binary to run -- this is wrong, since grubx64.efi is only signed by the
Canonical keys, not by Microsoft keys, and so will fail to boot in a
Secure Boot scenario.
** Branch linked: lp:~ubuntu-core-dev/debian-installer/trusty-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604441
Title:
D-I on 16.04.1 breaks on usb probe and networking setup on secureb
Not message in kernel 4.7
** Attachment added: "dmesg_4.7.0-040700-lowlatency"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605782/+attachment/4707325/+files/dmesg_4.7.0-040700-lowlatency
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a m
I'm receiving constant toshiba_acpi: Unknown event received 93 ,but I'm
not really experiencing any issues. Anything I can do to assist, I'd
like to clear this as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Branch linked: lp:ubiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600308
Title:
ubiquity targets invalid device name with nvme disks, fails to install
grub
To manage notifications abou
Public bug reported:
problem while updating
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: guitarix-common 0.35.0-1
ProcVersionSignature: Ubuntu 4.4.0-33.52-lowlatency 4.4.15
Uname: Linux 4.4.0-33-lowlatency x86_64
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
Date: Mon Jul 25 16:
Hello Scott, or anyone else affected,
Accepted livecd-rootfs into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.208.13 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status:
Ahh, yes it was. Comment 8 is a duplicate request, sorry about that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603810
Title:
Ubuntu turns monitor permanently off during boot
To manage notific
** Branch linked: lp:~ubuntu-core-dev/livecd-rootfs/trusty-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568918
Title:
Add support for lts-xenial kernel flavours in trusty
To manage notif
This does appear to be an Ubuntu specific kernel. I'll build an Ubuntu
kernel based on 4.0 and post a link to it for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603810
Title:
Ubuntu turn
This bug was fixed in the package gvrng - 4.4-2
Sponsored for Hans Joachim Desserud (hjd)
---
gvrng (4.4-2) unstable; urgency=medium
* QA upload.
* Declare compliance with Debian Policy 3.9.8.
* Use compat level 9 and require debhelper >= 9.
* Remove quilt from Build-Depends.
clang in 15.04 and 16.04 LTS is pretty unusable without this patch.
Linking against precompiled (with the gcc toolchain) system libraries
fails.
There are also multiple affected users in this closely related bug:
https://bugs.launchpad.net/ubuntu/+source/llvm-
toolchain-3.8/+bug/1488254
--
You
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
*** This bug is a duplicate of bug 1605291 ***
https://bugs.launchpad.net/bugs/1605291
** This bug has been marked a duplicate of bug 1605291
please merge llvm-toolchain-3.8 from Debian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: llvm-toolchain-3.8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488254
I removed that kernel and installed it again. This time, it didn't
panic, but Wireless connection does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605731
Title:
Kernel 4.4.0-31 Causes k
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: llvm-toolchain-3.8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605291
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0
Can you submit an SRU request[0] to the kernel team mailing list:
kernel-t...@lists.ubuntu.com
[0] https://wiki.ubuntu.com/StableReleaseUpdates
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received thi
** Changed in: livecd-rootfs (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Adam Conrad (adconrad)
** Changed in: livecd-rootfs (Ubuntu Trusty)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Adam Conrad (adconrad)
--
You received this bug notification because you are a mem
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0
Wasn't testing with 3.16 and 3.19 ubuntu patched kernels enough to disprove
the grub theory?
Jason
On Mon, Jul 25, 2016 at 1:44 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Can you see if the bug still happens when booting a Trusty kernel on the
> Xenial system? This can be d
livecd-rootfs changes have been tested and compared in a PPA. Will re-
compared after the SRU is in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568918
Title:
Add support for lts-xenial kernel f
Hi!
I tried to start simple scan with
#SANE_NET_HOSTS=XXX.XXX.XXX.XX simple-scan
and after some time it actually started, using the network scanner on
XXX.XXX.XXX.XX, using a saned process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
@ernst:
Many, many thanks for the details . . . I can see numerous "errors" showing
up as the OS loads, including something about the "r128" "failing," I think
we've discussed some of these things before . . . but, since for the most
part "things were working" I didn't mess with it.
But, indeed,
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
Also, can you grab a screen shot or take a digital picture of the panic?
Then attach it to the bug for review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605731
Title:
Kernel 4.4.0-31 Causes ker
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605782
Title:
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
FI
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
201 - 300 of 784 matches
Mail list logo