FYI, you can reset this setting from the command line using 'xset mouse
default'. I'm not saying that's a permanent solution to this bug, just
wanted to make sure people knew of it as a workaround until this is
resolved.
I would also like to have a "return to defaults" button in that dialog.
--
Forgive me if I'm confusing this bug with the one about moving buttons
back to the right side of the window, but I actually like this order:
gconftool-2 --set /apps/metacity/general/button_layout --type string
"minimize,maximize:close"
It seems to me that there is some argument is around having t
Wow! That finally explains why I could never get gnome-keyring to manage
my ssh key: I renamed id_rsa.pub to something useful for being scp'd
over to other hosts. I created a symlink and it works great now!
Fantastic!
So with seahorse/keyring properly recognizing my SSH key now I care a
lot less a
In bug 397145 it was pointed out that importing your ssh keys happens
automatically if ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub are both present.
Did you maybe rename your public key file? That was what make the SSH
agent stuff not work on my system. I haven't tested, but I suspect that
key importing mi
Public bug reported:
Binary package hint: seahorse-plugins
I'm trying to make gnome-keyring work as my SSH key forwarding agent
properly but I've run into trouble with how my public key is detected.
It seems to be the case that gnome-keyring will automagically recognize
any file matching ~/.ssh/i
This may be related to bug 397145 which I just filed. Basically I
suspect that seahorse and gnome-keyring-manager refuse to recognize the
id_rsa file because it isn't recognized as the proper mime type. Can you
check your key file to see what mime type it is identified as?
Also, can someone who th
This still affects me in Karmic, on a fresh installation with a
different SSH key file.
Is there anyone who has Seahorse actually recognizing their SSH key? If
so can that person please comment on what mime type their key file is
detected as?
--
id_rsa not detected as x-pem-key
https://bugs.laun
I'm affected by this as well.
--
rhythymbox doesn't play cds (No URI handler implemented for "cdda")
https://bugs.launchpad.net/bugs/435035
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu.
--
desktop-bugs mailing
I actually have some relevant libraries here..
$ dpkg -L libgstreamer-plugins-base0.10-0 |grep cdda
/usr/lib/libgstcdda-0.10.so.0.18.0
/usr/lib/libgstcdda-0.10.so.0
Shouldn't those be enough for me to play audio CDs with?
--
rhythymbox doesn't play cds (No URI handler implemented for "cdda")
ht
shared-mime-info 3.39-1ubuntu1
seahorse 2.22.2-0ubuntu1
I don't think this has been fixed, but the issue may be moot. It seems
that Seahorse doesn't do SSH key management anymore, it's now the
responsibility of gnome-keyring[1] and there doesn't seem to be a UI for
it. This mime info may still be
Public bug reported:
Binary package hint: gedit
I had just created a file and tried to open it from the file browser
sidebar. The file was located on a remove server via SSH/SFTP.
ProblemType: Crash
Architecture: i386
Date: Wed Apr 4 10:57:00 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/7144548/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/7144585/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/7144601/Disassembly.txt
** Attachm
Public bug reported:
Binary package hint: gtk2-engines-ubuntulooks
See this bug at Mozilla:
https://bugzilla.mozilla.org/show_bug.cgi?id=367509
There seems to be some issue with the ubuntulooks engine that causes
Firefox 3 trunk builds to show memory leak behavior when FF starts. When
I launch a
13 matches
Mail list logo
