** Package changed: ubuntu => linux (Ubuntu)
** Summary changed:
- Mainline kernel build failure - 5.2, 5.1.17
+ Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank Dmitrii,
it looks ready for uploads now - Eoan at first and once complete there into the
SRU queue.
For now I sponsored the Eoan upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833299
Hrm, why didn't this component-mismatch when migrating, I must have missed
something:
>From build [1]:
1. qemu-system-arm
Recommends: ... qemu-efi-aarch64, qemu-efi-arm
But:
qemu-system-arm | 1:4.0+dfsg-0ubuntu4| eoan
qemu-efi-aarch64 | 0~20190606.20d2e5a1-1ubuntu2 |
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827790
Title:
Dell XPS 13 9380 - Screen brightness
** Package changed: mutter (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Package changed: xorg-server (Ubuntu) => gnome-settings-daemon
(Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => New
--
You received this
Merge request submitted for Eoan:
https://code.launchpad.net/~wxl/usb-creator/usb-creator/+merge/370094
** Changed in: usb-creator (Ubuntu Eoan)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the inquiry, vanvugt. I'm trying an Ubuntu on Wayland session
this evening and the brightness flashing has continued with about the
same frequency.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for console-setup (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: console-setup (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-signed (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-signed (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824407
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
[Expired for network-manager-openvpn (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: network-manager-openvpn (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[SRU]
[Impact]
Unlike usb-creator-gtk, which has a different codebase, usb-creator-kde
has long been non-functional, getting stuck immediately upon launching.
This means that for Kubuntu, post-18.04 Lubuntu, and any user who
chooses to use
Something like this http://cdimages.ubuntu.com/lubuntu/daily-
live/current/?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827417
Title:
Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen
Please raise the issue to linux-bt...@vger.kernel.org, and let btrfs
maintainers know this commit causes the regression:
commit 31d11b83b96faaee4bb514d375a09489117c3e8d
Author: Filipe Manana
Date: Wed May 9 16:01:46 2018 +0100
Btrfs: fix duplicate extents after fsync of file with prealloc
Public bug reported:
The mainline kernel builds on kernels.ubuntu.com are in failed state for
the latest kernel versions.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.17/
Okay, I finally realized that it was my self-built libgcrypt that causes
the issue.
** Changed in: gnupg2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775783
I am super new to linux. I have read through the thread, and I am pretty sure
that my ASUS ZenBook is having the same problem. I re-installed Ubuntu and have
just not upgraded, but I not happy with that workaround. So, will this be
something that will be fixed with a future update? Or, will I
I can't test that with the same conditions, it no longer affects me,
nobody else marked "it affects me", and a lot happened since then (the
ticket is against 15.04), so I suggest closing this as won't fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am experiencing this problem on Ubuntu Mate 18.04.2 reading/writing
the
/DCIM/Camera
folder on a Samsung Galaxy S5 mini with Android 6.0.1
The first ~250 of 550 jpg images copy successfully, then file the
operation window freezes and does not respond to clicking the cancel
button.
Hi, @wjbarid,
In order to determine the right hardware spec on your device, please
attach `sudo lspci -vvnnk` output. It will contains subsystem ID that
can be used to find the right iwlwifi model.
For bluetooth firmware blob name, you should try:
1. clone
** Tags removed: verification-needed-bionic verification-needed-cosmic
verification-needed-disco
** Tags added: verification-done-bionic verification-done-cosmic
verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux-meta (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/1836291
Title:
Hi Matthew,
I think that's a valid point to mark this bug as a Won't Fix for X
(which applies to T as well).
Thanks for working on this one.
I will bring this to the LTP, to see if we can skip this one with older kernels.
** Changed in: linux (Ubuntu Trusty)
Status: Triaged => Won't Fix
** Summary changed:
- Missing NIC driver for Armada 8040 (Macchiatobin)
+ Enable NIC driver for Armada SOCs in disco/generic arm64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835054
Title:
installed (for testing purposes)
guiverc@d960-ubu2:/de2900/ubuntu_64$ sudo apt install
'usb-creator-kde=0.3.6~ppa1' 'usb-creator-common=0.3.6~ppa1'
...
guiverc@d960-ubu2:/de2900/ubuntu_64$ apt-cache policy usb-creator-kde
usb-creator-kde:
Installed: 0.3.6~ppa1
Candidate: 0.3.6
Version
Does the problem occur in only Xorg sessions ("Ubuntu") or Wayland too
("Ubuntu on Wayland")?
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Incomplete
** Also affects: mutter (Ubuntu)
Importance: Undecided
** Tags added: bionic
** Summary changed:
- No HDMI sound after suspend/resume on 16.04
+ No HDMI sound after suspend/resume
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718927
Title:
No HDMI
*** This bug is a duplicate of bug 1718927 ***
https://bugs.launchpad.net/bugs/1718927
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1718927, so it is being marked as such. Please
Please be careful to only report one issue per bug. It sounds like there
are multiple issues here. Which issue would you like this bug to be
about, and which web browser are you using?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You
The attachments show that pulseaudio was not running when the bug was
reported in 2014. That's why things seem to disappear in the GUI:
!!Sound Servers on this system
!!
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - No
Please let us know if
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1836051
When reporting bugs in the future please use apport by using 'ubuntu-
I have provided a fix in:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/qemu/+git/qemu/+merge/369470
And provided that patchset package in PPA:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1828495?field.series_filter=disco
I think we're good now, will test it in my new
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: virtualbox (Ubuntu)
Status: Invalid => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830961
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Also affects: tlp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: tlp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 508522 ***
https://bugs.launchpad.net/bugs/508522
Eric, it sounds like you're right about the "true bug".
However I also feel this bug report as it was originally worded is not
really any different to bug 508522.
I suggest the right thing to do here is to:
Yes the upstream bug link (I just fixed up) is showing it was fixed in
gdm3 version 3.27.91, so before 18.04 was released.
** Bug watch added: bugzilla.gnome.org/ #793609
https://bugzilla.gnome.org/show_bug.cgi?id=793609
** Changed in: gdm
Importance: Medium => Unknown
** Changed in: gdm
The formal fix is awaiting review;
https://gitlab.gnome.org/GNOME/mutter/merge_requests/600
but you can download it as a patch:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/600.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hey Christian:
Checking out my merge requests from:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/qemu
You can see that the upstream commit:
https://github.com/qemu/qemu/commit/4c257911dcc7
Is the same in the QEMU Bionic MR:
Invalidated per OP.
** Changed in: lubuntu-meta (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581321
Title:
Lubuntu 16.04 Cannot connect to WiFi
To
Well, this was a LONG time ago, and I must have figured out how to get around
the bug, or the bug was fixed, but...
It seems to me that reporting not being able to get Wi-Fi to work, when it had
worked perfectly well in all [L]Ubuntu versions I had used previous to 16.04
(with no fiddling at
** Changed in: linux-oem (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834550
Title:
System hangs after play video from thunderbolt HDD
** Changed in: linux-firmware (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: linux-firmware (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [SRU]
+
+ [Impact]
+
+ Unlike usb-creator-gtk, which has a different codebase, usb-creator-kde
+ has long been non-functional, getting stuck immediately upon launching.
+ This means that for Kubuntu, post-18.04 Lubuntu, and any user who
+ chooses to use
Well, I patched everything and put it in a PPA if folks want to test:
https://launchpad.net/~wxl/+archive/ubuntu/staging/+packages
** Summary changed:
- usb-creator-kde shows the install popup after a few seconds of launching
without any input
+ [SRU] usb-creator-kde shows the install popup
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04
I have this problem using Alienware 17 R2 with Nvidia 970M Graphic card
and ubuntu 19.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774950
Title:
Suspend fails in Ubuntu and Kubuntu 18.04 but
I tested in 18.04.2, an upgraded 18.04 from 16.04 and 16.04 and I had
the same results. That I said, I must be doing something wrong. Here's
what I did:
1. Enable "SSH Key Agent" in the "Autostart" section of lubuntu-default-apps
1. Run `ssh-keygen`
1. Reboot
1. Run `ssh-add -l`
I'll notice
Public bug reported:
I got an error on Ubuntu 10.04 while installing the package
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-kernel-common 20080825+1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21
Uname: Linux 2.6.32-38-generic i686
Architecture:
Public bug reported:
Now I very meticulously cleaned the hard drive with gparted, created a GPT
partition table, created a FAT32 partition of 500MB and set both ESP and BOOT
flags, and then created the rest of the partitions I wanted, including a SWAP.
I then chose "Do something else" and there
see above.
** Attachment added: "Screenshot_2019-07-14_22-03-01.png"
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1836509/+attachment/5277044/+files/Screenshot_2019-07-14_22-03-01.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Seems the file screendump I tried to attach didn't make it through, so trying
again.
These screendumps shows both the gparted when the EFI partition was created,
and the installer partition tables when trying to install.
** Attachment added: "Screenshot_2019-07-14_22-01-28.png"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kubuntu-meta (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/1817418
Is this issue still happening? I think it was fixed in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749481
Title:
Wrong session marked as selected in session dropdown on login screen
To
Public bug reported:
What details are there that wasn't gathered bu the bug-report tool?
I have tried both with the efi-partition that was left by earlier Windows
installation, and that which is supposed to be made by the Ubuntu installer
itself, and even tried to make one with gparted, and
Public bug reported:
This machine Lenovo H-454 fails to recover from Suspend
Screen blacks and stays that way. Monitor shows power off.
Indicator shows no hard drive activity
Requires a hard (power-off) shut-down and restart after which there
are a lot of orphaned inodes and finally a login
The documentation is a little bit confusing here -- the "HintSystem"
property is not about the device access or filesystem permissions, it's
about "accessing" UDisks functions using PolicyKit.
See the policies here [1] for mounting filesystems -- "normal" devices
can be mounted by a "regular"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: update-notifier (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/1836475
Then I guess we will mark this as invalid since Xenial is no longer
supported by the Lubuntu team.
** Changed in: lubuntu-meta (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unable to reproduce issue using latest Lubuntu 18.04 i386 alternate ISO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529314
Title:
Newly installed Xenial (encrypted LVM) will not boot
To manage
Public bug reported:
0) run bionic ver 18.04.1 in vmware player VM-machine ver 15.04
Everything worked fine until today when updating.
open-vm-tools has version 3.5.7 (working)
1) Ubuntu 18.04.2 LTS Release: 18.04
2) apt-cache policy open-vm-tools
open-vm-tools:
Installerad:
Public bug reported:
[18.04 amd64]
HintSystem (which can be set by a udev rule with ENV{UDISKS_SYSTEM}="1")
is supposed to "require additional permissions to access" [0] but there
is no difference in the mount permissions when it is set:
# UDISKS_SYSTEM=0
$ udisksctl info -b /dev/sr0
I re-installed the default kernel using the following command:
$ sudo apt install --reinstall linux-image-5.0.0-20-generic
then installed the latest linux-firmware as directed above,
and now bluetooth is broken again, same as before. I guess this means that your
fix is required Kai-Heng.
Thanks
** Attachment added: "bionic build & autopkgtest log"
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1836496/+attachment/5277023/+files/redis-bionic.log
** Description changed:
- Two CVEs have been published, I'm merging the patches from buster-
- security.
+ [Affected]
+
** Attachment added: "xenial build & autopkgtest log"
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1836496/+attachment/5277024/+files/redis-xenial.log
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-10192
--
You received this bug notification because you are a
** Attachment added: "disco build & autopkgtest log"
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1836496/+attachment/5277022/+files/redis-disco.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1836497
and then change the status of the bug to 'Confirmed'.
If, due to the
** Patch added: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1836496/+attachment/5277018/+files/redis-disco.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836496
Public bug reported:
84 | {
| ^
/home/kernel/COD/linux/scripts/mod/devicetable-offsets.c: In function 'main':
/home/kernel/COD/linux/scripts/mod/devicetable-offsets.c:10:1: error:
'-mindirect-branch' and '-fcf-protection' are not compatible
10 | {
| ^
make[4]: ***
** Patch added: "redis-bionic.diff"
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1836496/+attachment/5277019/+files/redis-bionic.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836496
** Patch added: "redis-xenial.diff"
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1836496/+attachment/5277020/+files/redis-xenial.diff
** Changed in: redis (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Reading the git branches and the Debian uploads, CVE-2019-10193 does not
affect xenial and bionic.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-10193
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Be advised that it is dangerous to use fscrypt without umask 077, as any
user can read the contents of any file you access even if they don't
have the security token.
https://github.com/google/fscrypt/issues/132
** Bug watch added: github.com/google/fscrypt/issues #132
If all goes well today. It's been on my TODO list for a while, but
things keep on getting piled on top.
** Also affects: usb-creator (Ubuntu Eoan)
Importance: High
Assignee: Walter Lapchynski (wxl)
Status: Triaged
--
You received this bug notification because you are a member of
Yes, I still have this issue even if I had upgraded my host to latest
debian buster. This issue maybe related to seabios + i440fx, I can get
normal dispaly with seabios + q35.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a security vulnerability ***
Public security bug reported:
Two CVEs have been published, I'm merging the patches from buster-
security.
** Affects: redis (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
I see people are still encountering this bug. When is it likely to be fixed?
https://askubuntu.com/a/1158252/612
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629715
Title:
usb-creator-kde shows
Actually squashfuse_ll is being installed, it is renamed in this patch:
https://salsa.debian.org/sgclark-guest/squashfuse/blob/master/debian/patches/install_squashfuse_lowlevel.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking as invalid. Talked to Lyn and she said that the original
hardware is gone, so can't test it on that. Additionally, she tried on
other hardware and couldn't reproduce.
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Invalid
** Changed in: xserver-xorg-input-mouse (Ubuntu)
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1836440
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
dministrador@administrador-pc:~/Descargas/alarm-clock-applet-0.3.4$ sudo
apt-get install libglib2.0-dev libgtk2.0-dev libgconf2-dev
libgstreamer1.0-dev gnome-icon-theme libnotify-dev intltool
./configure :
*
alarm-clock 0.3.4
The custom kernel has a fix for this particular issue. Please use the
default kernel to test latest firmware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832988
Title:
Intel 8260 Bluetooth not
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836440
Marked invalid per OP's comment above.
** Changed in: lubuntu-meta (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511156
Title:
After upgrade to
Thanks Kai-Heng,
I installed the latest firmware as you described and bluetooth works.
Please note I didn't uninstall the custom kernel from before. I don't know if
this matters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277003/+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/1836491
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277010/+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/1836491
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277007/+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/1836491
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277004/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277012/+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/1836491
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277008/+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/1836491
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277016/+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/1836491
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277014/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836491
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277013/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836491
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277015/+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/1836491
Title:
Updated hardinfo.html to show current kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Attachment added: "hardinfo_report.html"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836491/+attachment/5277001/+files/hardinfo_report.html
** Tags added:
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277002/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836491
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1836491/+attachment/5277011/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 170 matches
Mail list logo
