Tested in oneiric. External mic OK, internal mic still not working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598351
Title:
External/Internal Mic on Lenovo Ideapad U150 (Conexant CX20582-
Tested in oneiric. External mic OK, internal mic still not working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598351
Title:
External/Internal Mic on Lenovo Ideapad U150 (Conexant CX20582-
After upgrade to Oneiric, many applications requiring the authentication dialog
stopped working.
* I am detecting exactly the same bug with the same error message for
software-properties-gtk.
* gnome-control-center - User Accounts - Unlock fails with the following error
message:
It seems like the problem occurs, because /usr/lib/policykit-1-gnome
/polkit-gnome-authentication-agent-1 is not running.
After running the authentication agent manually the authentication
window appears as expected and administrative operations can be executed
without problems.
I am trying to
Seems to be fixed in natty and recent updates of maverick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/646969
Title:
pulseaudio lock-autospawn.c: Cannot access autospawn lock.
To manage
Tested in natty. External mic OK, internal mic still not working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598351
Title:
External/Internal Mic on Lenovo Ideapad U150 (Conexant CX20582-
In my case it seems like the problem is high interrupt load due to ACPI.
I still do not understand what exactly ACPI has to do with Xorg CPU
Utilization, it is even stranger that an ACPI problem could cause high
CPU utilization for user applications like gedit or thunderbird, but the
fact is that
I have detected just the same symptoms on a 32-bit Maverick Install with
Intel Video (Intel GM45). The problem does not seem to be specific to
Nvidia drivers. I've done testing with 2.6.35-22-generic,
2.6.35-23-generic and I've also tried 2.6.36 from Kernel PPA and the
results are basically the
The problem does not occur only with Nvidia chipsets but also with Intel Video
(Intel GM45). The GUI is sooo slow it is unbearable. Here is one way to
replicate the problem:
1. Click on Gnome Main Menu.
2. Start moving the pointer up and down over the menu entries.
3. In a few seconds Xorg will
The bug also affects Lenovo Ideapad U150. On this laptop, the brightness
buttons work, the brightness applet notification pops up to show current
brightness level and the respective files in /sys and /proc folders are
updated with the brightness value, but the display brightness level
stays at
Sound worked fine in Lucid. After upgrading to Maverick listening to music
frequently becomes imposible because sound is totally garbled. The following
message appears to coincide with sound problems:
pulseaudio[2372]: ratelimit.c: 3 events suppressed
The event that seems to be supressed seems
I've just upgraded to Maverick. Out of the box, recording from external
Mic works fine, while Internal Mic capture volume is very low and there
is lots of popping and crackling noise.
--
External/Internal Mic on Lenovo Ideapad U150 (Conexant CX20582- Pebble) does
not work.
Y get the same error on a Lenovo Ideapad U150 with Conexant CX20582
(Pebble).
--
pulseaudio[2034]: alsa-util.c: snd_pcm_avail_delay() returned strange values:
delay 0 is less than avail 16.
https://bugs.launchpad.net/bugs/640462
You received this bug notification because you are a member of
On Lenovo Ideapad U150, the touchpad supports two-finger vertical and
horizontal scroll, after executing the following commands:
xinput set-int-prop SynPS/2 Synaptics TouchPad Synaptics Two-Finger
Pressure 32 10
xinput set-int-prop SynPS/2 Synaptics TouchPad Synaptics Two-Finger Width
32 8
I compiled ALSA version 1.0.23 from sources using the following document as a
guide:
http://monespaceperso.org/blog-en/2010/05/02/upgrade-alsa-1-0-23-on-ubuntu-lucid-lynx-10-04/
Before the upgrade only the following knobs were available in ALSA
Mixer: Master, PCM, S/PDIF, Capture, Analog Mic
Public bug reported:
Ubuntu Lucid on Lenovo Ideapad U150 Laptop with Conexant CX20582
(Pebble) sound. Speakers and headphones work perfect; sound switched
seamlessly to headphone when plugged into Jack.
I upgraded the Kernel and Alsa Drivers from Lucid Proposed Updates:
a...@ikarus:~$ uname -a
ALSA Info script output can be found here:
http://www.alsa-project.org/db/?f=9294e6729dee601fbc9a8723d96c80793ff4e2a9
--
External/Internal Mic on Lenovo Ideapad U150 (Conexant CX20582- Pebble) does
not work.
https://bugs.launchpad.net/bugs/598351
You received this bug notification because you
Thanks Scott, for the detailed explanation. Even though I've been using
Ubuntu for the last few years, I am quite new to launchpad.
--
mountall blocks on timeout waiting for a partition, rather than supplying
prompt and picking it up later
https://bugs.launchpad.net/bugs/527666
You received
Hi Scott, I will be glad to help as much as I can.
I am sending you the following information in the attached zip file:
udevadm_info.recshell - Output of 'udevadm info --export-db' in recovery shell.
boot.log.recshell - /var/log/boot.log from recovery shell.
udev.recshell - /var/log/udev from
Hi Scott,
I upgraded the device-mapper packages from your PPA repo and I've done
some testing.
I've done five reboots and one shutdown-restart cycle for testing
without any boot problems so far; seems like things have definitely
gotten much better; congratulations. :-)
All LV device nodes have
* I have upgraded to mountall 2.14 from PPA, but the boot still fails in
more the attempts. The bug is kind of tricky, because after the
upgrade, it seemed as if the issue was fixed, but in subsequent boots
the problem reappeared.
* The bug does not apply only to /var, but it can be any other
Oops, sorry /var/log/udev was sitting there, but I had not seen it... I
am attaching the log for udev for the same boot attempt...
** Attachment added: udev
http://launchpadlibrarian.net/45203998/udev
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You
*** This bug is a duplicate of bug 561390 ***
https://bugs.launchpad.net/bugs/561390
** This bug has been marked a duplicate of bug 561390
LVM - /var failed to mount during boot
--
lucid hangs on boot because of device ownership
https://bugs.launchpad.net/bugs/557909
You received this
I've done some more testing trying to isolate the bug. I generated
copies of the boot.log and udev log files in the recovery shell, to
leave out log entries from the boot process after leaving the recovery
shell.
The /etc/fstab contains the following file systems:
/dev/mapper/vg0-lvRoot/
Hi Scott,
The bugs 561390 and 527666 seem to be pointing to the very same issue to me.
Infact, I was quite tempted to mark them as duplicates:
* In both cases the same error message is displayed and the only way to
continue with the boot process is to enter the Recovery Shell and mount the
Given the fact that the mounting of partitions and the boot process
still fails half the time can the status of the issue be updated?
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
Bugs, which
The bug 527666 is still not fixed, and the two bugs seem to related. I
upgraded to mountall from the PPA, but I still have problems randomly,
getting some filesystems on LVs mounted. The issue does not seem to
occur consistently, because I have upgraded two laptops to Lucid and
only one exhibits
Seems like the problem does not occur consistently with every possible
setup, because I have a another laptop with 8 LVs that I upgraded to
Lucid yesterday and it has been booting without problems; just the usual
error messages for statd and ureadahead startup for having /var on a
separate
With following line in mountall.conf to fix permissions for LVs, everything
seems to work fine:
chown root:root /dev/mapper/*
But, I've discovered that on battery power things get even worse. The
boot seems to hangup about the same place, but I cannot obtain a
recovery shell and I have found no
With the change to fix de ownership issue of DM device nodes, things
seemed to be working, but then I started having problems again today
even with mains power. I second Thierry Carrez that the boot fails about
half the time. In fact the things have become worse, because sometimes
pressing M for
After a recent Lucid upgrade I have been observing the same message at
boot.
What is wrong with having a /var on a separate partition? Separating
/var is a quite common recommended installation best practice for UNIX /
Linux systems. I always try to use LVM to have a small root partition
and
I am experiencing exactly the same problem since I upgraded to Lucid two
days ago.
Seems to be related to the following issue in Lucid:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/527666
The boot process hangs with the following message:
The disk drive for /xxx is not ready yet or
Yesterday, I had posted a comment with details of the issue I am
experiencing since I upgraded to Lucid.
Lucid hangs up indefinitely with the Waiting for 'some partition'
error. The partitions that cause the problem are on LVs. Amit Kucheria
mentioned that at this point some of the LVs have
*** This bug is a duplicate of bug 527666 ***
https://bugs.launchpad.net/bugs/527666
** This bug has been marked a duplicate of bug 527666
Waiting for /some/partition [SM]
--
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification
I am experiencing exactly the same problem since I upgraded to Lucid
yesterday. I wonder if this is a udev problem, because I've also
discovered an issue with the permissions of /dev/shm.
Since, the upgrade to Lucid, boots hangup indefinitely. I have to execute the
following procedure to get to
35 matches
Mail list logo
