[Bug 57340] beagle-search uses bashism but invokes sh
Public bug reported: Binary package hint: beagle /usr/bin/beagle-search starts with "#!/usr/bin/bash" but then on the last line uses "exec -a foo". The "-a" option is bash specific. Or more specifically in my experience it is not supported by dash (which is supposed to be POSIX complient or so). So either the shell should be changed or the -a option should be changed IMHO. Cheers Floris ** Affects: beagle (Ubuntu) Importance: Untriaged Assignee: Ubuntu Desktop Bugs Status: Rejected -- beagle-search uses bashism but invokes sh https://launchpad.net/bugs/57340 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57340] beagle-search uses bashism but invokes sh
Public bug reported: Binary package hint: beagle /usr/bin/beagle-search starts with "#!/usr/bin/bash" but then on the last line uses "exec -a foo". The "-a" option is bash specific. Or more specifically in my experience it is not supported by dash (which is supposed to be POSIX complient or so). So either the shell should be changed or the -a option should be changed IMHO. Cheers Floris ** Affects: beagle (Ubuntu) Importance: Untriaged Assignee: Ubuntu Desktop Bugs Status: Rejected -- beagle-search uses bashism but invokes sh https://launchpad.net/bugs/57340 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57340] beagle-search uses bashism but invokes sh
Public bug reported: Binary package hint: beagle /usr/bin/beagle-search starts with "#!/usr/bin/bash" but then on the last line uses "exec -a foo". The "-a" option is bash specific. Or more specifically in my experience it is not supported by dash (which is supposed to be POSIX complient or so). So either the shell should be changed or the -a option should be changed IMHO. Cheers Floris ** Affects: beagle (Ubuntu) Importance: Untriaged Assignee: Ubuntu Desktop Bugs Status: Rejected -- beagle-search uses bashism but invokes sh https://launchpad.net/bugs/57340 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57340] beagle-search uses bashism but invokes sh
Public bug reported: Binary package hint: beagle /usr/bin/beagle-search starts with "#!/usr/bin/bash" but then on the last line uses "exec -a foo". The "-a" option is bash specific. Or more specifically in my experience it is not supported by dash (which is supposed to be POSIX complient or so). So either the shell should be changed or the -a option should be changed IMHO. Cheers Floris ** Affects: beagle (Ubuntu) Importance: Untriaged Assignee: Ubuntu Desktop Bugs Status: Rejected -- beagle-search uses bashism but invokes sh https://launchpad.net/bugs/57340 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57340] beagle-search uses bashism but invokes sh
Public bug reported: Binary package hint: beagle /usr/bin/beagle-search starts with "#!/usr/bin/bash" but then on the last line uses "exec -a foo". The "-a" option is bash specific. Or more specifically in my experience it is not supported by dash (which is supposed to be POSIX complient or so). So either the shell should be changed or the -a option should be changed IMHO. Cheers Floris ** Affects: beagle (Ubuntu) Importance: Untriaged Assignee: Ubuntu Desktop Bugs Status: Rejected -- beagle-search uses bashism but invokes sh https://launchpad.net/bugs/57340 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57340] beagle-search uses bashism but invokes sh
Public bug reported: Binary package hint: beagle /usr/bin/beagle-search starts with "#!/usr/bin/bash" but then on the last line uses "exec -a foo". The "-a" option is bash specific. Or more specifically in my experience it is not supported by dash (which is supposed to be POSIX complient or so). So either the shell should be changed or the -a option should be changed IMHO. Cheers Floris ** Affects: beagle (Ubuntu) Importance: Untriaged Assignee: Ubuntu Desktop Bugs Status: Rejected -- beagle-search uses bashism but invokes sh https://launchpad.net/bugs/57340 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
** Attachment added: "Screenshot-seahorse.png" http://launchpadlibrarian.net/14511503/Screenshot-seahorse.png -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
I think this oneline patch fixes the problem (haven't tested it yet) ** Attachment added: "seahorse-homedirbug.patch" http://launchpadlibrarian.net/14511775/seahorse-homedirbug.patch -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] [NEW] Seahorse assumes current dir is $HOME when setting up ssh
Public bug reported: Binary package hint: seahorse Seahorse has a very useful feature to automatically copy your public ssh-key to a remote machine so you can login using that key later on. There is one assumption seahorse makes that is not always true though: when ssh'ing to the remote machine to place the public key there, it assumes the current directory is your home directory, and tries to do stuff with .ssh/authorized_keys there. On one of the machines I frequently use, I'm not in my homedir after ssh'ing there. Seahorse tries to access .ssh/authorized_keys and fails, because the current directory is /data. I think Seahorse should not rely on the current directory being $HOME, but explicitely make it so as the first command to be run remotely. I have attached a screenshot of the errormessage I received. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
I just had something like this: Gaim was on status available (no message), and I switched to a saved/custom state 'eating'. That status I had created earlier to display 'out to lunch' for msn, and 'away' for all other networks with a custom awaymessage 'Etenstijd' (time for a meal in dutch). ** Attachment added: "Crash Report" http://librarian.launchpad.net/4942148/_usr_bin_gaim.1000.crash -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
I can confirm this too. Also using Feisty Fawn, and a Sony Clie T675C. I can also confirm that the problem goes away when there are no todo items on my clie without a due date, it seems to be a problem related to undated todo items. The last messages gpilotd shows before the error: etodoconduit-Message: add_record: adding [0 1177279200 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [0 1179698400 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [1 -1 1 0 'Censored' '' 2] to desktop *** stack smashing detected ***: /usr/bin/gpilotd terminated Aborted (core dumped) The Cencored texts where different, but are not relevant I hope. They all contain only normal alphabetical characters, I had an @ sign in the last one but replaced that by 'at' for the last one, just to be sure that wasn't the problem. I do have the coredump if that is of any use, but there is no gpilot ubuntu package with debugging symbols as far as I could see. -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
> Interestingly, it seems to happen when the due date is empty. > is there anyone to confirm this? Yes, that's what I said in my reply, and also what RobotII said in the first reply -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
For me, it's not, never had it again at least not since I run 2.0.0beta6 -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87805] Re: "users and groups" empty since upgrade
I have this too, not only with users-admin, but with services-admin too. In shares-admin it is even more obvious there goes something wrong, because it complains I don't have NFS and/or SAMBA installed, which I both have functioning well. When started from the commandline with 'gksu users-admin' I receive the message below, followed by a perfectly looking users-admin screen, only it's empty. [EMAIL PROTECTED]:~$ gksu users-admin (users-admin:1153): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) -- "users and groups" empty since upgrade https://launchpad.net/bugs/87805 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Re: Mahjongg: pause button disappears after resume
Hmm,, I thought by submitting the bug using the Help>Report a Bug menu item some more information would be here automatically. Guess not. I'm running feisty, and gnome-games is version 1:2.18.0-0ubuntu1 right now. -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Mahjongg: pause button disappears after resume
Public bug reported: Binary package hint: gnome-games When you click on the pause button during a game of Mahjongg, it is being replaced with a resume button in some fancy way. After you click the resume button, the switch back does remove the resume button, but doesn't show the pause button again, instead there is a gap on the toolbar. Workaround: use pause from the game menu ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: Unconfirmed -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
** Attachment added: "Screenshot-seahorse.png" http://launchpadlibrarian.net/14511503/Screenshot-seahorse.png -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
I think this oneline patch fixes the problem (haven't tested it yet) ** Attachment added: "seahorse-homedirbug.patch" http://launchpadlibrarian.net/14511775/seahorse-homedirbug.patch -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] [NEW] Seahorse assumes current dir is $HOME when setting up ssh
Public bug reported: Binary package hint: seahorse Seahorse has a very useful feature to automatically copy your public ssh-key to a remote machine so you can login using that key later on. There is one assumption seahorse makes that is not always true though: when ssh'ing to the remote machine to place the public key there, it assumes the current directory is your home directory, and tries to do stuff with .ssh/authorized_keys there. On one of the machines I frequently use, I'm not in my homedir after ssh'ing there. Seahorse tries to access .ssh/authorized_keys and fails, because the current directory is /data. I think Seahorse should not rely on the current directory being $HOME, but explicitely make it so as the first command to be run remotely. I have attached a screenshot of the errormessage I received. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Re: Mahjongg: pause button disappears after resume
Hmm,, I thought by submitting the bug using the Help>Report a Bug menu item some more information would be here automatically. Guess not. I'm running feisty, and gnome-games is version 1:2.18.0-0ubuntu1 right now. -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Mahjongg: pause button disappears after resume
Public bug reported: Binary package hint: gnome-games When you click on the pause button during a game of Mahjongg, it is being replaced with a resume button in some fancy way. After you click the resume button, the switch back does remove the resume button, but doesn't show the pause button again, instead there is a gap on the toolbar. Workaround: use pause from the game menu ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: Unconfirmed -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
I can confirm this too. Also using Feisty Fawn, and a Sony Clie T675C. I can also confirm that the problem goes away when there are no todo items on my clie without a due date, it seems to be a problem related to undated todo items. The last messages gpilotd shows before the error: etodoconduit-Message: add_record: adding [0 1177279200 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [0 1179698400 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [1 -1 1 0 'Censored' '' 2] to desktop *** stack smashing detected ***: /usr/bin/gpilotd terminated Aborted (core dumped) The Cencored texts where different, but are not relevant I hope. They all contain only normal alphabetical characters, I had an @ sign in the last one but replaced that by 'at' for the last one, just to be sure that wasn't the problem. I do have the coredump if that is of any use, but there is no gpilot ubuntu package with debugging symbols as far as I could see. -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
> Interestingly, it seems to happen when the due date is empty. > is there anyone to confirm this? Yes, that's what I said in my reply, and also what RobotII said in the first reply -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
I just had something like this: Gaim was on status available (no message), and I switched to a saved/custom state 'eating'. That status I had created earlier to display 'out to lunch' for msn, and 'away' for all other networks with a custom awaymessage 'Etenstijd' (time for a meal in dutch). ** Attachment added: "Crash Report" http://librarian.launchpad.net/4942148/_usr_bin_gaim.1000.crash -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
For me, it's not, never had it again at least not since I run 2.0.0beta6 -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87805] Re: "users and groups" empty since upgrade
I have this too, not only with users-admin, but with services-admin too. In shares-admin it is even more obvious there goes something wrong, because it complains I don't have NFS and/or SAMBA installed, which I both have functioning well. When started from the commandline with 'gksu users-admin' I receive the message below, followed by a perfectly looking users-admin screen, only it's empty. [EMAIL PROTECTED]:~$ gksu users-admin (users-admin:1153): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) -- "users and groups" empty since upgrade https://launchpad.net/bugs/87805 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
** Attachment added: "Screenshot-seahorse.png" http://launchpadlibrarian.net/14511503/Screenshot-seahorse.png -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
I think this oneline patch fixes the problem (haven't tested it yet) ** Attachment added: "seahorse-homedirbug.patch" http://launchpadlibrarian.net/14511775/seahorse-homedirbug.patch -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] [NEW] Seahorse assumes current dir is $HOME when setting up ssh
Public bug reported: Binary package hint: seahorse Seahorse has a very useful feature to automatically copy your public ssh-key to a remote machine so you can login using that key later on. There is one assumption seahorse makes that is not always true though: when ssh'ing to the remote machine to place the public key there, it assumes the current directory is your home directory, and tries to do stuff with .ssh/authorized_keys there. On one of the machines I frequently use, I'm not in my homedir after ssh'ing there. Seahorse tries to access .ssh/authorized_keys and fails, because the current directory is /data. I think Seahorse should not rely on the current directory being $HOME, but explicitely make it so as the first command to be run remotely. I have attached a screenshot of the errormessage I received. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
I just had something like this: Gaim was on status available (no message), and I switched to a saved/custom state 'eating'. That status I had created earlier to display 'out to lunch' for msn, and 'away' for all other networks with a custom awaymessage 'Etenstijd' (time for a meal in dutch). ** Attachment added: "Crash Report" http://librarian.launchpad.net/4942148/_usr_bin_gaim.1000.crash -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
I can confirm this too. Also using Feisty Fawn, and a Sony Clie T675C. I can also confirm that the problem goes away when there are no todo items on my clie without a due date, it seems to be a problem related to undated todo items. The last messages gpilotd shows before the error: etodoconduit-Message: add_record: adding [0 1177279200 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [0 1179698400 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [1 -1 1 0 'Censored' '' 2] to desktop *** stack smashing detected ***: /usr/bin/gpilotd terminated Aborted (core dumped) The Cencored texts where different, but are not relevant I hope. They all contain only normal alphabetical characters, I had an @ sign in the last one but replaced that by 'at' for the last one, just to be sure that wasn't the problem. I do have the coredump if that is of any use, but there is no gpilot ubuntu package with debugging symbols as far as I could see. -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
> Interestingly, it seems to happen when the due date is empty. > is there anyone to confirm this? Yes, that's what I said in my reply, and also what RobotII said in the first reply -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
For me, it's not, never had it again at least not since I run 2.0.0beta6 -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87805] Re: "users and groups" empty since upgrade
I have this too, not only with users-admin, but with services-admin too. In shares-admin it is even more obvious there goes something wrong, because it complains I don't have NFS and/or SAMBA installed, which I both have functioning well. When started from the commandline with 'gksu users-admin' I receive the message below, followed by a perfectly looking users-admin screen, only it's empty. [EMAIL PROTECTED]:~$ gksu users-admin (users-admin:1153): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) -- "users and groups" empty since upgrade https://launchpad.net/bugs/87805 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Re: Mahjongg: pause button disappears after resume
Hmm,, I thought by submitting the bug using the Help>Report a Bug menu item some more information would be here automatically. Guess not. I'm running feisty, and gnome-games is version 1:2.18.0-0ubuntu1 right now. -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Mahjongg: pause button disappears after resume
Public bug reported: Binary package hint: gnome-games When you click on the pause button during a game of Mahjongg, it is being replaced with a resume button in some fancy way. After you click the resume button, the switch back does remove the resume button, but doesn't show the pause button again, instead there is a gap on the toolbar. Workaround: use pause from the game menu ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: Unconfirmed -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
** Attachment added: "Screenshot-seahorse.png" http://launchpadlibrarian.net/14511503/Screenshot-seahorse.png -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
I think this oneline patch fixes the problem (haven't tested it yet) ** Attachment added: "seahorse-homedirbug.patch" http://launchpadlibrarian.net/14511775/seahorse-homedirbug.patch -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] [NEW] Seahorse assumes current dir is $HOME when setting up ssh
Public bug reported: Binary package hint: seahorse Seahorse has a very useful feature to automatically copy your public ssh-key to a remote machine so you can login using that key later on. There is one assumption seahorse makes that is not always true though: when ssh'ing to the remote machine to place the public key there, it assumes the current directory is your home directory, and tries to do stuff with .ssh/authorized_keys there. On one of the machines I frequently use, I'm not in my homedir after ssh'ing there. Seahorse tries to access .ssh/authorized_keys and fails, because the current directory is /data. I think Seahorse should not rely on the current directory being $HOME, but explicitely make it so as the first command to be run remotely. I have attached a screenshot of the errormessage I received. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
For me, it's not, never had it again at least not since I run 2.0.0beta6 -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87805] Re: "users and groups" empty since upgrade
I have this too, not only with users-admin, but with services-admin too. In shares-admin it is even more obvious there goes something wrong, because it complains I don't have NFS and/or SAMBA installed, which I both have functioning well. When started from the commandline with 'gksu users-admin' I receive the message below, followed by a perfectly looking users-admin screen, only it's empty. [EMAIL PROTECTED]:~$ gksu users-admin (users-admin:1153): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) -- "users and groups" empty since upgrade https://launchpad.net/bugs/87805 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Re: Mahjongg: pause button disappears after resume
Hmm,, I thought by submitting the bug using the Help>Report a Bug menu item some more information would be here automatically. Guess not. I'm running feisty, and gnome-games is version 1:2.18.0-0ubuntu1 right now. -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Mahjongg: pause button disappears after resume
Public bug reported: Binary package hint: gnome-games When you click on the pause button during a game of Mahjongg, it is being replaced with a resume button in some fancy way. After you click the resume button, the switch back does remove the resume button, but doesn't show the pause button again, instead there is a gap on the toolbar. Workaround: use pause from the game menu ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: Unconfirmed -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
I can confirm this too. Also using Feisty Fawn, and a Sony Clie T675C. I can also confirm that the problem goes away when there are no todo items on my clie without a due date, it seems to be a problem related to undated todo items. The last messages gpilotd shows before the error: etodoconduit-Message: add_record: adding [0 1177279200 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [0 1179698400 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [1 -1 1 0 'Censored' '' 2] to desktop *** stack smashing detected ***: /usr/bin/gpilotd terminated Aborted (core dumped) The Cencored texts where different, but are not relevant I hope. They all contain only normal alphabetical characters, I had an @ sign in the last one but replaced that by 'at' for the last one, just to be sure that wasn't the problem. I do have the coredump if that is of any use, but there is no gpilot ubuntu package with debugging symbols as far as I could see. -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
> Interestingly, it seems to happen when the due date is empty. > is there anyone to confirm this? Yes, that's what I said in my reply, and also what RobotII said in the first reply -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
I just had something like this: Gaim was on status available (no message), and I switched to a saved/custom state 'eating'. That status I had created earlier to display 'out to lunch' for msn, and 'away' for all other networks with a custom awaymessage 'Etenstijd' (time for a meal in dutch). ** Attachment added: "Crash Report" http://librarian.launchpad.net/4942148/_usr_bin_gaim.1000.crash -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
I just had something like this: Gaim was on status available (no message), and I switched to a saved/custom state 'eating'. That status I had created earlier to display 'out to lunch' for msn, and 'away' for all other networks with a custom awaymessage 'Etenstijd' (time for a meal in dutch). ** Attachment added: "Crash Report" http://librarian.launchpad.net/4942148/_usr_bin_gaim.1000.crash -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
** Attachment added: "Screenshot-seahorse.png" http://launchpadlibrarian.net/14511503/Screenshot-seahorse.png -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
I think this oneline patch fixes the problem (haven't tested it yet) ** Attachment added: "seahorse-homedirbug.patch" http://launchpadlibrarian.net/14511775/seahorse-homedirbug.patch -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] [NEW] Seahorse assumes current dir is $HOME when setting up ssh
Public bug reported: Binary package hint: seahorse Seahorse has a very useful feature to automatically copy your public ssh-key to a remote machine so you can login using that key later on. There is one assumption seahorse makes that is not always true though: when ssh'ing to the remote machine to place the public key there, it assumes the current directory is your home directory, and tries to do stuff with .ssh/authorized_keys there. On one of the machines I frequently use, I'm not in my homedir after ssh'ing there. Seahorse tries to access .ssh/authorized_keys and fails, because the current directory is /data. I think Seahorse should not rely on the current directory being $HOME, but explicitely make it so as the first command to be run remotely. I have attached a screenshot of the errormessage I received. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
For me, it's not, never had it again at least not since I run 2.0.0beta6 -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87805] Re: "users and groups" empty since upgrade
I have this too, not only with users-admin, but with services-admin too. In shares-admin it is even more obvious there goes something wrong, because it complains I don't have NFS and/or SAMBA installed, which I both have functioning well. When started from the commandline with 'gksu users-admin' I receive the message below, followed by a perfectly looking users-admin screen, only it's empty. [EMAIL PROTECTED]:~$ gksu users-admin (users-admin:1153): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) -- "users and groups" empty since upgrade https://launchpad.net/bugs/87805 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Re: Mahjongg: pause button disappears after resume
Hmm,, I thought by submitting the bug using the Help>Report a Bug menu item some more information would be here automatically. Guess not. I'm running feisty, and gnome-games is version 1:2.18.0-0ubuntu1 right now. -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Mahjongg: pause button disappears after resume
Public bug reported: Binary package hint: gnome-games When you click on the pause button during a game of Mahjongg, it is being replaced with a resume button in some fancy way. After you click the resume button, the switch back does remove the resume button, but doesn't show the pause button again, instead there is a gap on the toolbar. Workaround: use pause from the game menu ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: Unconfirmed -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
I can confirm this too. Also using Feisty Fawn, and a Sony Clie T675C. I can also confirm that the problem goes away when there are no todo items on my clie without a due date, it seems to be a problem related to undated todo items. The last messages gpilotd shows before the error: etodoconduit-Message: add_record: adding [0 1177279200 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [0 1179698400 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [1 -1 1 0 'Censored' '' 2] to desktop *** stack smashing detected ***: /usr/bin/gpilotd terminated Aborted (core dumped) The Cencored texts where different, but are not relevant I hope. They all contain only normal alphabetical characters, I had an @ sign in the last one but replaced that by 'at' for the last one, just to be sure that wasn't the problem. I do have the coredump if that is of any use, but there is no gpilot ubuntu package with debugging symbols as far as I could see. -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
> Interestingly, it seems to happen when the due date is empty. > is there anyone to confirm this? Yes, that's what I said in my reply, and also what RobotII said in the first reply -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
I just had something like this: Gaim was on status available (no message), and I switched to a saved/custom state 'eating'. That status I had created earlier to display 'out to lunch' for msn, and 'away' for all other networks with a custom awaymessage 'Etenstijd' (time for a meal in dutch). ** Attachment added: "Crash Report" http://librarian.launchpad.net/4942148/_usr_bin_gaim.1000.crash -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60020] Re: Crash while trying to set away message
For me, it's not, never had it again at least not since I run 2.0.0beta6 -- Crash while trying to set away message https://launchpad.net/bugs/60020 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87805] Re: "users and groups" empty since upgrade
I have this too, not only with users-admin, but with services-admin too. In shares-admin it is even more obvious there goes something wrong, because it complains I don't have NFS and/or SAMBA installed, which I both have functioning well. When started from the commandline with 'gksu users-admin' I receive the message below, followed by a perfectly looking users-admin screen, only it's empty. [EMAIL PROTECTED]:~$ gksu users-admin (users-admin:1153): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) (users-admin:1153): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) -- "users and groups" empty since upgrade https://launchpad.net/bugs/87805 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Re: Mahjongg: pause button disappears after resume
Hmm,, I thought by submitting the bug using the Help>Report a Bug menu item some more information would be here automatically. Guess not. I'm running feisty, and gnome-games is version 1:2.18.0-0ubuntu1 right now. -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 94851] Mahjongg: pause button disappears after resume
Public bug reported: Binary package hint: gnome-games When you click on the pause button during a game of Mahjongg, it is being replaced with a resume button in some fancy way. After you click the resume button, the switch back does remove the resume button, but doesn't show the pause button again, instead there is a gap on the toolbar. Workaround: use pause from the game menu ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: Unconfirmed -- Mahjongg: pause button disappears after resume https://launchpad.net/bugs/94851 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
I can confirm this too. Also using Feisty Fawn, and a Sony Clie T675C. I can also confirm that the problem goes away when there are no todo items on my clie without a due date, it seems to be a problem related to undated todo items. The last messages gpilotd shows before the error: etodoconduit-Message: add_record: adding [0 1177279200 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [0 1179698400 1 0 'Censored' '[14-99:99 s000 ]' 3] to desktop etodoconduit-Message: add_record: adding [1 -1 1 0 'Censored' '' 2] to desktop *** stack smashing detected ***: /usr/bin/gpilotd terminated Aborted (core dumped) The Cencored texts where different, but are not relevant I hope. They all contain only normal alphabetical characters, I had an @ sign in the last one but replaced that by 'at' for the last one, just to be sure that wasn't the problem. I do have the coredump if that is of any use, but there is no gpilot ubuntu package with debugging symbols as far as I could see. -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
> Interestingly, it seems to happen when the due date is empty. > is there anyone to confirm this? Yes, that's what I said in my reply, and also what RobotII said in the first reply -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
** Attachment added: "Screenshot-seahorse.png" http://launchpadlibrarian.net/14511503/Screenshot-seahorse.png -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] Re: Seahorse assumes current dir is $HOME when setting up ssh
I think this oneline patch fixes the problem (haven't tested it yet) ** Attachment added: "seahorse-homedirbug.patch" http://launchpadlibrarian.net/14511775/seahorse-homedirbug.patch -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 230222] [NEW] Seahorse assumes current dir is $HOME when setting up ssh
Public bug reported: Binary package hint: seahorse Seahorse has a very useful feature to automatically copy your public ssh-key to a remote machine so you can login using that key later on. There is one assumption seahorse makes that is not always true though: when ssh'ing to the remote machine to place the public key there, it assumes the current directory is your home directory, and tries to do stuff with .ssh/authorized_keys there. On one of the machines I frequently use, I'm not in my homedir after ssh'ing there. Seahorse tries to access .ssh/authorized_keys and fails, because the current directory is /data. I think Seahorse should not rely on the current directory being $HOME, but explicitely make it so as the first command to be run remotely. I have attached a screenshot of the errormessage I received. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- Seahorse assumes current dir is $HOME when setting up ssh https://bugs.launchpad.net/bugs/230222 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
