unable to collect logs due to the instability of the kernel
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
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/1329069
3.13.0-27.50
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kevin 10207 F pulseaudio
CurrentDesktop: Unity
Date: Fri
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kevin 10207 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jun 13 02:13:05 2014
HibernationDevice: RESUME=UUID=8434466e-40aa-4c19-990f-adc570555efa
InstallationDate: Installed on 2013-06-02 (375
I have also seen this manifest when running Update Manager under the
2.6.32-61 kernel. Launch Update Manager and click the Check button to
reload the cache of software sources and Update Manager will hang.
--
You received this bug notification because you are a member of Kernel
Packages, which
Bridge)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage notifications
)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage notifications about this bug
Bridge)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage notifications about
)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage notifications about this bug
Bridge)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage notifications about
)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage notifications about
)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage notifications about
Bridge)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage notifications about
of VT8237A
South Bridge)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage
of VT8237A
South Bridge)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage
Bridge)
* VIA Technologies VT6103 Ethernet external PHY
* BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
* Ubuntu 8.04.4 LTS 32-bit
* Ubuntu 10.04.4 LTS 32-bit
* Xubuntu 12.04 32-bit
Regards,
Kevin Brace
To manage notifications
).
Typing in the following commands in Terminal does seem to get my Ethernet
access back.
~$ sudo rmmod via_rhine
~$ sudo modprobe via_rhine
Of course, remove ~$ when one types in the commands.
Still I want a more permanent solution by getting the bug fixed.
Regards,
Kevin Brace
--
You
On A05 and have the exact same issue.
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
--
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/1010931
Title:
14e4:4727 With
Fresh install of 13.10 fully updated.
--
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/1010931
Title:
14e4:4727 With Broadcom BCM4313, 2.4GHz works but 5GHz doesn't
Status in “linux”
-23-generic i686
Annotation: This occured during a previous hibernate and prevented it from
resuming properly.
ApportVersion: 2.14.1-0ubuntu1
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kevin 1847 F lxpanel
CRDA: Error: [Errno 2] No such file
: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kevin 1690 F pulseaudio
Card0
]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kevin 1690 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e0 irq 45'
Mixer name : 'Intel CougarPoint HDMI
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1226855/+attachment/4167056/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1226855/+attachment/4167061/+files/UdevDb.txt
--
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/1226855
strace -f -o open-iscsi-start-lxc.txt service open-iscsi start
** Attachment added: strace -f service open-iscsi start
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855/+attachment/4167066/+files/open-iscsi-start-lxc.txt
** Changed in: linux (Ubuntu)
Status: Incomplete =
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1226855/+attachment/4167059/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1226855/+attachment/4167062/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1226855/+attachment/4167060/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1226855/+attachment/4167058/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This is still an impacting issue, Curious if there has been any progress on it
on any front?
Being that apport information was requested I've provided it from my running
systems.
The apport information attached to this issue is from within the LXC container.
The host system is:
Ubuntu 14.04.01
I'm seeing this issue as well on a Dell XPS. I've disabled 11n as
described in this bug (and elsewhere) but wifi still drops once every
few hours. I'll try to grab some logs next time it happens.
--
You received this bug notification because you are a member of Kernel
Packages, which is
3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kevin 10207 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jun 13 02:13:05 2014
HibernationDevice: RESUME=UUID=8434466e-40aa
Public bug reported:
/boot mounted (ro)
issued ' mount -o remount,rw /boot' in another terminal and reran 'apt-
get -f install'
all is wonderful with this great OS! Keep up the good work :)
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-38-generic (not installed)
in order to help set priority, we're hoping to have this functionality
to support convergence demonstrations ~Feb 22015
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1400827
Title:
dang it...that's 2015, not 22015so few months, not 20,000 years+few
months
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1400827
Title:
BlueZ crashing when connecting input channel
Same issue, on ASUS F200M.
--
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/1416849
Title:
Booted into blank screen after the security update
Status in linux package in Ubuntu:
Public bug reported:
$ cat /proc/version_signature
Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
$ lsb_release -rd
Description:Ubuntu 14.10
Release:14.10
$ apt-cache policy linux-cloud-tools-common
linux-cloud-tools-common:
Installed: 3.16.0-29.39
Candidate: 3.16.0-29.39
Version
It appears that the apt-get dist-upgrade munged linux-cloud-tools-
generic and didn't upgrade linux-cloud-tools-3.16-28 and linux-cloud-
tools-3.16-28-generic to linux-cloud-tools-3.16-29 and linux-cloud-
tools-3.16-29-generic. But trying to fix that led to:
invoke-rc.d: initscript hv-kvp-daemon,
I not only did as you suggested (which had no effect), I then purged all
the linux-cloud-* and dependencies, then did the install -f, clean and
update cycle and re-installed. Same problem. Now marked as confirmed as
per your instructions.
** Changed in: linux (Ubuntu)
Status: Incomplete =
Just encountered this bug for the first time on latest kernel
3.13.0-45-generic; booting 3.13.0-44-generic works. System is running as
a guest inside VMWare Workstation 11.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
sorry, forgot to include uname -a on my machine:
Linux frenesi 3.16.0-31-generic #43-Ubuntu SMP Tue Mar 10 17:37:36 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Seeing exactly this same issue on a fresh installation of Xubuntu 14.10
on my Thinkpad X200.
--
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/1406054
Title:
EeePC 1000 screen black waking
with this older bios ?
Regards
Kevin
On Fri, 2015-06-12 at 06:02 +, Po-Hsu Lin wrote:
Hi,
as this bug is affecting many different platforms, I don't think it's a BIOS
issue.
Verified on 201403-14879 - HP 355 G2 Notebook PC
Bump if anyone has time to work on this it would be a huge benefit to
the OpenStack community.
This is a blocking issue for us too as we're not able to fully use LXC
containers in our OpenStack deployments. Specifically we can not run
nova-compute in an lxc container due to issues with (RW)
Exactly the same problem experienced whilst trying to connect an Aquaris
4.5 to a Toyota bluetooth hands free system. I am more than willing to
help with testing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
adding projects linux-mako & linux-flo, is it possible to change to the
interactive governor by default (instead of OnDemand)
also, not just for mako/flo but this is a question that should be
asked/answered for all devices (arale, krillin,... as well)
** No longer affects: qtmir
** No longer
it's better, but i still see failure about 25% of the time
** Changed in: canonical-pocket-desktop
Importance: High => Medium
** Changed in: bluez (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: openstack-ansible/juno
Status: Confirmed => Won't Fix
** Changed in: openstack-ansible/kilo
Status: Confirmed => Fix Committed
** Changed in: openstack-ansible/trunk
Status: Confirmed => In Progress
** Changed in: openstack-ansible/trunk
Status: In
** Also affects: qtmir
Importance: Undecided
Status: New
** No longer affects: qtmir (Ubuntu)
** No longer affects: qtmir
** Also affects: canonical-pocket-desktop
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
touching this bug as on our unity8 windowed mode i see this as
1. go to system settings
2. select connect device
3. select mouse detected
4. select connect
(put user back to bt first view)
expected: to be connected
result: have to go back to the mouse bt page and hit connect again.
this is really
I can confirm that this bug in also present in Linux Mint 17.2 (based
upon Ubuntu 14.04) as early as August 25th 2015. I can also confirm that
the previous workaround worked works like a charm. Seems that the weird
behavior is somewhat related to the Centrino wireless adapter...
Thanks, Julian
** Changed in: canonical-pocket-desktop
Importance: Undecided = High
** Changed in: canonical-pocket-desktop
Status: New = In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: canonical-pocket-desktop
Importance: Medium => High
** Changed in: bluez (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1481136
Is this a duplicate of #1435040?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1525320
Title:
Aquaris E4.5 can't connect with car [Skoda Fabia] using bluetooth
Status in Canonical
Updated to OTA-8 this morning. Still cannot get my BQ 4.5 to connect to
my Toyota in car bluetooth system. The phone can see the car bluetooth,
but when I enter the PIN nothing happens, either on the phone or the
car.
--
You received this bug notification because you are a member of Kernel
Public bug reported:
spawned from bug 1513450
as well as some investigation by tvoss
devices need to be tuned to utililze the interactive governor; available method
employed by android/apple is to switch to interactive when the device is picked
up (sensor) or screen is unblanked
this actually
spawned bug 1518418 for the governor topic
** No longer affects: linux-flo (Ubuntu)
** No longer affects: linux-mako (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-flo in Ubuntu.
https://bugs.launchpad.net/bugs/1513450
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Released
** Changed in: ubuntu-system-settings-online-accounts
Status: New => Fix Released
** Changed in: canonical-pocket-desktop
Status: New => Fix Released
--
You received this bug notification
Can someone explain how, if at all, these fixes flow through to other
Linux versions like Fedora?
--
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/1136110
Title:
USB Audio Codec choppy
Public bug reported:
while testing pd, had trouble connecting a previously connected mouse.
attempted the restart indicator-bluetooth trick, this didn't help.
I could see the mouse in the list, but never would connect when selecting the
"connect" button.
in the end had to "forget device" then
Public bug reported:
Every time i flash, needing to connect my bt mouse/keyboard, i open
u-s-s and go to the bt icon, select it and tap on "connect a
device"...little orange spinner spins...but list never populates.
I have to log on to the device shell and restart indicator-bluetooth at
which
Public bug reported:
So I've been running ubuntu-pd on Nexus4 over a few days and began
noticing this.
1. connect bt mouse and keyboard
2. connect to external monitor
3. use device for extended period of time
sometimes the devices will appear to disconnect, as well as be forgotten.
I can't tell
I'm not sure if this needs a new bug or if i am correct in adding this
information.
But I made a quick video to show exactly the problem i'm seeing
https://www.youtube.com/watch?v=Mkql0gSq1RQ
hope that helps.
--
You received this bug notification because you are a member of Kernel
Packages,
so currently holding up promotion of mir - so, just noting here (mainly for
alan) we're disabling this test on mir 0.19.1 rel, if this bug gets fixed, we
should reinstate test if we do a 0.19.2
aiui, we've left it active on devel - so might be fixed by time we do mir0.20
and this will be moot
Public bug reported:
I'm not sure what is happening with this error, I think it may be
related to my having to manually make space in /boot to update the
kernel. It is possible I have removed the wrong things.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package:
I'm seeing this with an HP bt mouse and a logitech keyboard.
I'd say 30% of the time.
I was testing N7 convergence pretty heavily yesterday.
I was having to hit "forget device" then reconnect.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I meant OTA-9 BTW
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1435040
Title:
Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Status in Canonical System Image:
Confirmed
Upgraded to OTA-0 and still not working with my E4.5 and Toyota Avensis.
I have access to phones running the following OS:
1. Symbian
2.Android
3.iOS
4. Firefox OS
5. Ubuntu
All of them connect to the car bluetooth without issue, except Ubuntu.
It's been an issue for a year now.
Can we have a
this is effecting mir-snap work as well
** Changed in: linux (Ubuntu)
Importance: High => Critical
** Changed in: mir
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
using mako, every no and then when having bt mouse/keyboard connected - you
will see when selecting a text box there is a repeating character (there is no
specific character, but always repeats)
it seems to be related somehow to bt devices disconnecting
the only cure is a
Public bug reported:
Problem occurred on startup of system
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-76-generic 3.13.0-76.120
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
ApportVersion:
>Fix 1: I think the policy for screen management is simple,
> never turn the display on if proximity is detected, it should
> not be specific to SMS or calls.
So you are saying we should have the proximity sensor on all the time ?
I disagree, first that's a power drain. Second, people will
** Description changed:
NOTE: kgunn suggests this bug be about 1) not 2) here
1)
I have been noticing my phone and tablet occasionally turning on without
interaction. Several times with my phone in my pocket I found it in the
emergency call UI
- I also see the tablet display turn on
@pat - also does the screen dim/blank at after expected expiry in the case of
#1) ?
and second, same question in the case of #2) ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552371
It seems like there is 1 bug and then 1 potential bug/feature depending
based on the original description
1) actual bug - display turning on by itself (btw, i know this happens
with Flo/N7 as well)
2) feature - bt devices are input, and we do want the screen to wake up
on keypress or mouse move.
** Changed in: canonical-pocket-desktop
Importance: Undecided => Critical
** Changed in: canonical-pocket-desktop
Assignee: (unassigned) => kevin gunn (kgunn72)
** Changed in: mir
Importance: Undecided => Critical
** Changed in: mir (Ubuntu)
Importance: Undecided =&
Aquaris E.45
OTA 10.1
Pairing does not work with Toyota Avensis (2010 model)
Also does not work with Parrot Minikit portable handsfree kit (approx 10 years
old)
On both, entering the pairing PIN results in no action from the phone,
and "pairing failed" message on the other device.
--
You
** Changed in: mir
Milestone: 0.23.0 => 0.24.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552371
Title:
Unexpected display on
Status in Canonical System Image:
Confirmed
** Changed in: canonical-devices-system-image
Assignee: Michał Sawicz (saviq) => Stephen M. Webb (bregma)
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Milestone: None =>
Public bug reported:
on latest rc-proposed for frieza seeing the following
1. connect bt mouse, no problem
2. turn on bt keyboard (logitech k480)
3. click sync
4. u-s-s spinner goes
expect: to see keyboard icon in list and availble to click on
actual: keyboard icon flashes for just a moment,
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552371
Title:
Unexpected display on
Status in Canonical System Image:
Incomplete
It looks like I'm having the same problem with a clean install of
Xubuntu 16.04.1, and I'll be trying the clocksource tweak. If you don't
hear back, it got fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@ppisati - if you have a classic deb based filesystem that is Xenial based, add
the ppa:ci-train-ppa-service/stable-phone-overlay (update/upgrade), then you
can simply apt-get install unity8-desktop-session-mir. Once that is installed,
you can toggle between unity8 & unity7 by clicking the
@ppisati - didi you need anything else?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1625805
Title:
arm64 kernel
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1625805
Title:
arm64 kernel panic for l2 mmu with unity8
@ogra actually we do! we all lucked out, recently (like within the last
month) someone somewhere turned on gallium/freedreno drivers for our
mesa builds. So i've got the full stack, i've already run the mir-
server/client snap on it with no problems (really need to blog that)
--
You received
so to be clear, this on ubuntu-core dragonboard image from the beta
images
--
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/1625805
Title:
arm64 kernel panic for l2 mmu with unity8
Public bug reported:
alsa force reload worke d but now it dont
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture:
Public bug reported:
after rebooting
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
@ppisati sorry about that, must've had too many tabs open. Corrected the
link and shared the doc with you as well.
** Description changed:
we are running the unity8 session snap on amd64 without any problems.
- to setup and reproduce the problem follow the "on Dragonboard" section of
Public bug reported:
every time i log out log back in no sound
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture:
Public bug reported:
no sound after restart shut down or accidental power off
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
** Summary changed:
- arm64 kernel panic for l2 mmu with unity8 session snap
+ arm64 kernel panic for l2 mmu with unity8 session snap (& deb as well)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
is there any update to this bug?
--
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/1625805
Title:
arm64 kernel panic for l2 mmu with unity8 session snap
Status in Snappy:
New
Status in
Public bug reported:
no sound
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse: Error:
** Summary changed:
- Xenial update to v4.4.26 stable release
+ Xenial update to v4.4.27 stable release
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released => New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug
Per the discussion above, this could be anywhere (qtmir, untiy8) not
necessarily in unity8 per se.
It does seem that this is specific to "unity8 on dragonboard" though.
We know that...
- mir-kiosk examples works on dragonboard
- unity8 works on arm64 m10
** Summary changed:
- arm64: history
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
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/1625805
Title:
dragonboard: history daemon dereferences a
** No longer affects: neutron
--
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/1463911
Title:
IPV6 fragmentation and mtu issue
Status in linux package in Ubuntu:
Confirmed
Status in
kjotte@polaris:/tmp$ wget
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7/linux-image-4.11.0-041100rc7-generic_4.11.0-041100rc7.201704161731_amd64.deb
--2017-04-18 14:17:58--
101 - 200 of 462 matches
Mail list logo
