[Bug 771448] Re: desktop wall edge flipping broken
Nevermind about event windows - I hadn't realized 'desktop wall' depends on 'mouse position polling'. It seems to be a problem with the latter then - perhaps it's not sending position events reliably? I just tried reducing the polling interval, with no effect. But then I tried disabling polling entirely - temporarily disabling wall - and then re-enabling both. Success! Flipping is working fine again. For now, anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771448 Title: desktop wall edge flipping broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/771448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771448] Re: desktop wall edge flipping broken
Well, pointer edge flipping was working flawlessly for a while with the mouse button binding workaround, but now edge flipping is back to only working infrequently or erratically at best. A recent update seems to have hosed it. I have two laptops suffering the problem now. More updates/review: Toggling the edge flipping or restarting compiz no longer seem to result in a "honeymoon" period of a few viewport switches as they once seemed to. It's erratic all the way. Dragging windows also no longer helps. Drags will be block similar to cursor moves. The behavior also seems slightly different on the two laptops - one, the x300, is running unity. Edge flipping actually works fine - until compiz crashes - then, when compiz is restarted from the console, edge flipping becomes unreliable. On the x201, in normal mode, it seems to be erratic from the beginning. All edge directions are susceptible to failure, but it seems to have particular difficulty with 'top'/'up'. Perhaps the last indicates it is something to do with panels or other windows 'hiding' compiz' event windows? OId compiz seemed to have this down pat, but I remember keeping event windows in the right place was a nightmare on a window manager whose source code I was playing around with years ago. I do have a top panel - unity or regular - in both setups. I also feel like the unity one may have extra difficulty with 'up' AND 'left', which would fit. Or when other windows overlap the edge of the screen. (However, it is all so erratic it is hard to tell for sure.) Altogether a major (and frustrating) regression in any case. Please let me know if there's anything I can do ot help debug or test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771448 Title: desktop wall edge flipping broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/771448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771448] Re: desktop wall edge flipping broken
Piling on. I've been living with this since switching over to alpha Natty repositories several months ago. Figured it was just screwed up configuration, or would sort itself out , but recently did a clean upgrade on a second computer and am seeing exactly the same issue. Edge flipping will work a few times (anywhere from once to a few dozen), and then stop. Extremely aggravating, since it's so random. As observed by the others, grabbing a title bar and moving a window around a little (usually) seems to reset things - temporarily. So does unchecking and rechecking the option in compizconfig, or disabling and reenabling wall. (Occasionally, it seems to develop a pattern, where particular sides are more problematic than others: for example, after "resetting" as above, doing nothing but flipping left and right will seem to work fine for some time, but not up and down - and trying to will break left/right as well. This may be my imagination though. It's hardly consistent.) Derek's workaround seems to work (thanks Derek, big relief!). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771448 Title: desktop wall edge flipping broken -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434520] Re: Pulseaudio refuses to use internal microphone input (Lenovo X300)
I'm on the road with a different computer so can't test at the moment, but will the first chance I get. I think my reasoning while flailing about to come up with the workaround was the hope that maybe pulseaudio might not be quite as "smart" or vigilant about (mis)managing the second card instance. In other words, the second instance might work like all instances did in Jaunty*, where alsamixer could be used to manually switch to the correct device right under pulseaudio's nose, and thus escape whatever bad or misinterpreted metadata pulseaudio is using to choose the wrong mic. It does seem to sort of work that way in practice, but I have no idea whether that's what is actually happening, or why. * Note that the same bug was also present back in Jaunty -- the workaround had fewer steps, but pulseaudio still activated the wrong mic initially. -- Pulseaudio refuses to use internal microphone input (Lenovo X300) https://bugs.launchpad.net/bugs/434520 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 434520] Re: Pulseaudio refuses to use internal microphone input (Lenovo X300)
Ok, I've at least found a workaround, but the bug is still present:
Manually loading an alsa source in /etc/pulse/default.pa works ("load-
module module-alsa-source device=hw:0,0").
This adds an "Internal Audio" input device, in additon to the auto-
loaded (udev?) "Internal Audio Analog Stereo".
After configuring alsa levels with alsamixer, the manually loaded
"Internal Audio" device works for recording. The auto-loaded "Internal
Analog Stereo" device still behaves incorrectly (no sound is produced,
and selecting it misconfigures the alsa levels; they have to be
readjusted before the manual device works again).
--
Pulseaudio refuses to use internal microphone input (Lenovo X300)
https://bugs.launchpad.net/bugs/434520
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 434520] Re: Pulseaudio refuses to use internal microphone input (Lenovo X300)
I did just discover that I can make gnome-sound-recorder, and probably other gstreamer apps, work by bypassing pulseaudio entirely for input. Just use gstreamer-properties to select Alsa as the input plugin (I also have to select my specific device "AD198x Analog", as default doesn't work). This isn't an entirely satisfactory solution, however. Pulseaudio input is still crippled, and Skype, for example, appears to rely on pulseaudio only nowadays. -- Pulseaudio refuses to use internal microphone input (Lenovo X300) https://bugs.launchpad.net/bugs/434520 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 434520] Re: Pulseaudio refuses to use internal microphone input (Lenovo X300)
Larry's suggestion doesn't work for me. Or rather, it might, but I can't find the "volume icon in the top panel" he refers to. (Perhaps it's a non-default applet that I don't have installed?) I only have the standard panel volume control, which has a volume slider on left click, and a menu with "mute" and "sound preferences" on right click. "Sound preferences" brings up the standard sound preferences control panel, which is unhelpful. Also, this bug is still present, exactly as originally described, in Lucid Alpha 2. -- Pulseaudio refuses to use internal microphone input (Lenovo X300) https://bugs.launchpad.net/bugs/434520 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 462646] [NEW] Associate a proxy with a network connection
Public bug reported: Wishlist: There should be a way to associate a proxy configuration with a particular wireless network. In my case, I use an iphone as an internet proxy over an ad hoc network. It's a relatively minor annoyance, but currently after setting up the network, I have to manually change the proxy configuration (and then sometimes I forget to change it back). I'd like to tell network manager which proxy configuration profile to use, and have it automatically set that whenever I'm using the network and unset it when done. I'm sure there are many other situations where people would want proxy configurations tied to particular network configurations. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- Associate a proxy with a network connection https://bugs.launchpad.net/bugs/462646 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 462625] [NEW] fix handling of previously created ad-hoc networks
Public bug reported: Use case: I use a proxy server running on an iphone to get mobile internet. This requires creating an ad-hoc network on my laptop, then joining the iphone to it. I'd like to easily connect/recreate this network whenever no other known networks are available. The problem: Once created, if I leave the new ad hoc network as "connect automatically", network manager sometimes uses it even when [preferred] regular networks are in range. If I turn off "connect automatically", there doesn't appear to be a way to easily recreate the network: it doesn't seem to reliably show up in the menu of available networks, and although the connection is selectable under the dropdown in the "Create New Wireless Network" dialog, if anything other then "New..." is selected there, the "Create" button remains inactive. How it should work: Previously created ad-hoc networks should always be available in the connection menu, either included with the scan results, or at the bottom of the menu (maybe replace the "Create New Wireless Network..." item with a "Create a Network >" submenu containing previously configured networks along with a "new..." item.) Alternatively (or additionally) there ought to be a way to prioritize the list of known/previously-used networks, so that network manager would never attempt to use the "iphone" network unless NO other [known] networks were available. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- fix handling of previously created ad-hoc networks https://bugs.launchpad.net/bugs/462625 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 434520] Re: Pulseaudio refuses to use internal microphone input (Lenovo X300)
Yes. The "analog stereo duplex" profile is selected in the Hardware tab. There is only one device available in the Input tab - "Internal Audio Analog Stereo". -- Pulseaudio refuses to use internal microphone input (Lenovo X300) https://bugs.launchpad.net/bugs/434520 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 434520] Re: Pulseaudio refuses to use internal microphone input (Lenovo X300)
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/32238681/AlsaDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/32238682/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/32238683/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/32238684/Card0.Codecs.codec.0.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/32238685/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/32238686/Dependencies.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/32238687/PciMultimedia.txt -- Pulseaudio refuses to use internal microphone input (Lenovo X300) https://bugs.launchpad.net/bugs/434520 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 434520] [NEW] Pulseaudio refuses to use internal microphone input (Lenovo X300)
Public bug reported: Binary package hint: pulseaudio Pulseaudio seems to have decided that the ALSA "Mic" capture device on my machine is the only one it will use. "Internal Mic" is the correct one (at least when no external mic is plugged in). If I use alsamixer to switch to the correct capture device, the pulseaudio volume controls instantly marks its input device as "muted" (and no sound is captured with, e.g., gnome sound recorder). Un-muting within the pulseaudio volume control again switches the alsa mixer back to the incorrect "Mic" device (which captures only noise). There doesn't seem to be any way to tell pulseaudio which capture channel to use. Pulseaudio level meter show the same thing - noise when the incorrect "Mic" device is active, but completely muted if alsamixer is used to change to the right device. Everything works fine if I boot a jaunty live disk - the alsa configuration and device detection seems exactly the same, but alsamixer can be used to switch active devices underneath pulseaudio. Sound recorder and pulseaudio level meters show noise on the "Mic" device, but correct capture when the "Internal Mic" is active. (And muting with the pulseaudio only deselects the "Capture" level control in alsamixer, it does not activate "Mic" and deactivate "Internal Mic".) This may be a duplicate of Bug #414215, but it didn't seem quite the same to me. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oliver 3202 F pulseaudio oliver 3493 F alsamixer /dev/snd/pcmC0D0p: oliver 3202 F...m pulseaudio /dev/snd/pcmC0D0c: oliver 3202 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfa22 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,17aa20fb,00100200' Controls : 14 Simple ctrls : 10 Date: Tue Sep 22 03:53:35 2009 DistroRelease: Ubuntu 9.10 Package: pulseaudio 1:0.9.18-0ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.34-generic SourcePackage: pulseaudio Uname: Linux 2.6.31-10-generic x86_64 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Pulseaudio refuses to use internal microphone input (Lenovo X300) https://bugs.launchpad.net/bugs/434520 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 434521] Re: Pulseaudio refuses to use internal microphone input (Lenovo X300)
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/32238721/AlsaDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/32238722/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/32238723/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/32238724/Card0.Codecs.codec.0.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/32238725/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/32238726/Dependencies.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/32238727/PciMultimedia.txt -- Pulseaudio refuses to use internal microphone input (Lenovo X300) https://bugs.launchpad.net/bugs/434521 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 434521] [NEW] Pulseaudio refuses to use internal microphone input (Lenovo X300)
Public bug reported: Binary package hint: pulseaudio Pulseaudio seems to have decided that the ALSA "Mic" capture device on my machine is the only one it will use. "Internal Mic" is the correct one (at least when no external mic is plugged in). If I use alsamixer to switch to the correct capture device, the pulseaudio volume controls instantly marks its input device as "muted" (and no sound is captured with, e.g., gnome sound recorder). Un-muting within the pulseaudio volume control again switches the alsa mixer back to the incorrect "Mic" device (which captures only noise). There doesn't seem to be any way to tell pulseaudio which capture channel to use. Pulseaudio level meter show the same thing - noise when the incorrect "Mic" device is active, but completely muted if alsamixer is used to change to the right device. Everything works fine if I boot a jaunty live disk - the alsa configuration and device detection seems exactly the same, but alsamixer can be used to switch active devices underneath pulseaudio. Sound recorder and pulseaudio level meters show noise on the "Mic" device, but correct capture when the "Internal Mic" is active. (And muting with the pulseaudio only deselects the "Capture" level control in alsamixer, it does not activate "Mic" and deactivate "Internal Mic".) This may be a duplicate of Bug #414215, but it didn't seem quite the same to me. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oliver 3202 F pulseaudio oliver 3493 F alsamixer /dev/snd/pcmC0D0p: oliver 3202 F...m pulseaudio /dev/snd/pcmC0D0c: oliver 3202 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfa22 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,17aa20fb,00100200' Controls : 14 Simple ctrls : 10 Date: Tue Sep 22 03:53:35 2009 DistroRelease: Ubuntu 9.10 Package: pulseaudio 1:0.9.18-0ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.34-generic SourcePackage: pulseaudio Uname: Linux 2.6.31-10-generic x86_64 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Pulseaudio refuses to use internal microphone input (Lenovo X300) https://bugs.launchpad.net/bugs/434521 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 282387] Re: scrollwheel emulation breaks after suspend with 2.6.27-7
5f2c8a2dcdf98b39997ee5e7c9a9ace3b640bfa3 seems to be working well for me so far. Thanks Niklas. (NB: I did have to manually install a couple extra xorg related -dev packages to compile it.) -- scrollwheel emulation breaks after suspend with 2.6.27-7 https://bugs.launchpad.net/bugs/282387 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 282387] Re: scrollwheel emulation breaks after suspend with 2.6.27-7
I'm also experiencing this problem: scroll emulation set with xinput works initially, but stops working after a suspend/resume. Same versions as above. I'll add that it also stops working after a mere VT switch (which may be the real cause, since suspend/resume seems to do a VT switch implicitly). Trying to turn it back on with xinput seems to partly work: button 2 presses stop being emitted and the cursor freezes while button 2 is down, but no button 4/5 events are emitted. (And, occasionally, re- running xinput WILL work after suspend/resume.) -- scrollwheel emulation breaks after suspend with 2.6.27-7 https://bugs.launchpad.net/bugs/282387 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 82518] Merge upstream unix2_chkpwd
I have the same problem with libpam-unix2 1.25-1.1 and gnome-screensaver 2.17.7-0ubuntu2. The problem is exactly as described in Debian #295526 above: gnome- screensaver drops any privileges it has by the time it calls into PAM, but pam_unix2 needs to read the hash from the shadow file. The regular pam_unix module calls unix_chkpwd when it discovers this situation. The same solution should work with pam_unix2. If the security implications of this approach are acceptable in pam_unix, they should be here as well. -- problems with libpam-unix2 and gnome-screensaver https://launchpad.net/bugs/82518 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
