This bug is still present on latest Saucy Salamander 3.11.0-3.
On the same WPA encrypted network:
Precise on the same hardware boots up and connects automatically.
Nook HD+ boots up and connects autmatically even faster.
Asus Transformer TF101 boots up and connects automatically.
Samsung Galaxy
Bug still present on saucy. Ubuntu network manager policy is not user friendly
-
Precise connected fairly quickly after power up to wireless WPA encrypted
network.
Nook connects immediately on power up to wireless WPA encrypted network.
Chromebook connects immediately on power up to wireless
Public bug reported:
org.freedesktop.DBus.Python.gi._glib.GError: Traceback (most recent call last):
File /usr/lib/python3/dist-packages/dbus/service.py, line 707, in
_message_cb
retval = candidate_method(self, *args, **keywords)
File /usr/share/usb-creator/usb-creator-helper, line 239,
Public bug reported:
(gtk-update-icon-cache-3.0:5066): GdkPixbuf-WARNING **: Cannot open
pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
This likely means that your installation is broken.
Try running the command
Thanks for looking at this bug.
I ran the three apt-get commands you mention. Clean no reported
problem.
I then ran the commands that failed yesterday:
sudo apt-get update
sudo apt-get dist-upgrade
Clean, no reported problem.
As of today the bug is not reproducible so it can be marked
Public bug reported:
I've been running tahr on tower, notebook, netbook both 32 bit and 64 bit for
months and installs every few weeks.
Suddenly on one of the pc's but not the others after update a couple of days
ago this
Enter password for keyring Default to unlock
shows up on boot and boot
Thanks, how do I turn the bot off, or how do I keep this message from
coming up on each and every boot?
I just found an ubuntu setting about online accounts which I turned
off. Let me reboot and see if that helped.
If I want to access my google accounts I log on to gmail. Google is
absolutely
Public bug reported:
jerry@Aspire1:~$ ubuntu-bug linux
tail: cannot open ‘/var/log/syslog’ for reading: No such file or directory
Took a look, there is no syslog. In spite of all this on the screen
ubuntu-bug does work:
jerry@Aspire1:~$ jerry@Aspire1:~$ ubuntu-bug linux
jerry@Aspire1:~$:
Online accounts is turned off, rebooted, and still get a message about
entering keyring password four times in succession which I cancel.
?
How do I turn this keyring password message off, or else at least set
the password (how) so I don't interrupt every power on for this message?
Thanks.
--
Updated as of today, 12 March, rebooted, still no syslog. Not much in
/var/log:
jerry@Aspire1:~$ ls /var/log
boot.log dmesggpu-manager.log pm-powersave.log udev
cups dmesg.0 lightdm samba Xorg.0.log
--
You received this bug notification because you are a
Public bug reported:
First time, with chromium browser up and using brasero to blank a CD,
got a kernel panic. Complete stop to text screen wouldn't do a thing.
Lots of stuff on the screen no way to copy it all short of a digital
camera.
Second time, no browser up, using brasero to blank a CD,
Sorry, I don't see anything in the kern logs relevant.
This tahr install was done on April 10 with the then current zsync.
I updated tahr on April 14 after the subject bug. I've repeated the
actions that caused the bug, and tahr hasn't failed since with the same
original setup.
At this point
Public bug reported:
.iso 20140718 (and 17) boot to background, two flashing icons, no
desktop. Ctrl-Alt-F1 and tried ubuntu-bug which said there were missing
packages.
Lenovo M58p:
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03)
I've been trying every day to boot utopic .iso since I filed this bug.
Daily-live current image 20140720 finally booted and installed
successfully.
At this point the bug is not reproducible so could be marked solved
however that is done.
--
You received this bug notification because you are a
Public bug reported:
Firefox running fine.
Installed Chromium from synaptic.
Trying to log into google mail.
I can type in password, however the email field will not accept any keyboard
input. I'm using the keyboard here.
Can't enter anything in URL field either.
I just did an update,
Re-booted a couple times. First time I enter into the URL field it
works, in this case google mail, subsequently I can highlight into the
field but the URL field no longer accepts input.
Let me try utopic 64. I've been using google chrome there, but I can
install chromium too.
--
You received
Re-booted a couple times. First time I enter into the URL field it
works, in this case google mail, subsequently I can highlight into the
field but the URL field no longer accepts input.
Let me try utopic 64. I've been using google chrome there, but I can
install chromium too.
I did install
Whole lot easier for me: Install Google Chrome for Linux.
Google Chrome works just fine for me. Chromium does not.
A screw up on burning flash might kill the netbook.
Best thing for me is to use Google Chrome instead of Chromium.
Thanks for your attention.
I'm using 32 bit utopic lubuntu on
Booted same lubuntu utopic on Compaq:
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Intel(R) Celeron(R) D CPU 3.33GHz
stepping: 5
microcode : 0x7
cpu MHz : 3325.135
cache size : 512 KB
Chromium gets the identical problem,
Christopher, I'm trying to file a new report so I re-created the bug.
Right now Launchpad will show me other bugs however no place I can find
to say none of these I want to enter a new bug or words to that
effect.
--
You received this bug notification because you are a member of Kernel
Public bug reported:
Having problems just lately with tahr. It's been running fine for months.
Screen wil lock up. Ctrl-Alt-F1 log in, doesn't ask for password. Have to
reboot.
Does not reboot successfully.
Do an e2fsck from another partition comes up clean, no errors.
Now tahr boots, but no
Attached is cat/proc/cpuinfo
Reason for looking for syslog is tahr has locked up with some kind of
disk error on two different hard drives and three partitions. As I
remember the last time there was a syslog it said something about
running e2fsck which I did, and showed no errors. Rebooted and
Did yet another zsync from cdimage on 14 February and install on a different
hard drive and partition.
Still no syslog.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1280287
Title:
Problem does not exist on 3 March daily build. Syslog is there O.K. so
bug is solved.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1280287
Title:
tahr /var/log/syslog missing?
Public bug reported:
Updated unity, boots to background only.
Unity will not start. Boot recovery mode no help.
Did Ctrl-Alt-F1 ubuntu-bug linux, did K to keep report,
Booted another partition 14.10 and did ubuntu-bug /tmp/apport* to
generate this ubuntu-bug.
ProblemType: Bug
DistroRelease:
Thanks for looking at this bug.
Multiple attempts at update, boot in recovery, finally able to boot into
Unity O.K.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1355771
Title:
Utopic
Public bug reported:
zsync'd utopic today, booted and all that appears is wallpaper. No panels, no
icons, no applets, nothing.
Ctrl-Alt-F1 did ubuntu-bug linux,
Copied /tmp/apport* to a partition on the hard drive
then did:
ubuntu-bug apport*
to report this bug.
model name : Intel(R)
Booted today's zsync of utopic.iso
Wallpaper only. No unity.
+bug/1356357
No way to re-install utopic.
Is there a start unity or anything to get the panels and applets
running?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hmm, what is a bot?
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1356357
Title:
utopic .iso 20140813 boots to wallpaper no panels
Status in “linux” package in Ubuntu:
Comment #5
3.16.0-5 booted O.K. on the utopic that updated to 3.16.0-7 and got the
wallpaper failure with the -7. The -5 runs O.K.
Both kernels were still in the /boot folder.
The other utopic partition is a new install with wallpaper failure and
there's no prior kernels, only -7.
How
Installed kernel -6 on the .iso install that only has -7 kernel
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc6-utopic/
Seemed to install, also got the same problem wallpaper only no unity
panels.
In sum:
proper boot from utopic with kernel -5
wallpaper only no panels from utopic -5
Found an usb drive with -6 linux image. Booted ran fine.
-8 from update will rarely start unity. -7 never boots to panels.
BTW, Xorg seems to be running the screen fine. Starting unity gets many
lines of errors but I don't know what log these might be stored in - I
haven't found any of these
Tried several boots at linux image -8 level. Then got a compiz error
see Bug #1357753
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1356357
Title:
utopic .iso 20140813 boots to
Tried several boots at linux image -8 level. Then got a compiz error
see Bug #1357753
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1356357
Title:
utopic .iso 20140813 boots to
Plowed thru a screenful of messages when starting unity and saw the line
near the top:
Your hardware does not support unity
or words to that effect.
This hardware is Intel Core 2 Duo on a Lenovo Think Centre. Main line
hardware if there ever was.
Strange, unity on the linux-image -5 Unity
Bug #1357746 is in the same area. Compiz and unity fail to start on
later kernels while the -5 kernel on the same utopic runs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1356357
Public bug reported:
Intel Core 2 Duo 3 gHz 4 gb Lenovo Think Centre.
Boots 3.16.0-6 amd64 fine, runs compiz 3D fine.
Today's amd64 iso download, 20 August, boots to desktop cursor.
No unity.
Did ubuntu-bug from command line on the booted iso, saved report.
Booted 3.10.0-6 and ran
Just installed 3.16.0-6 .iso and upgraded today to 3.16.0-10.
Both kernels are in /boot.
If I select 3.16.0-10 boots to desktop, from past investigations that
means compiz failed and hence unity failed.
If I select 3.16.0-6 boots just fine, 3D and all.
Since it's the same install, everything
Rebooted selecting 3.16.0-10 kernel and compiz and unity failed like
they have been since 3.16.0-7.
Failing uname -a:
Linux Lenovo2 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:26:44 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Just did apt-get update apt-get dist-upgrade 27 August. No help on
Still trying to get 3.16.0-10 to run unity on Intel Core 2 Duo.
Many boots yesterday, just one time 3.16.0-10 ran just fine with 3D
hardware support. All the rest, I assume compiz has decided that the
hardware does not support 3D. It does.
Viewing all this as a black box, what's going on
Joseph, on your comment #18,
yes, booting with prior kernel 3.16.0-6 works. Like right now. As has
all utopic kernels previous to 3.10.0-7.
Tried latest 3.17.0-031700rc2-generic on three different installs:
1. On a 3.16.0-9 install, compiz/unity fail as usual. installed
3.16.0-6 works for me. Looking at Xorg.0.log - is this the driver
that's being used?
[ 9.623] (II) intel(0): Using Kernel Mode Setting driver: i915, version
1.6.0 20080730
[ 9.623] (II) intel(0): SNA compiled: xserver-xorg-video-intel
2:2.99.914-1~exp1ubuntu1 (Maarten Lankhorst
Here's the same thing from 3.16.0-10 where compiz fails and hence unity fails.
I'm no developer, looks to me like the same driver works for 3.16.0-6 and fails
with 3.16.0-10 ?
Am I looking in the wrong place?
[ 9.469] (II) intel(0): SNA compiled: xserver-xorg-video-intel
Stephen, thanks for your interest.
Here's EE results from booting 3.16.0-6 which is fully working:
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 7.504] Initializing built-in extension MIT-SCREEN-SAVER
[ 7.631] (EE) intel: Failed to load module dri3 (module does
As a computer development engineer, if something failed that ran before,
suspect would be whatever was new (kernel in this case). Did the new
item fail, or did it react in such a way to cause something else to fail
that was running O.K. before?
Can you tell if the same Intel driver is being used
Thanks. If I can do any testing let me know.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1359299
Title:
utopic 3.16.0-9 iso boots to desktop no unity
Status in “linux” package in
BTW, if there's any way to try Compiz with bisection, from my past
ubuntu testing over the years since Compiz was introduced, Compiz code
has a lot of hardware dependencies
Just tried 3.16.0-11 updates on 30 August still no go.
--
You received this bug notification because you are a member
As far as triangulation from the bird's eye view:
utopic fails:
ubuntu unity/compiz amd64 after July 31
utopic works:
ubuntu unity/compiz amd64 July 31 and before
ubuntu unity/compiz i386 today
kubuntu amd64 today
xubuntu amd64 today
lubuntu amd64 today
I'm no particular fan of unity, but as
On Intel Core 2 Duo 3.0 gHz Intel Corporation 4 Series Chipset Integrated
Graphics Controller (rev 03)
Trying 3.17.0-rc3
3.16.0-11.iso actually boots to unity. First time in a month. Very shaky
1920x1024 mouse hardly works.
boots to desktop only. No unity. .iso did get unity, install didn't.
Well, 3.16.0-11 has booted to desktop only, and for the first time
booted normally on Intel Core 2 Duo 3.0 gHz. rc3 kernel is also in
/boot I select which kernel at boot time..and sets to 1360x768 which
the rc3 nomodeset would not do.
.iso is
Next 3 boots unity/compiz failed.
Had to do nomodeset to post this comment.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1359299
Title:
utopic 3.16.0-9 iso boots to desktop no unity
linux-image-3.16.0-12 booted O.K. several times this morning.
I wouldn't know whether there is actually a fix for compiz or just whether the
timing race of compiz/x is better.
So as of 3.16.0-12 this problem has not reproduced over several
boots.
BTW, 3.17...rc3 still fails unless
4 September amd64 .iso boots to flashing desktop, no unity.
3.16.0-12 kernel in the .iso according to ls /boot fails to start
unity.
My -11 updated to -12 does work.
Now the .iso is usually behind apt-get update. Past experience if the
.iso isn't running correctly the install won't either.
U + 1 forums for last few days a number of people on a variety of
hardware booting to black screen or command line or
Anything we can do to test anything?
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Joseph, will give them a try.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1359299
Title:
utopic 3.16.0-9 iso boots to desktop no unity
Status in Unity:
Confirmed
Status in “linux”
Joseph, tried the rc7 and the -7 kernels on a new install which is at
-12 level. The .iso boots to desktop so I do a Ctrl-Alt-F1 for a
command .ine. The .deb's were previously downloaded with a utopic -12
which works.
With the fresh .iso install, no updates, did dpkg -i on the rc7. Booted,
As of 10 September, the amd64 daily build hasn't been built since 5 September
and is still at the 3.16.0-12 level.
The .iso boots to desktop as usual. No compiz/unity.
From command line do apt-get update and then apt-get dist-upgrade, reboot at
3.16.0-14 whereupon compiz/unity work.
BTW,
As of 11 September, the daily(?)-live current amd64 .iso is still at 5
September, 3.16.0-12, boots to desktop no compiz/unity.
Daily-live pending amd64 was at 10 3.16.0-14, boots to compiz/unity
fine. Installed fine (for a develompment image).
I haven't heard that there was any change in the
daily-live current now dated 11 September. Zsync vs. yesterday's daily-live
pending updated said 82% complete.
.iso amd64 booted normally, unity panels O.K. kernel 3.16.0-14.
First daily-live current that booted O.K. since July.
So as of today, this bug did not occur.
--
You received this
Public bug reported:
Did Ctrl-AltF1 sudo service lightdm resart to get desktop.
Acer Apire1 netbook 2GB
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.10
DISTRIB_CODENAME=utopic
DISTRIB_DESCRIPTION=Ubuntu Utopic Unicorn (development branch)
Linux Aspire1 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1
Public bug reported:
I set resolution in displays to 1360x768
Select Activities and it uses resolution 1920x1020 which is so small it's hard
to read.
Some windows are using 1360x768 which is what I want
Some windows revert to max resolution which is barely readable.
ubuntu utopic unity has no
Public bug reported:
Looks to me like the same failure I get with
sudo software-properties-gtk
How do I add Ubuntu Partners to Repositories?
How do I change Update frequency from daily to never, I update
frequently anyway when I want to, and don't want Update to come blasting
in to what I'm
BTW, Systems Settings Software Updates won't start either.
Vivid just installed from the daily .iso
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386017
Title:
vivid synaptic
After today's vivd updates bug is fixed here,
System Settings Software Updates works,
sudo software-properties-gtk works,
Synaptic Settings Repositories works.
Thanks much, whoever.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
*** This bug is a duplicate of bug 1410480 ***
https://bugs.launchpad.net/bugs/1410480
Problem is the file permissions for /etc/default/keyboard on the vivid
.iso are
ls -l /etc/default/keyboard
c-
Won't work. No way ubiquity can use the file.
On previous vivid, tahr, etc. file
*** This bug is a duplicate of bug 1410480 ***
https://bugs.launchpad.net/bugs/1410480
bug #1410480, overlayfs v1: renaming existing file uses chardev whiteout
(should be symlink)
seems to have nothing at all to do with ubiquity install failures which
is this bug here.
I've verified tahr
Workaround finally posted on Launchpad:
#sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf
#Add the following lines
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
EndSection
#reboot
--
You received this bug notification because you are a member
>From Comment #3 I installed
linux-headers-4.2.0-040200_4.2.0-040200.201508301530_all.deb
linux-headers-4.2.0-040200-generic_4.2.0-040200.201508301530_amd64.deb
linux-image-4.2.0-040200-generic_4.2.0-040200.201508301530_amd64.deb
which is the latest I saw, dated 8-30-2015.
gsettings still
Public bug reported:
until recent updates,
gsettings set org.gnome.desktop.background picture-uri
'file:home/jerry/Pictures/Shark_Island.jpg'
reset wallpaper to the desired picture. Most of the time Wily boots to
a horizontally hashed wallpaper which used to be corrected by doing
gsettings
Public bug reported:
Since update unity buttons no longer visible, off the left of the screen.
Settings Hide is off.
A number of screen images are horizontally barred even the settings wallpaper
choices and the full screen, exit buttons on the window frame.
Terminal text will be horizontally
Today's update Sept 4 2015 worst screen yet. Even the text screen is
unreadable. See attachment.
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu Wily Werewolf (development branch)"
Linux Lenovo2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:25:10 UTC 2015
I typically use 1280 x 720 resolution easier for me to read.
That's a resolution where after last week's update the screen is shifted left,
black margin on the right, and unity buttons fall off the left. Hide is off.
If I change to 1368 x 768 the unity buttons are visible.
The monitor will
as of Sept 12 Wily updates gsettings still fails to work, reverts to
default brown screen.
Installed Utopic kernel on Wily, now Settings Appearance Wallpaper
displays jpg fine. With Wily kernel displays unreadable.
gsettings settings fails with Utopic kernel on Wily.
With Utopic kernel on
One of my three test pc systems consistently gets this delay with
Xenial. Updates no improvement.
I'll look for the systemd-logind messages next time I boot it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Christopher, will try kernel 4.5-rc1.
Current status on two pc's, xenial can set up the printer, print test page,
which is "held" I don't know why.
Release the page and it never prints.
14.04 LTS on the same pc, different partition prints fine.
--
You received this bug notification because
14.04 still printing fine. Actually, yesterday's ubuntu update screwed
up the network on 14.04 so I did a fresh install, printer works fine.
All the same hardware just a different partition from 4.5 RC1
4.5 RC1 printer installs O.K., connects, do a print, and all it gets is
processing/pending
Public bug reported:
Xenial Files can't browse wired local network.
In a different partition, same pc, 14.04.3 Files can Browse Network,
both ubuntu and Windows pc's
Xenial Nemo select "Network" can browse the network fine, display photos
from Windows pc O.K.
Xenial Files will not browse, just
Public bug reported:
There was an error during the CUPS operation: 'client-error-not-
possible'.
14.04.3 on another partition accesses network printer on XP just fine.
With identical smb.conf xenial cannot access the printer.
Xenial can access XP jpg images etc. so network connection to XP
Info from 14.04 LTS same hardware, same network, just different partition:
Network prints fine. Quick. No authentication problems etc.
cat /media/jerry/9110d642-ba35-4dfd-b42a-ceec94cbf7e3/etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
Tried the xenial 4.4 kernel listed in #3.
Connected to network printer settings says O.K. jpg files read fine
from the networked XP.
Submit print job, queque shows "completed", but nothing ever prints
except from 14.04 which works fine.
Booted another partition with xenial 4.3.0-7, connected
I've been testing Xenial iso's since the first images came out. Never
had this problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1559595
Title:
xenial fresh installs boot to
Public bug reported:
Fresh install 19 March daily build "current" .iso, apt-get update, apt-get
dist-upgrade booted to command line no desktop
Fresh install 19 March daily live "pending" same thing
from command line did ubuntu-bug, saved file
Booted xenial in another partition, this one a month
This problem occurred with Xenial Daily Live Current.
Daily Live Pending did not have the problem so I'm installed and running
O.K.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1559595
Installed Nemo file manager since Xenial Files does not have the Browse
Network feature that Trusty does.
With Nemo browsing the network just fine to Windows 10 was able to get
printer installed. Not a BIOS problem.
Entered a bug against Ubuntu Files, confirmed, missing browse network
selection
The browse network function omitted from Xenial Files (Nautilus)
Easiest workaround apt-get install Nemo
Another workaround,
start Files
Ctrl l that's a lower case L
network:///
does browse network. Just hard for me to remember these command line
like commands. Prefer GUI
With a lot of effort and million monkeys on the keyboard I was finally able to
get Xenial to access Windows 10 printer.
Yakkety Yak same problem all over again.
I'll flail around a bit and open another bug if necessary.
Conclusion, Ubuntu developers don't have a Windows 10 on their network to
*** This bug is a duplicate of bug 1650750 ***
https://bugs.launchpad.net/bugs/1650750
Trusty LTS no problem with keyboard, same PC, same keyboard, different
partition.
On Xenial LTS, All Settings -> BlueTooth -> Devices -> Anker A7721 ->
turn keyboard on, "On" flashes on screen and shuts
Public bug reported:
Turn bluetooth connection on with mouse selection and linux keeps turning it
off.
Anker A7721 keyboard running fine before update today and fine on other ubuntu
partitions.
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1
Public bug reported:
Turn bluetooth connection on with mouse selection and linux keeps turning it
off.
Anker A7721 keyboard running fine before update today and fine on other ubuntu
partitions.
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1
This bug goes away with Zesty Zappos kernel.
Zesty fixed Xenial's bios problem.
Problem solved I'll use Zesty waiting to see if an update to Zesty brings the
problem back.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
90 matches
Mail list logo
