[Bug 151365] Re: Autosave doesn't work for Unsaved Documents
Seen this too, same problem: a laptop outage. jedit does this, I'll be using it on the laptop. -- Autosave doesn't work for Unsaved Documents https://bugs.launchpad.net/bugs/151365 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 621853] Re: palimpsest crashed with SIGSEGV while looking at bad volume
I'll have a go at recreating this problem... -- palimpsest crashed with SIGSEGV while looking at bad volume https://bugs.launchpad.net/bugs/621853 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 621853] Re: palimpsest crashed with SIGSEGV while looking at bad volume
** Attachment added: CoreDump.gz https://bugs.launchpad.net/bugs/621853/+attachment/1508656/+files/CoreDump.gz ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/621853/+attachment/1508657/+files/Dependencies.txt ** Attachment added: Disassembly.txt https://bugs.launchpad.net/bugs/621853/+attachment/1508658/+files/Disassembly.txt ** Attachment added: ProcMaps.txt https://bugs.launchpad.net/bugs/621853/+attachment/1508659/+files/ProcMaps.txt ** Attachment added: ProcStatus.txt https://bugs.launchpad.net/bugs/621853/+attachment/1508660/+files/ProcStatus.txt ** Attachment added: Registers.txt https://bugs.launchpad.net/bugs/621853/+attachment/1508661/+files/Registers.txt ** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/621853/+attachment/1508662/+files/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/621853/+attachment/1508663/+files/ThreadStacktrace.txt ** Visibility changed to: Public -- palimpsest crashed with SIGSEGV while looking at bad volume https://bugs.launchpad.net/bugs/621853 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 187127] Re: ssh always asks to unlock private key with no password set
Still seeing this on Ubuntu 10.04; the unset SSH_AUTH_SOCK trick works -- ssh always asks to unlock private key with no password set https://bugs.launchpad.net/bugs/187127 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 442078] Re: Buttons in Eclipse not working correctly with GTK+ 2.18.1-1
Having just hit this, it's unfair to blame any particular group. You can't blame the eclipse team as their code worked; you can't blame the GTK team as they followed the spec. Its just together, it makes the transition to Ubuntu 9:10 the most painful ubuntu upgrade for a while, certainly I'm not enjoying it much on the two machines I've upgraded. If you ever have the opportunity to look at the windows OS code, you will see truckloads of compatbility flags that get set on an app-by-app basis; MS believe that backwards compatibility is the strength of their OS, though it adds to bloat, complicates testing, and hits performance (more code to pull in, more branch misprediction). Apple take a stricter view. I think here linux/ubuntu is taking the Apple view: you get it wrong, you deal with it. While it will be dealt with, it is causing a lot of short term pain. -- Buttons in Eclipse not working correctly with GTK+ 2.18.1-1 https://bugs.launchpad.net/bugs/442078 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 437429] Re: No GUI to configure/disable login sound
I know this is really annoying, and a regression, but a login sound you can't easily disable is a feature of Windows Mobile and of OS/X. So it could be argued that this feature is simply being consistent with other consumer OSes. Of course, if the goal is to be better, then yes, it is a bug -- No GUI to configure/disable login sound https://bugs.launchpad.net/bugs/437429 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 187127] Re: ssh always asks to unlock private key with no password set
let me have a check. I think the problem was @home, judging by the log. That machine is interesting as calls to getLocalHost() don't always work, which is very good for finding assumptions in code, including anything that relies on an ORB to work reliably https://issues.apache.org/jira/browse/IVY-817 https://issues.apache.org/jira/browse/HADOOP-3426 http://jira.smartfrog.org/jira/browse/SFOS-697 On Tue, Apr 21, 2009 at 9:21 AM, Sebastien Bacher seb...@ubuntu.com wrote: do you still have the issue? do you have public keys as described on the GNOME bug? -- ssh always asks to unlock private key with no password set https://bugs.launchpad.net/bugs/187127 You received this bug notification because you are a direct subscriber of the bug. -- ssh always asks to unlock private key with no password set https://bugs.launchpad.net/bugs/187127 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 187127] Re: ssh always asks to unlock private key with no password set
I am seeing that today, its new. What does auth.log say? Jan 23 14:59:48 k2 gdm[5733]: pam_unix(gdm:session): session opened for user slo by (uid=0) Jan 23 14:59:48 k2 gdm[5733]: pam_ck_connector(gdm:session): nox11 mode, ignoring PAM_TTY :0 Jan 23 14:59:48 k2 gdm[5733]: gnome-keyring-daemon: couldn't lookup keyring component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified Jan 23 14:59:48 k2 gdm[5733]: Autolaunch error: X11 initialization failed. Jan 23 14:59:48 k2 gdm[5733]: )gnome-keyring-daemon: couldn't lookup ssh component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified Jan 23 14:59:48 k2 gdm[5733]: Autolaunch error: X11 initialization failed. Jan 23 14:59:48 k2 gdm[5733]: )gnome-keyring-daemon: couldn't lookup pkcs11 component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified Jan 23 14:59:48 k2 gdm[5733]: Autolaunch error: X11 initialization failed. Jan 23 14:59:48 k2 gdm[5733]: ) Jan 23 14:59:48 k2 gnome-keyring-daemon[5963]: Couldn't unlock login keyring with provided password Jan 23 14:59:48 k2 gnome-keyring-daemon[5963]: Failed to unlock login on startup In this case the root cause appears to be the login didn't start everything, so now when I try and SSH to a remote box, whatever is meant to be doing its work in the background (letting me SSH to my laptop using a non-password-protected private key) isn't. -- ssh always asks to unlock private key with no password set https://bugs.launchpad.net/bugs/187127 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
