how is this tagged with Wishlist importance?
while i was reporting my issue w/ wireless keyboard i've noticed a few other
issues which seem to be resolved in newer bluez releases (5.25 this month).
there is a bunch of people affected w/ various mouse/keyboard/headphones not
working which can be
Updated my bios to 1.39 as implied by the bot.
--
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/1390964
Title:
Desktop hangs with intel_crtc_wait_for_pending_flips
Status in “linux”
I will try a BIOS upgrade on this machine later on.
However, I doubt it will change anything since I have to totally different
machines exhibiting the same problem (and it worked on the machine above an
12.04.5):
Machine 1: Lenovo X230 Laptop
Machine 2: Different desktop computer
Information
Walter and Boris, the video=ofonly radeon.agpmode=-1 work-around
allows installation to complete on my hardware. The installed system
even boots to the desktop. If forgot to test it on the 2014-11-08 image
but remembered for the 2014-11-09 image
--
You received this bug notification because
The issue is still not fixed, using Ubuntu 14.10 with 3.16.0-24-generic
kernel.
I've tried changing the DeviceID in /etc/bluetooth/main.conf with no
success, the system seems to think everything is running correctly.
Here is some data I collected : http://pastebin.com/E0Q05x0D
--
You received
This bug was fixed in the package bcmwl - 6.30.223.248+bdcom-0ubuntu2
---
bcmwl (6.30.223.248+bdcom-0ubuntu2) vivid; urgency=medium
* debian/dkms.conf.in,
debian/patches/0014-add-support-for-Linux-3.17.patch,
debian/patches/0015-add-support-for-Linux-3.18.patch:
- Add
I tried the 3.18-rc2 and my X553MA didn't even boot with it.
And I just built and installed vanilla 3.17.2 and with it the touchpad
functionality stays same as with 3.13.0-39-generic.
(But now with 3.17.2 screen brightness control does work...)
--
You received this bug notification because
Public bug reported:
Sometimes (randomly), my laptop cannot wake up from the suspended to ram
state.
It is an ASUS X200MA-CT220H notebook, with ubuntu 14.04.
When the system hangs on wake, even the caps-lock led does not light up
when pressing the key. Looks like the kernel hangs.
** Affects:
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1391090
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
I could not test the latest mainline kernel (3.18-rc4) . As before, the
system did not boot; however, this time, instead of displaying a
message, it simply gave a black screen. I also tried 3.18-rc3 with the
exact same result.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags added: vivid
--
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/1300349
Title:
8086:0a16 [Dell Inspiron 17R 5737] Video looks interlaced
Status in “linux” package in Ubuntu:
ahb, just to clarify, this report is only scoped to the Z77 Extrem4 hardware,
not any other. If you are having a problem with different hardware, please file
a new report, one per hardware combination, via a terminal:
ubuntu-bug linux
As well, please do not tar or compress files as it makes it
Janne Heikkinen, thank you for your comment. So your hardware and problem may
be tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into the default Ubuntu kernel (not a
mainline one) via:
ubuntu-bug linux
For more on this, please read
The Aviv, could you please test 3.18-rc3 (not rc4) and advise to the
results?
** Tags removed: kernel-unable-to-test-upstream
** Tags added: kernel-unable-to-test-upstream-3.18-rc4 needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this
The Aviv, could you please test 3.18-rc1 and advise to the results?
--
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/1387420
Title:
System freezes when performing a backup bash script
Tested mainline kernel version 3.18.0-031800rc4-generic
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.18.0-rc4
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which
Pascal Fürst, the issue you are reporting is an upstream one. Could you
please report this problem to the appropriate mailing list (linux-input)
by following the instructions _verbatim_ at
https://wiki.ubuntu.com/Bugs/Upstream/kernel ?
Please provide a direct URL to your e-mail to the mailing
Same here.
Ubuntu 14.04.1 64 Bit
After resume freezing on amd graphic card. When I am on intel suspend work fine.
--
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/1283938
Title:
[Samsung
https://translations.launchpad.net/ddtp-ubuntu/utopic/+pots/ddtp-ubuntu-
main/nl/12253/+translate
** Changed in: ddtp-ubuntu
Status: Triaged = Fix Released
** Changed in: ddtp-ubuntu/trusty
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member
I'll comply to Ubuntu's bug procedure(s).
Yet, I think it is important from a developers point of view to know from the
start that this issue is not related to a specify HW, but rather a more general
problem (i.e. at least concerning the Z77 desktop, the X230 laptop and the Z87
desktop).
@Andy: any news about this? can you reproduce? maybe any better place to
report 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/1381968
Title:
Fstrim destroys data on loopback
You have been subscribed to a public bug:
Using the nvidia-340.58 (from xorg-edgers ppa) with the latest 3.18
kernel, get that warning logged:
kernel: [ 35.160563] No drm_driver.set_busid() implementation provided
by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique
name
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1390390
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
** Package changed: xorg (Ubuntu) = linux (Ubuntu)
--
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/1390390
Title:
[xorg-edgers] No drm_driver.set_busid() implementation provided by
** Tags added: cts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1324125
Title:
Unable to trigger a kernel crash dump on laptop
Status in “kexec-tools” package in Ubuntu:
I also rebuilt the kernel using latest 3.16.0-25 ubuntu kernel (mainline
3.16.7).
This may solve some issues with nvidia.
Now we have 3.18, 3.17 and official 3.16 kernels patched with focaltech
driver.
https://www.dropbox.com/sh/07642x3lziqgmz9/AACGWNO5_lNnX7x7tYMoH9gka?dl=0
--
You received
Sorry for the noob question, but will this driver be included in the
offical 3.18 release? Where/how could I check this?
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/1372609
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed = In Progress
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul
Larson (pwlars)
--
You received this bug notification because you are a
This looks like a dkms bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758485
** Bug watch added: Debian Bug tracker #758485
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758485
** Bug watch added: Debian Bug tracker #757758
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757758
And here is the patch with new file mode. Now we do not need to create
focaltech.c and focaltech.h before apply.
** Patch added: focaltech3.16-v4.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372609/+attachment/4257286/+files/focaltech3.16-v4.patch
--
You received this bug
Updated patch with new file mode.
** Patch added: focaltech3.16-v4.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388160/+attachment/4257287/+files/focaltech3.16-v4.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This is most likely the patch we need:
http://anonscm.debian.org/cgit/pkg-dkms/dkms.git/patch/?id=9064776a8a9b5fb633e14a225c162a87eeea2cfd
And we should probably sync 2.2.0.3-2 into vivid.
** Also affects: dkms (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux
same bug as lp:1358373
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1390817
Title:
sed and unknown command `m' during kernel install
Status in “dkms” package in Ubuntu:
New
Status
@Martin
Probably the patch will be applied to 3.18. At list it has been
submitted. But it may take a lot of time until it lands in Ubuntu
kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
linux 3.18.0.2-2-generic (from canonical-kernel-team)
(sorry apport-collect open my default chromium browser, but ubuntu one
logging fails, so i cant use it)
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1382221
Title:
please add linux nvme block driver
Hi Chris,
the update did not change any symptoms for me.
Booting the kernel without the option 'psmouse.proto=bare' results in
the trackpad not working just as before. The only response it will
produce when you touch the trackpad is (on rare occassions) it might
instantly jump to a random part
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1384469
Title:
[i915_bdw] GPU hang bug, typo fix
No, it probably won't. I have not had much time, and on the red hat bug
tracker there is one case where the patch breaks suspend.
I do not know how to proceed or how to debug the issue, maybe adding a
quirk which disables the driver would be an option. I'll see whether I find
some more time next
The suspend problem is a general 3.18 but. It works for everyone else. So no
need to be so focused on that problem.
Just be it tested on 3.16 or 3.17 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Daniel, could you please take a test as #12? 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/1366841
Title:
[Dell XPS 11] Card reader RTS5249 doesn't work because failed to
I can verify that the regression is fixed in the proposed kernel.
--
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/1385510
Title:
CONFIG_SOUND_OSS_CORE_PRECLAIM Flag Set to Yes
Status in
I cannot edit the tag on Brad Figg's verification request, changing it
to verification-done-utopic.
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Trusty verified:
dannf@mustang:~$ cat /proc/version
Linux version 3.13.0-40-generic (buildd@auburn) (gcc version 4.8.2
(Ubuntu/Linaro 4.8.2-19ubuntu1) ) #68-Ubuntu SMP4
dannf@mustang:~$ sudo modprobe ipmi_si
modprobe: ERROR: could not insert 'ipmi_si': No such device
** Tags removed:
Utopic verified:
dannf@mustang:~$ cat /proc/version
Linux version 3.16.0-25-generic (buildd@beebe) (gcc version 4.9.1
(Ubuntu/Linaro 4.9.1-16ubuntu6) ) #33-Ubuntu SMP 4
dannf@mustang:~$ sudo modprobe ipmi_si
modprobe: ERROR:
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
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/1380432
Title:
24x7 counters: Bug in catalog_read()
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1366841
Title:
[Dell XPS 11] Card reader RTS5249
Darek, thank you for your comment. Unfortunately, this bug report is not scoped
to you, your hardware, or your problem. So your hardware and problem may be
tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into the default Ubuntu
usbip and usbipd binaries are part of the linux-tools-common package.
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looks like the bios update did not fix the bug, it stared again.
any suggestions ?
--
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/1389006
Title:
USB mouse and keyboard unresponsive
** Description changed:
- I'm experiencing the same issue described by users here -- the trackpad
- is not recognized on my ASUS D550MA-DS01.
+ The trackpad is not recognized on my ASUS D550MA-DS01. xinputs --list
+ shows no trackpad, and running synclient returns 'Couldn't find
+ synaptics
*** This bug is a duplicate of bug 1358373 ***
https://bugs.launchpad.net/bugs/1358373
@d9d
Cool, I'll dupe it and work on that other bug.
** This bug has been marked a duplicate of bug 1358373
sed: -e expression #1, char 6: unknown command: `m'
--
You received this bug notification
Ben Lansdell, could you please test the latest upstream kernel available
from the very top line at the top of the page (the release names are
irrelevant for testing in your release) following
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
upstream developers to examine the
Per Tyler, this is fixed in r2456. In 14.04, add-decimal-interp.patch
should be removed in favor of this patch.
** No longer affects: linux (Ubuntu)
** Also affects: apparmor (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu)
Status: Confirmed =
Thx for the feedback Lars, I think we can call it on the bug Walter,
so far nobody else has come forward with anything that suggests
otherwise.
Where would we propose to implement those params to be set as default
for the specific systems in future builds/ releases, would a post to the
ppc list
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
--
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/1391090
Title:
ASUS X200MA-CT220H does not resume from suspend
Status in
I'm so sorry, i didn't get to it and now traveling the world for a year
without my docking station. Hope someone else finds the time to bisect
this problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ramgorur, could you please test the latest upstream kernel available
from the very top line at the top of the page (the release names are
irrelevant for testing in your release) following
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
upstream developers to examine the
One thing to look into is how much the video=ofonly radeon.agpmode=-1
settings slow down the GUI. Some things, such as clicking on an icon,
are quite sluggish but I don't know how to find where the fault lies.
--
You received this bug notification because you are a member of Kernel
Packages,
Thanks for verifying Luciano!
--
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/1380432
Title:
24x7 counters: Bug in catalog_read()
Status in “linux” package in Ubuntu:
Fix Released
I'll ask the person to test with a different kernel, but so far the
symptoms looked different to the reports here.
Am 10.11.2014 17:15 schrieb Pilot6 1372...@bugs.launchpad.net:
The suspend problem is a general 3.18 but. It works for everyone else. So
no need to be so focused on that problem.
Will this patch go out in 3.13.0-38 this week?
I'm assuming that the discussion around 'linux-keystone' is something
different. Regardless, please do not drop this fix from 3.13.0-38 as
we're expecting it this week per Stefan's comments above - and we have
already verified it resolves the issue.
I'm also curious about an update on this issue. I'm running 14.04.1,
Kernel 3.13.0-39-generic and LXC 1.0.6-0ubuntu0.1. 'strace' output of
open-scsi looks basically the same as above.
As I understand it, this is related to iSCSI's Netlink implementation
not being namespace aware? I would love
You have been subscribed to a public bug:
When I boot my Ubuntu system I get the following messages into the
console before the Ubuntu splash screen:
[...] INFO @wl_cfg80211_attach : Registered CFG80211 phy
[...] Bluetooth: hci0 command 0x1003 tx timeout
** Affects: linux (Ubuntu)
these messages come from the kernel. Reassigning.
** Package changed: plymouth (Ubuntu) = linux (Ubuntu)
--
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/1390487
Title:
Inappropriate
Following the request, I updated the Bios, from the 302 to the 312
version, as proven by:
sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
X751LA.312
06/27/2014
I then run apt-get update apt-get upgrade, but no new drivers were
downloaded. I opened System Tools Preferences
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1390487
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
Luca Manunta, could you please test the latest upstream kernel available
from the very top line at the top of the page (the release names are
irrelevant for testing in your release) following
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
upstream developers to examine the
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed = In Progress
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paul
Larson (pwlars)
--
You received this bug notification because you are a
It turns out that the check which generates the panic here is likely
invalid, and the code will handle the situation just fine, so the check
can be removed. I've prepared a kernel with removes that check (and a
related one), which I've temporarily replaced with a warning for testing
so we can
** Tags added: utopic
--
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/601299
Title:
btrfs fsync() is extremely slow
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux”
I believe this is due to incomplete or not at all set up Xorg conf which
for some reason is not done for a long time on certain Radeon systems,
so those are without DRI and all the bells and whistles.
Did you try what I mentioned above?
sudo service lightdm stop
sudo Xorg -configure
sudo mv
I'm still experiencing this issue.
--
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/1251065
Title:
HP Mini 1000 fails to resume from suspend
Status in The Linux Kernel:
Invalid
Status
Peter-jezdec, could you please test the latest mainline kernel
(3.18-rc4) and advise to the results? If it doesn't provide a testable
environment please test the next newest release until one allows you to
test to the issue.
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
The latest mainline kernel can be downloaded from:
] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc4-vivid/
--
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/1390772
Title:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.18 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.18 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
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on
1 - 100 of 168 matches
Mail list logo
