I would love to see evidence from an actual user test showing that the
original behavior was confusing, because I'm skeptical that any such
evidence exists.
Can somebody find even *one* user who was confused?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've hacked back in the old behavior and created a PPA:
https://launchpad.net/~ef/+archive/grid-cycling
At the moment it's waiting in the build queue, and will be for several
hours.
If you're adventurous and on amd64, you can try these. They work for me,
but that's no guarantee they won't
I'm seeing the same problem as Carlos, but in addition the top-right
position doesn't work at all. Instead it behaves just like center-top.
So my Ctr-Alt-KP8 and Ctr-Alt-KP9 buttons do the exact same thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
It's possible to rebind or disable Unity's Alt-Tab key (through CCSM or
gconf-editor), but its Alt-Grave key is hard-coded.
This makes it impossible to use said key with compiz's other window
switchers (unless you completely abandon unity shell).
I thought I must just be
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/878915
Title:
Unity Shell Plugin hard-coded key binding
To manage notifications about this bug go to:
The gnome bug is already closed as NOTGNOME, because this is an Ubuntu-
specific problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875070
Title:
gnome terminal intercepts my alt key
I'm not running on the same hardware anymore, so unfortunately I can't
easily reproduce. Thanks for your help.
--
pulseaudio unusable (es1968 driver on karmic)
https://bugs.launchpad.net/bugs/480543
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: emacs23
One of the best new features in emacs23 is --daemon. An emacs daemon
can persist as long as you want, across login sessions. However, this
doesn't work well in Karmic because of two issues:
1. The XAUTHORITY environment variable changes with
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35738541/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/35738542/XsessionErrors.txt
--
Ubuntu doesn't play well with emacs --daemon across sessions
Still seeing the same behavior. Nothing but clicks, and pulseaudio is
killed when I kill the client.
pulseaudio package is version 1:0.9.20-0ubuntu1~~karmic~ubuntuaudiodev1
Log attached.
** Attachment added: pulseaudio -
http://launchpadlibrarian.net/35679490/pulse.log
--
pulseaudio
Public bug reported:
Binary package hint: pulseaudio
Constant underruns are making pulseaudio completely unusable.
Applications trying to play sound seem to hang.
But I can play sound with no problems if I send it directly through oss
(with ogg123 -d oss, for example).
pulseaudio complains
** Attachment added: output of pulseaudio -vv
http://launchpadlibrarian.net/35519959/pulse.log
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/35519960/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/35519961/AplayDevices.txt
**
** Attachment added: output of pulseaudio -vv
http://launchpadlibrarian.net/35561732/pulse.log
--
pulseaudio unusable (es1968 driver on karmic)
https://bugs.launchpad.net/bugs/480543
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks, but that doesn't fix it. The above attachment is the pulseaudio
output with tsched=0. There are still frequent glitches and complaints
about the driver.
--
pulseaudio unusable (es1968 driver on karmic)
https://bugs.launchpad.net/bugs/480543
You received this bug notification because
I put these lines in limits.conf:
@audio - rtprio 99
@audio - nice -10
@audio - memlock unlimited
And ensured that my user in is the audio group. But still no
improvement.
The sound card works flawlessly with OSS, and under WinXP, so it's hard
to not blame pulseaudio.
Also, what is the
Yes, I rebooted just to be sure.
--
pulseaudio unusable (es1968 driver on karmic)
https://bugs.launchpad.net/bugs/480543
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
That's essentially what I'm already doing, is there something wrong with
the logs I've been attaching?
Will run with - instead of just -vv...
--
pulseaudio unusable (es1968 driver on karmic)
https://bugs.launchpad.net/bugs/480543
You received this bug notification because you are a member
Ok, new log. My test case here was playing a file via mpg123. I got
nothing but clicks, and then when I killed mpg123, the pulse daemon also
died.
** Attachment added: pulseaudio -
http://launchpadlibrarian.net/35563451/pulseverbose.log
--
pulseaudio unusable (es1968 driver on karmic)
By died I mean, was killed by SIGKILL. Not sure what sends the signal.
--
pulseaudio unusable (es1968 driver on karmic)
https://bugs.launchpad.net/bugs/480543
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I gave up on Jaunty for now. I'm running Arch's stock 2.6.28 kernel
with no problems.
--
linux 2.6.28 don't boot
https://bugs.launchpad.net/bugs/343268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Yup, still having the problem under 2.6.28-10.
Attaching a photo of the kernel panic I get under this kernel.
** Attachment added: bug.jpg
http://launchpadlibrarian.net/24004030/bug.jpg
--
linux 2.6.28-9 don't boot
https://bugs.launchpad.net/bugs/343268
You received this bug notification
I am having the same problem, although I'm on different hardware and I'm
not sure if it's the same bug.
I upgraded to Jaunty from Ibex. It ran ok for several weeks, but
eventually a kernel update made it hang during boot. If I boot in
rescue mode I can see a kernel panic in the init process
22 matches
Mail list logo
