[Bug 561125] Re: WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()
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/561125 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561125] Re: WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564356] [NEW] [Lucid] Hotkeys not fully working on Eee 1005ha
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-fuctioning hotkeys are: On/Off Touchpad, Change resolution, switch to vga/mirror screen etc (but I think this one has never been implemented anyway), and system monitor. (F3, F4, F8, F9, respectively) (However Turn off screen/backlight (F7) is working, which is a very handy hotkey to have. It was not earlier) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: acpi-support 0.134 ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Thu Apr 15 19:04:52 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318) ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: acpi-support ** Affects: acpi-support (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- [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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564356] Re: [Lucid] Hotkeys not fully working on Eee 1005ha
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532844] Re: Lucid: White symbols on light panel and Ubuntu Logo are difficult to see
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 542435] Re: White Icons not clearly visible on low contrast screens
*** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525302] Re: gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError in __init__() )
@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 __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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532633] Re: [light-theme] please revert the order of the window controls back to menu:minimize, maximize, close
@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. Since the decision is to put the buttons on the left now, the only logical, and understandable action to take would be to completely mirror the original layout onto the left. Therefore making the order, Close - maximize - minimize. Note that this still isn't the same as OSX. (OSX- Close, Minimize, Maximize) Now, I can see you give the counterpoint that it's in the same order on the left as it is on the right. Sure it's a valid point, but the brain still tends to want to click the [left] corner to close, because it used to be in a corner originally. I still don't understand what is holding us back from keeping the button layout on the left, but in a different order. If you could explain, it would be great, so people, like me, will stop worrying and trying to give counterpoints in an attempt to persuade somebody, that might, or might not be listening. (It's like firing a gun a night) There should not be any reason to not make a huge change, slightly less easier to adapt to. Thanks, and I hope you and the design team will still consider some sort of change to the order.. of course, if you had the time to read this. -- [light-theme] please revert the order of the window controls back to menu:minimize,maximize,close https://bugs.launchpad.net/bugs/532633 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 542435] [NEW] White Icons not clearly visible on low contrast screens
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 than the current light grey background, to create more contrast, and therefore visible. For example, at its current color, on a Asus Eee 1005ha, it is about only 10% visible, maybe even less, depending on screen angle. ProblemType: Bug Architecture: i386 Date: Fri Mar 19 22:46:48 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318) Package: gdm 2.29.92-0ubuntu3 ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: gdm Uname: Linux 2.6.32-16-generic i686 ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug beta beta1 i386 lucid -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 542435] Re: White Icons not clearly visible on low contrast screens
** 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 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 than the current light grey background, to create more contrast, and therefore visible. For example, at its current color, on a Asus Eee 1005ha, it is about only 10% visible, maybe even less, depending on screen angle. ProblemType: Bug Architecture: i386 Date: Fri Mar 19 22:46:48 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318) Package: gdm 2.29.92-0ubuntu3 ProcEnviron: - LANG=en_CA.utf8 - SHELL=/bin/bash + LANG=en_CA.utf8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: gdm Uname: Linux 2.6.32-16-generic i686 -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532633] Re: [light-theme] please revert the order of the window controls back to menu:minimize, maximize, close
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 its own beliefs and mission Seeing as that changing the side of the window buttons is a pretty big UI change, many users feel that they aren't getting a say in the changes that they dislike, and is why there are a lot of negative thoughts, with negative attitudes. But, however, if it is put into perspective, it is reasonable to be acting in such a way. For years, ubuntu has had its window buttons on the same side, in the same order. With the new changes the buttons are now on the left, but not only that, they are in a different order. I strongly believe that this completely ruins the consistency factor of ubuntu. And on the other side, seeing as this is it's 10th release, and a LTS, it is also reasonable that there is going to be some change. However, the main problem is that every, every, every popular OS has the close button in a corner, and never towards the center...this is probably the greatest concern of all the people who are against the change, and NOT the side of the buttons. Whats done is done, unless the UI Freeze is lenient. But for NEXT TIME, Canonical should put extreme care in making sure users are satisfied. (Surveys, surveys, surveys, heck, even Google is doing it!) -- [light-theme] please revert the order of the window controls back to menu:minimize,maximize,close https://bugs.launchpad.net/bugs/532633 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532844] Re: Lucid: White symbols on light panel and Ubuntu Logo are difficult to see
@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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532844] Re: Lucid: White symbols on light panel and Ubuntu Logo are difficult to see
*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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525302] Re: gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError in __init__() )
@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://bugs.launchpad.net/bugs/525302 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525302] Re: gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError in __init__() )
@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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525302] Re: gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError in __init__() )
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447259] Re: Internal microphone not working with certain programs
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525302] Re: gwibber-accounts crashed on trying to open it ( crashed with BadArgumentsError in __init__() )
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 497703] [NEW] NotifyOSD slow with repetitive notifications
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 problem when numerous notifications (that aren't
volume notifications) appear over top of each other and it waits for the
older one to disappear first, then shows the newer one later.
Volume and other notifications should not appear as if they popped up
one after another, but rather as if the OSD was one window with dynamic
text (and icons,etc) that change in real time, as notifications occur,
and not wait for the older ones to disappear.
(Also, ideally, clicking a notifcation should take you to the program it
came from, and/or close the OSD pop up {but this isn't really a bug so
i'll go post it on brainstorm as well} )
ProblemType: Bug
Architecture: i386
Date: Thu Dec 17 01:58:42 2009
DistroRelease: Ubuntu 9.10
GtkTheme: Inverted
IconTheme: elementary_2.2
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
MachineType: ASUSTeK Computer INC. 1005HA
Package: notify-osd 0.9.24-0ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic
root=UUID=0e4e4399-5b80-4763-8f60-a87a999551e6 ro quiet splash
ProcEnviron:
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
RelatedPackageVersions:
xserver-xorg 1:7.4+3ubuntu10
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-xorg-video-intel 2:2.9.0-1ubuntu2
xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: notify-osd
Uname: Linux 2.6.31-16-generic i686
WindowManager: compiz
dmi.bios.date: 09/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0905
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0905:bd09/23/2009:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
** Affects: notify-osd (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
NotifyOSD slow with repetitive notifications
https://bugs.launchpad.net/bugs/497703
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 497703] Re: NotifyOSD slow with repetitive notifications
** 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 ** Attachment added: Lsmod.txt http://launchpadlibrarian.net/36899507/Lsmod.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/36899508/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/36899509/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/36899510/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/36899511/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/36899512/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/36899514/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/36899515/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/36899516/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/36899517/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/36899518/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/36899519/Xrandr.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/36899520/XsessionErrors.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/36899521/glxinfo.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/36899522/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/36899524/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/36899525/xdpyinfo.txt -- NotifyOSD slow with repetitive notifications https://bugs.launchpad.net/bugs/497703 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447259] Re: Internal microphone does not work with certain programs
** 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447259] Re: Internal microphone does not work with certain programs
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 example on my eee 1005, it creates a static sound which does not go away unless you mute the output. In skype it can be solved by using the command /bin/sh -c PULSE_SERVER=127.0.0.1 skype , but sometimes causes the static sound to appear. This bug is LONG over due in being fixed, and is in my honest opinion, a HUGE bug, since programs like skype do not work. Many people rely on skype or other programs to call overseas, as well as family and friends, and since audio does not work, it is a major drawback for ubuntu. A non-working internal mic will make ALOT of laptop users not use ubuntu. This MUST be fixed for lucid, especially since its an LTS release - _everything_ should be expected to work, other than relatively new systems. -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447259] Re: Internal microphone does not work with certain programs
** 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 running Ubuntu 9.10 on my Acer Aspire One A150L and I find that in + some programs, the internal microphone won't record/output anything due + to a problem with pulseaudio. I've tried the following programs to see + whether the microphone works or not: Sound Recorder -- records clearly - Sound Preferences, Input tab -- volume meter shows little to no response - Pulseaudio Volume Meter (Recording) -- responds correctly + Sound Preferences, Input tab -- volume meter shows little to no response (Only responds slightly to extemely loud sounds and only when is amplified to max [which I think is 400%]) + Pulseaudio Volume Meter (Recording) -- responds correctly (On eee 1005ha - alot of background noise so the meter jumps up and down, but seems to pick up louder sounds) Pulseaudio Volume Control, Input Devices and Recording tabs -- volume meter shows little to no response, only get a response when I tap the microphone sharply - Skype 2.1 beta -- mic does not record + Skype 2.1 beta -- Does not recieve any microphone input on internal microphone. arecord -- volume meter responds - I've made sure to keep the recording volume to 100 before testing these - programs. This bug is non-existent in Ubuntu 9.04. + I've made sure to keep the recording volume to 100 before testing these programs. This bug is non-existent in Ubuntu 9.04. + (Exists in Karmic/9.10) + + Bug also existant on Eee 1005ha - most likely is a problem on all or + most Intel HDA devices with internal microphones. + ProblemType: Bug AplayDevices: - List of PLAYBACK Hardware Devices - card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of PLAYBACK Hardware Devices + card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of CAPTURE Hardware Devices + card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: davidoc1489 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: davidoc1489 F pulseaudio Card0.Amixer.info: - Card hw:0 'Intel'/'HDA Intel at 0x3854 irq 29' -Mixer name : 'Realtek ALC268' -Components : 'HDA:10ec0268,1025015b,00100101' -Controls : 8 -Simple ctrls : 5 + Card hw:0 'Intel'/'HDA Intel at 0x3854 irq 29' + Mixer name : 'Realtek ALC268' + Components : 'HDA:10ec0268,1025015b,00100101' + Controls : 8 + Simple ctrls : 5 Date: Fri Oct 9 15:15:24 2009 DistroRelease: Ubuntu 9.10 Package: pulseaudio 1:0.9.18-0ubuntu3 ProcEnviron: - LANG=en_IE.UTF-8 - SHELL=/bin/bash + LANG=en_IE.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: pulseaudio Tags: ubuntu-unr Uname: Linux 2.6.31-12-generic i686 ** Summary changed: - Internal microphone does not work with certain programs + Internal microphone not working with certain programs -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447259] Re: Internal microphone not working with certain programs
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, but unfortunately I don't.. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447259] Re: Internal microphone not working with certain programs
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 489520] Re: [Karmic] Xorg crashes and does not detect when VGA is connected
** 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 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) When a monitor (VGA) is connected before booting/starting xorg, screens work fine, however both displays are set at low resolution, and you need to change it to the monitors native resolution (in my case laptop is 1024x600 and monitor is 1280x720). When you set the resolutions to these, xorg crashes again, so you have to disable the laptop screen. In other words it is only able to display from one screen (need to retest this, if I remember to). - -Should display both screens, and preferably automatically choose native resolutions, instead of automatically using 'mirror screen', which defaults to the lower resolution, which usually ends up looking bad on larger displays. + - 3) When a vga monitor is plugged in, it is not detected quick enough - usually have to open up systemdisplay just so it 'finds' the monitor. + 2) When a monitor (VGA) is connected BEFORE booting/starting xorg, + screens work fine, however both displays are set at the + lowest/compatible resolution of both monitors (by default). You need to + change it to the monitors native resolution (in my case laptop is + 1024x600 and monitor is 1280x720). However, when you set the resolutions + to these, xorg crashes again, so you have to disable the laptop screen + before changing the resolution. In other words it is only able to + display from one screen (However this used to work with 9.04). + + -Should display both screens, and preferably automatically choose + native resolutions, instead of automatically using 'mirror screen', + which defaults to the lower resolution, which usually ends up looking + bad on larger displays. UPDATE--Screen resolutions are remembered (pre- + boot), but xorg still crashes if the situation in point 1 occurs. (even + if resolution is previously set) + + + + 3) When a vga monitor is plugged in, it is not detected quick enough - + usually have to open up systemdisplay just so it 'finds' the monitor. + --Update: It 'finds' the monitor, but xorg crashes as state in point 1 + - screen detection should have a 5 second timer? + + = Sorry if this is not enough information, this is my first bug report, and it's three in the morning. I will try to get more info if requested. - = Occured on: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) xorg: - Installed: 1:7.4+3ubuntu7 + Installed: 1:7.4+3ubuntu7 9.10 / Karmic Asus Eee 1005ha One VGA output (no HDMI) ProblemType: Bug Architecture: i386 Date: Sat Nov 28 02:55:34 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MachineType: ASUSTeK Computer INC. 1005HA Package: xorg 1:7.4+3ubuntu7 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-15-generic root=UUID=0e4e4399-5b80-4763-8f60-a87a999551e6 ro quiet splash ProcEnviron: - LANG=en_CA.UTF-8 - SHELL=/bin/bash + LANG=en_CA.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-15.50-generic RelatedPackageVersions: - xserver-xorg 1:7.4+3ubuntu7 - libgl1-mesa-glx 7.6.0-1ubuntu4 - libdrm2 2.4.14-1ubuntu1 - xserver-xorg-video-intel 2:2.9.0-1ubuntu2 - xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1 + xserver-xorg 1:7.4+3ubuntu7 + libgl1-mesa-glx 7.6.0-1ubuntu4 + libdrm2 2.4.14-1ubuntu1 + xserver-xorg-video-intel 2:2.9.0-1ubuntu2 + xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1 SourcePackage: xorg Uname: Linux 2.6.31-15-generic i686 XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 09/23/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1005HA dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0905:bd09/23/2009:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1005HA dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. fglrx: Not loaded system: - distro: Ubuntu - architecture:
[Bug 489520] [NEW] [Karmic] Xorg crashes and does not detect when VGA is connected
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) When a monitor (VGA) is connected before booting/starting xorg, screens work fine, however both displays are set at low resolution, and you need to change it to the monitors native resolution (in my case laptop is 1024x600 and monitor is 1280x720). When you set the resolutions to these, xorg crashes again, so you have to disable the laptop screen. In other words it is only able to display from one screen (need to retest this, if I remember to). -Should display both screens, and preferably automatically choose native resolutions, instead of automatically using 'mirror screen', which defaults to the lower resolution, which usually ends up looking bad on larger displays. 3) When a vga monitor is plugged in, it is not detected quick enough - usually have to open up systemdisplay just so it 'finds' the monitor. - screen detection should have a 5 second timer? Sorry if this is not enough information, this is my first bug report, and it's three in the morning. I will try to get more info if requested. = Occured on: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) xorg: Installed: 1:7.4+3ubuntu7 9.10 / Karmic Asus Eee 1005ha One VGA output (no HDMI) ProblemType: Bug Architecture: i386 Date: Sat Nov 28 02:55:34 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MachineType: ASUSTeK Computer INC. 1005HA Package: xorg 1:7.4+3ubuntu7 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-15-generic root=UUID=0e4e4399-5b80-4763-8f60-a87a999551e6 ro quiet splash ProcEnviron: LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-15.50-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu7 libgl1-mesa-glx 7.6.0-1ubuntu4 libdrm2 2.4.14-1ubuntu1 xserver-xorg-video-intel 2:2.9.0-1ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1 SourcePackage: xorg Uname: Linux 2.6.31-15-generic i686 XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 09/23/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1005HA dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0905:bd09/23/2009:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1005HA dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. fglrx: Not loaded system: distro: Ubuntu architecture: i686kernel: 2.6.31-15-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- [Karmic] Xorg crashes and does not detect when VGA is connected https://bugs.launchpad.net/bugs/489520 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 489520] Re: [Karmic] Xorg crashes and does not detect when VGA is connected
** 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 ** Attachment added: Lspci.txt http://launchpadlibrarian.net/36196319/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/36196320/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/36196321/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/36196322/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/36196323/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/36196324/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/36196325/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/36196326/UdevLog.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/36196327/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/36196328/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/36196329/Xrandr.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/36196330/XsessionErrors.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/36196331/glxinfo.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/36196332/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/36196333/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/36196334/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/36196335/xkbcomp.txt -- [Karmic] Xorg crashes and does not detect when VGA is connected https://bugs.launchpad.net/bugs/489520 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
