** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44383762/Dependencies.txt
--
[Lucid] Hotkeys not fully working on Eee 1005ha
https://bugs.launchpad.net/bugs/564356
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: acpi-support
The wifi, mute, volume down, volume up (F2, F10, F11, F12, respectively)
do not work. I believe they used to work in Karmic, even if they didn't,
it is still essential to have these hotkeys functioning.
Further, but less essential - non-fuct
Edit: should of read your other post!.. atleast what you said can be
confirmed, samething happens to me, and with newest update.
--
WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143
local_bh_enable_ip+0x61/0x90()
https://bugs.launchpad.net/bugs/561125
You received this bug notification
I have no idea how this happens, but it shows up at restart a few times.
I'll post back if I can figure it out. (I haven't touched ubuntu one
prefs, like Sean said)
--
WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143
local_bh_enable_ip+0x61/0x90()
https://bugs.launchpad.net/bugs/56112
I believe this has now been fixed. (With all the latests updates on Beta
1)
** Changed in: light-themes (Ubuntu Lucid)
Status: Confirmed => Fix Released
--
Lucid: White symbols on light panel and Ubuntu Logo are difficult to see
https://bugs.launchpad.net/bugs/532844
You received this bug
@Mark Shuttleworth (if you still check this)
Given the amount of disappointment, I (as well as the design team) would listen
to what people are saying, but of course, you said it wasn't reasonable to do
so for the future (for new features). Then at least give our thoughts *some*
consideration.
@Gary: Did not crash for me, even without additional updates to beta1.
tried the gwibber items in MeMenu, and the messaging menu etc...still
did not crash.
Just wanted to put that out there.
(Asus 1005ha)
--
gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError
in __in
*** This bug is a duplicate of bug 532844 ***
https://bugs.launchpad.net/bugs/532844
Sorry.
--
White Icons not clearly visible on low contrast screens
https://bugs.launchpad.net/bugs/542435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
*He might of not been sure if it was in fact the light-theme or a
separate GDM theme.
Sorry thought this was my bug...mine was a duplicate...haha.
--
Lucid: White symbols on light panel and Ubuntu Logo are difficult to see
https://bugs.launchpad.net/bugs/532844
You received this bug notification
@Sebastien, sorry you're right. I just wasn't sure if it was in face the
light-theme, or a separate GDM theme.
--
Lucid: White symbols on light panel and Ubuntu Logo are difficult to see
https://bugs.launchpad.net/bugs/532844
You received this bug notification because you are a member of Ubuntu
B
I would of expected a user survey to go out, or something along those
lines to get an accurate, and full understanding of what USERS would
feel best with. After all, ubuntu is an OS that is built around open and
free ideals. Not letting everyone, or at least OPENLY DISCUSS CHANGE, is
a breach of it
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41366770/Dependencies.txt
** Description changed:
Binary package hint: gdm
- The white icons do not show up well on low contrasts screens. (i.e.
- Asus Eee 1005ha)
+ The white icons do not show up well on low contras
Public bug reported:
Binary package hint: gdm
The white icons do not show up well on low contrasts screens. (i.e. Asus Eee
1005ha)
Some of these 'white icons' are, the ubuntu logo, power icon, accessibility
icon, etc.
Icons should be changed to a more visible color, that is more different
tha
@Omer, Oh nevermind, Beta 1 comes out on Thursday..
--
gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError
in __init__() )
https://bugs.launchpad.net/bugs/525302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Omer, oh I forgot your could update stuff while you're on it live.. I
won't be able to test it out until next weekend, do you still want me to
try it out? (unless someone else confirms)
--
gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError
in __init__() )
https://b
Is the Alpha 3 Image updated with gwibber 2.29.92?
--
gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError
in __init__() )
https://bugs.launchpad.net/bugs/525302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Worst case scenario (for when Lucid is released), you'd have to go buy a
mic. I bought a small $3 one off ebay and it works fine :P
--
Internal microphone not working with certain programs
https://bugs.launchpad.net/bugs/447259
You received this bug notification because you are a member of Ubuntu
Also happens when you go to Broadcast Accounts in the status menu.
{on: eee 1005ha, netbook}
--
gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError
in __init__() )
https://bugs.launchpad.net/bugs/525302
You received this bug notification because you are a member of Ubu
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/36899504/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/36899505/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36899506/Dependencies.txt
** A
Public bug reported:
Binary package hint: notify-osd
When a notification appears one after another the OSD tends to lag and respond
slowly.
For example when I increase volume (from my netbook's volume hotkey) and hold
or repetitively press it, it will respond slowly.
It seems like a similar
No, you think that would help?
--
Internal microphone not working with certain programs
https://bugs.launchpad.net/bugs/447259
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
But is it really an ALSA problem? The mic works fine with ALSA, but it
doesn't when PA is supposed to use the mic.
I just really hope this gets fixed for 10.04 because it seems like it
isn't terribly hard to fix, since it's already half-working (with alsa
but not PA), I wish I knew more to help, b
** Description changed:
Binary package hint: pulseaudio
- I am running Ubuntu 9.10 beta on my Acer Aspire One A150L and I find
- that in some programs, the internal microphone will not record anything.
- I've tried the following programs to see whether the microphone works or
- not:
+ I am ru
This also occurs with the Eee 1005ha, im pretty sure it also has an
Intel HDA for the audio as well.
Internal mic works with sound recorder, although it is very noisy and
picks up alot of background noise instead of voices.
The problem is solved by using ALSA, but it causes problems, like for
exa
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
Internal microphone does not work with certain programs
https://bugs.launchpad.net/bugs/447259
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Description changed:
Binary package hint: xorg
- 1) When a monitor (VGA) is connected while xorg/desktop enviroment is
running, xorg will crash, the screen will turn black and only the mouse cursor
will show, with everything else 'frozen' as well. (Happens all the time)
+ 1) When a monit
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/36196315/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/36196317/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36196318/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
1) When a monitor (VGA) is connected while xorg/desktop enviroment is running,
xorg will crash, the screen will turn black and only the mouse cursor will
show, with everything else 'frozen' as well. (Happens all the time)
->Should not crash
2) Whe
28 matches
Mail list logo
