There is no known workaround for this yet.
I used to work well in Ubuntu 12.04, with options ath9k nohwcrypt=1.
I am using Ubuntu 13.04 x86-64 with packages up to date.
Tried compat-drivers 3.8.3-2-snpu and 3.9-rc4-2-su with no luck.
--
You received this bug notification because you are a
This is probably caused by the following cntlm bug:
http://sourceforge.net/tracker/?func=detailaid=3512077group_id=197861atid=963162
It can be seen by the network traffic that package-data-downloader
(through urllib) is using HTTP/1.0, the whole file is transfered and
then the connection hangs.
I am targeting this to cntlm package because apparently there is nothing
wrong with update-notifier nor with urllib.
** Package changed: update-notifier (Ubuntu) = cntlm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: ruby-gnome2
rubyripper [1] is performing poorly in maverik x86-64 (up-to-date). They
have an open issue for this [2].
Apparently there is nothing wrong with rubyripper. So I managed to
reduce it to a small test case. It is based in the very first ruby-
Public bug reported:
Binary package hint: cntlm
Ubuntu release: 10.10 desktop x86_64
Package version: 0.91~rc6-0ubuntu1
The stop command of cntlm's init.d script always fails.
Apparently it's about a syntax error specifyind the argument to the
retry switch when invoking start-stop-daemon.
** Patch added: proposal fix
https://bugs.launchpad.net/bugs/660515/+attachment/1692522/+files/cntlm.diff
--
problem with /etc/init.d/cntlm stop
https://bugs.launchpad.net/bugs/660515
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is still present in the 10.10 release.
I spent some time to figure out that the dot was not allowed in
usernames.
IMHO this UI bug is very annoying because it's often difficult to guess
what's going on and could end up with the user aborting the install.
--
Ubiquity in Lucid beta 1
xmacrorec not working in ubuntu 9.10 (x86-64). the description at
comment #20 describe it well.
cnee is really segfaulting.
--
xmacro quit-key no longer recognized
https://bugs.launchpad.net/bugs/367685
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The bug was confirmed by at least 3 users.
** Changed in: gnome-keyring (Ubuntu)
Status: New = Confirmed
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of
Setting status to new, since I believe anyone is able reproduce this issue
based on my last message.
Waiting for confirmation.
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete = New
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
I'm using jaunty i386 and I started to experience the same issue.
Everything was ok then I generated a keypair using ssh-keygen with a
non-empty passphrase. I copied it to my target machine's
.ssh/authorized_keys file and ssh command was able to log in (the
passphrase was asked in a window
Same issue with interpid desktop live cd (x86-64), following this:
https://help.ubuntu.com/community/Installation/FromLinux
partman does not recognize any of my hard disk partitions.
--
Partition selection window goes blank during installation
https://bugs.launchpad.net/bugs/201286
You received
Public bug reported:
It just happens at a cold boot.
The boot process starts normally, but when the X server is about to get
control of the video card I get a black screen. Apparently no system
activity and no mouse cursor. Can't switch virtual terminals also. But
there is video signal, a black
** Attachment added: Xorg.log.tar.gz
http://launchpadlibrarian.net/14549131/Xorg.log.tar.gz
--
System crashes at X.org start after cold boot (using nvidia driver)
https://bugs.launchpad.net/bugs/230913
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes, my problem was like the bug #91064.
From what I could understand the legacy driver can't properly do GLX rendering
with the X protocol extension Composite enabled.
So the driver disables it by default (when we have Composite).
# cat /var/log/Xorg.0.log | grep GLX
(II) Loading extension GLX
I might have the same problem.
driver nvidia (nvidia-glx-legacy) configured properly.
glxinfo output:
Xlib: extension GLX missing on display :0.0.
Xlib: extension GLX missing on display :0.0.
Xlib: extension GLX missing on display :0.0.
Error: couldn't find RGB GLX visual
Xlib: extension GLX
16 matches
Mail list logo
