** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194795
Title:
Sound menu music seeker in cinnamon counts seconds too quickly
To manage notifications about this bug go to:
Running Cinnamon under Arch Linux, but I have an identical issue with
Rhythmbox 3.0.3. The first track played after stopping is OK, then if
you fast-forward the next track plays twice as fast as normal, then 3x
speed, etc.
One slightly hacky fix in
FYI, I no longer own this hardware (sold and upgraded)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/658955
Title:
Natty fails to boot on Gigabyte GA-MA78GPM-UD2H
To manage notifications about
I've tested 3.2.20-generic and the bug is still there. The first fixed
version was 3.3-rc6 (both from the Mainline PPA).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/658955
Title:
Natty fails to
Brief update: Tweak is still necessary with the Precise default kernel,
but the final 3.3.0 kernel I tested under Oneiric was OK.
Looks like there's some upstream work in the area of buggy AMD
motherboard BIOSes: https://lkml.org/lkml/2012/3/28/249
If you want me to try for a bisect I can do it;
Trying the above 3.3-rc6 x86_64 kernel with GNOME 3.2 under Oneiric and
it's suspending/resuming OK so far as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907168
Title:
[ 3.0.0-14 regression
Interestingly, while it failed in 3.2.0 (that's what the above patch is
against) the motherboard boots out of the box with 3.3-rc6. There's a
new DMESG error however on the first and subsequent resumes:
[ 695.000381] Enabling non-boot CPUs ...
[ 695.000381] Booting Node 0 Processor 1 APIC 0x1
[
The issue is still intermittent with the released 3.0.0-15 and -16
kernels. I haven't figured out what makes it occur on some suspends but
not others.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I note comment #10 in bug #800140 reports a similar issue, and the whole
topic covers a similar error message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907168
Title:
[ 3.0.0-14 regression ]
I've been running it for a week now, as the bug's a bit intermittent,
and haven't managed to reproduce the issue with it. Will try with the
released 3.0.0-15 update now.
Incidentally I removed a stick of bad RAM recently which may have
contributed a little, but I suspect not wholly.
--
You
Sorry, disregard that, just resumed again and the error occurred under
3.0.0-15, in DMESG:
[drm:drm_mode_getfb] *ERROR* invalid framebuffer id
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907168
I can't reproduce it under 3.0.0-15.24, everything works as expected.
Sounds like a different issue to #904569 as that is a hang, whereas this
could be worked around by switching virtual terminals. Ah well, may have
been a temporary aberration of some kind with 3.0.0-14.
** Summary changed:
- [
Apologies for missing that, I've added the Signed-off-by and it passes
scripts/checkpatch.pl. Patch reattached.
I've no feedback yet from my upstream submissions, any chance of getting
the patch in there? The above linux-kernel list, and also the acpi-
support list:
Public bug reported:
This problem did not occur in 3.0.0-13 under Oneiric, nor did it occur
in a self-built 3.1.2 vanilla kernel I was testing a few weeks ago for
an unrelated bug.
Since upgrading to 3.0.0-14, every time I resume from suspend the screen
remains blank. Switching to a virtual
** Attachment added: DMESG showing error in 3.0.0-14
https://bugs.launchpad.net/bugs/907168/+attachment/2642162/+files/dmesg-3.0.0-14.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907168
Here's the patch I have submitted upstream to LKML:
https://lkml.org/lkml/2011/11/22/511
This automatically works around the issue and allows system using this
motherboard to boot and suspend/resume successfully, by detecting the
motherboard in a quirks list. Hope this helps.
** Attachment
I have solved the problem -- upstream bug on the Linux kernel bugzilla
linked.
Changing the kernel boot parameters to solely acpi_skip_timer_override
in /etc/default/grub results in the motherboard reliably booting and
suspending/resuming. This appears to affect a wide range of desktop
Gigabyte
** Summary changed:
- Slow suspend to RAM with clocksource TSC on Maverick AMD64
+ Natty fails to boot on Gigabyte GA-MA78GPM-UD2H
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/658955
Title:
Natty
The problem has worsened in Natty -- the default kernel will not boot
from the hard disk (freezes after you select it in GRUB2) unless you add
clocksource=hpet to the command line, in which case it boots perfectly
well.
For anyone else, you need to edit /etc/default/grub and add
clocksource=hpet
carl9170 works wonderfully without any disconnections for me under
Maverick. Built from compat-wireless. The only issue is that it doesn't
seem to want to resume properly once the computer has suspended, I get
this error in DMESG (after the USB devices have resumed):
[37522.811361] usb 1-2.1:
I've found a solution. The problem is that the clocksource TSC is
unstable (not just the AHCI driver). Adding:
clocksource=hpet
to the kernel boot command results in the first suspend working
properly.
** Summary changed:
- Slow suspend of AHCI driver on Lucid/Maverick AMD64
+ Slow suspend to
For anyone wanting a semi-fix that doesn't entail restarting while
waiting for evdev to be updated:
1) Even if the mouse is frozen, press Alt-F2 and type gnome-terminal
without quotes, then Enter.
2) Type xinput list without quotes, Enter, and note the id of the keyboard
listed under Virtual
Public bug reported:
Both Lucid and Maverick kernels suspend to RAM very slowly (5 minute
delay) on the first suspend after a cold boot. It appears that the
kernel is hanging for that time on suspending the AHCI device, per the
DMESG logfile included. I first noticed the problem halfway through
** Attachment added: AcpiTables.txt
https://bugs.launchpad.net/bugs/658955/+attachment/1687079/+files/AcpiTables.txt
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/658955/+attachment/1687080/+files/AlsaDevices.txt
** Attachment added: AplayDevices.txt
Confirming that this is a new regression in a fresh install of 10.10
final release from 10.04 (kept my /home partition). I have a combination
of a Microsoft Wired Keyboard 600 (all media keys cause the hang) and an
A4Tech USB mouse.
Notably pressing the XF86Calculator key causes a mouse selection
*** This bug is a duplicate of bug 636311 ***
https://bugs.launchpad.net/bugs/636311
Some more information: evdev is apparently misdetecting the keyboard as
a mouse:
# xinput list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer
*** This bug is a duplicate of bug 636311 ***
https://bugs.launchpad.net/bugs/636311
** This bug has been marked a duplicate of bug 636311
Keyboard special keys interfere with mouse
* You can subscribe to bug 636311 by following this link:
I see that a new driver has been released for this chipset:
http://wireless.kernel.org/en/users/Drivers/carl9170
I haven't had a chance to try it yet, but the changelog suggests many
features have been added and bugs fixed (including fatal errors).
Hopefully if it resolves the issues with
Agreed, it's not just a NetworkManager issue. I'm trialling ngc2997's
suggested patched NetworkManager from volanin's PPA, with background
scans off, and still experiencing the same freezing issues during large
data transfers (?maybe less frequently, hard to tell for sure).
Notably, I see
I have exactly the same problem (Linux nirvana 2.6.32-22-generic
#36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux). The
default Lucid ar9170usb is driving a TP-LINK WN-821N in 802.11g mode
with WPA2-PSK, connecting to OpenWRT 10.03 on WRT54GL running the b43
mac80211 driver. I have
This problem also affects my Toshiba Tecra M3. Suspend/resume worked
under Gutsy but fails with all release Hardy kernels and the current
Intrepid kernel. They would resume to a blank screen without accepting
any input necessitating a hard reboot.
Adding this to /etc/pm/config.d/config:
Hi, can one of the Evolution maintainers please comment as to whether
there are any plans to fix this crasher in Gutsy? It's solved upstream
and (apparently) in Hardy, and the Evolution addressbook is essentially
broken in Gutsy without this fixed.
Thanks!
--
Addressbook crash when searching
32 matches
Mail list logo
