I found switching from the add-on version to the xul-ext-lightning
Ubuntu package worked, giving me the latest version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797945
Title:
Lightning incompa
I'm still getting this with Ubuntu 18.04, with Intel sound and HDMI
output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736222
Title:
speech-dispatcher distorts all sound
To manage notifications
There's a setting in the CompizConfig Settings Manager (General Options
> Focus & Raise Behaviour > Focus Desktop) that controls the behaviour
for me in 16.04. It was on by default, and despite selecting sloppy
mode in Unity Tweak Tool it would focus the desktop. However turning it
off gave me the
>From the log messages that looks like a different problem. Am I right
in thinking that the trouble with suspending started later than the
trouble with USB devices disappearing? Does suspend and resume work
reliably without devices disappearing if you don't have the USB
soundcard attached?
--
Y
You should be able to get 3.19.0-30 for vivid through the normal
security updates. According to the changelog it includes the patch
(unlike -28).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116525
A couple of months ago I submitted a patch upstream to fix this
(http://article.gmane.org/gmane.linux.usb.general/128350), which is now
appearing in the Ubuntu kernels. In particular, I received a kernel
update for trusty yesterday which includes it, 3.13.0-65, and I think
that vivid and wily shou
I think you've misunderstood me: I've got a newer version but still have
the problem, and those patches don't solve it, but introduced the code
which does the bandwidth checking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
I also get this on a machine running trusty. The BIOS ought to be
fairly up to date:
root@pareto:/sys# dmidecode -s bios-version && dmidecode -s bios-release-date
G2ET99WW (2.59 )
12/04/2013
I looked into the code behind the "Not enough bandwidth on HS bus for
newly activated TT" kernel message
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116525
Title:
[Lenovo ThinkPad X230 Tablet] USB devices in docking station no longer
As mentioned in the upstream bug report, this was fixed in later
versions, probably by
https://git.gnome.org/browse/evince/commit/?id=8d3ac1d8de83f3c6d9c51e9ad2c56e000d4bb4e7
I've made a quick attempt at backporting this to trusty, and it does
seem to work now. I'll attach the patch.
** Patch a
Sorry, I should probably clarify, since I may have gotten confused
between several bugs and versions of this patch.
I have taken the earlier kernel build by Kamal, from
https://launchpad.net/~kamalmostafa/+archive/linux-kamal-
scien/+packages, which was mentioned in bug #578673, and that fixes th
Kamal's patch works for me on a Dell Inspiron 1564 with a Core i5
processor. Thanks! Looking forward to seeing this in an update of Lucid.
--
Lucid SRU: Intel Core i3/i5/i7 hang on resume from suspend (SCI_EN)
https://bugs.launchpad.net/bugs/594837
You received this bug notification because you a
We have seen the same problem on Debian/sparc, and suspect that it is
the same as http://sources.redhat.com/bugzilla/show_bug.cgi?id=4381
involving glibc making invalid alignment assumptions. We were able to
work around the problem by using nscd for host name caching.
--
Bus Error when attemptin
I have also tried switching virtual terminals upon resuming using Ctrl-
Alt-F1-10, with no luck. If I put the computer back to sleep using the
Function-Standby key combination, and wake it again, it is still broken,
but putting it to sleep using /etc/acpi/sleep.sh force seems to always
reset it to
After further experimentation, it turns out that this only happens when
suspending by closing the lid; if I suspend by using the power button on
the gnome panel, the power button on the laptop, the Function-Suspend
key combination, or '/etc/acpi/sleep.sh force', it suspends and resumes
just fine. O
Public bug reported:
I have just upgraded my girlfriend's computer (a Dell Inspiron 6000)
from Gutsy to Hardy. When she closes the lid, it goes to sleep just
fine, and when opening the lid back up again, it appears to wake up, but
the screen never turns back on. I've tried a few things (switching
On Wed, Feb 27, 2008 at 03:51:41PM -, Leann Ogasawara wrote:
> This bug was marked "Fix Committed" a while ago, but there has been no
> confirmation from Brian Campbell if this bug is actually resolved.
> Brian, care to comment if this is fixed for you? If so, we'll g
Public bug reported:
Binary package hint: nautilus
This is a feature request.
I have an external disk with several partitions. When I plug it in, the
automounter mounts it with the partitions named disk, disk-1, etc. It
appears that it is not consistent which one is named which, so it is
very ha
On Tue, Jul 11, 2006 at 08:08:54PM -, Ben Collins wrote:
> Yeah, link_in_boot should be yes for your purposed. Perhaps something
> else changed it on your system without your knowledge, but nothing in
> dapper should have done that.
What writes the initial /etc/kernel-img.conf? It doesn't app
On Tue, Jul 11, 2006 at 07:41:55PM -, Matt Zimmerman wrote:
>
> What's in /etc/kernel-img.conf? Perhaps you edited it?
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
I haven't changed it, I didn't even know about it
Public bug reported:
Binary package hint: linux-image-2.6.15-26-powerpc
The Linux kernel upgrades for dapper quietly fail because they update
the initrd.img and vmlinux symlinks in /, but not the ones in /boot
which yaboot uses. The result is that after reboot I'm still using the
old (vulnerable
21 matches
Mail list logo
