[Desktop-packages] [Bug 312722] Re: Connect to FTP with Login > Error "The file is not a directory"
Same problem on Ubuntu 12.10 ** This bug is no longer a duplicate of bug 290703 ssh connection should open the user directory by default -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/312722 Title: Connect to FTP with Login > Error "The file is not a directory" Status in Nautilus: New Status in “nautilus” package in Ubuntu: Confirmed Bug description: Ubuntu 8.04 & 8.10 Using Nautilus Connect to server, and choosing FTP (with login), entering (domain/IP) address, user, and hitting "Connect". Prompts for password, and then displays: "The folder contents could not be displayed" "Sorry, couldn't display all the contents of "/ on [host-address/IP]": The file is not a directory" To me it seems to be a problem with the directory on the server. the folder for the user is not the root / folder of the server it is: "/d:/www/edvl/domain.ch/html" when i connect with FireFTP or other clients. So Nautilus tries to connect to domain.ch/ where it has no permission! When connecting with the ftp> (Terminal) to "domain.ch/" there is also an error "ftp: domain.ch/: Unknown host Opening "domain.ch" leads to prompting the Username and afterwards the pw Perhaps Nautilus automatically adds the / at the end of the URL and this causes problems. Connecting directly to domain.ch/d:/www/edvl/domain.ch/html does not work neither. Consider: http://ubuntuforums.org/showthread.php?p=6468035 BTW: This is my first Bug Report, To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/312722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 903422] Re: Ubuntu does not work with Samsung Galaxy phones (Unable to open raw device 0)
There was recently a change to the adb tool. It now does authentication; the user is prompted to "allow" a new computer when the phone is connected to it. The old adb is not compatible. This change is probably why it fails, even though MTP on the Samsung Galaxy Nexus previously worked. I used the new adb (with the authentication) to manually push files. That worked fine. Trying the other forum posts (like changing the udev rules) did not work for me. It was very aggravating to get the cool new phone (Nexus 4) and then not be able to transfer files to it. (This comment reposted from duplicate bug 1092621.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/903422 Title: Ubuntu does not work with Samsung Galaxy phones (Unable to open raw device 0) Status in GVFS: Fix Released Status in “gmtp” package in Ubuntu: Invalid Status in “gvfs” package in Ubuntu: Fix Released Status in “udev” package in Ubuntu: Invalid Status in “gmtp” source package in Precise: Invalid Status in “gvfs” source package in Precise: Confirmed Status in “udev” source package in Precise: Invalid Status in “gmtp” source package in Quantal: Invalid Status in “gvfs” source package in Quantal: Confirmed Status in “udev” source package in Quantal: Invalid Bug description: If your device is not supported please open a new bug specifying: * device in question (make / model / release) * output of `mtp-detect` when the device is attached * output of `lsusb` when the device is attached This bug will be a catch all for recent Samsung Nexus & Nexus 7, or please comment what other recent Andorid 4.x devices are affected. Yes there is a lag in providing support for the most recent devices. As soon as the fixes are available, SRUs will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/903422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 505278] Re: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added?
Confirmed in 14.04.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/505278 Title: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added? Status in GNOME keyring services: New Status in Portable OpenSSH: Fix Released Status in “gnome-keyring” package in Ubuntu: Confirmed Status in “openssh” package in Ubuntu: Invalid Bug description: ssh-add -D seems to NOT remove my identities, even though it says it did. Also, why are all possible identities auto-added right away (on start?) rafal@lcwood(22:11:48)~$ ssh-add -l 8192 d1:50:43:64:52:7d:a0:61:ad:e2:bb:17:35:0d:7f:7d rafal1-rafal@lcwood (RSA) 8192 d8:f9:52:6d:d7:44:e2:fe:7d:72:78:f4:09:f7:4a:82 lcac_rafal_2_geovoucher_vm-rafal@aclc (RSA) 8192 1c:de:80:66:b2:c0:59:ff:03:61:58:43:ea:f5:b0:58 rafalsvn-rafal@lcwood (RSA) 8192 1b:7b:5b:a5:bf:40:7c:50:48:6f:5a:9b:f5:b3:43:1b rafaladmin-rafal@lcwood (RSA) rafal@lcwood(22:11:50)~$ ssh-add -D All identities removed. rafal@lcwood(22:11:51)~$ ssh-add -l 8192 d1:50:43:64:52:7d:a0:61:ad:e2:bb:17:35:0d:7f:7d rafal1-rafal@lcwood (RSA) 8192 d8:f9:52:6d:d7:44:e2:fe:7d:72:78:f4:09:f7:4a:82 lcac_rafal_2_geovoucher_vm-rafal@aclc (RSA) 8192 1c:de:80:66:b2:c0:59:ff:03:61:58:43:ea:f5:b0:58 rafalsvn-rafal@lcwood (RSA) 8192 1b:7b:5b:a5:bf:40:7c:50:48:6f:5a:9b:f5:b3:43:1b rafaladmin-rafal@lcwood (RSA) rafal@lcwood(22:11:53)~$ apport-bug ssh-ad ProblemType: Bug Architecture: amd64 Date: Sat Jan 9 22:12:25 2010 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: ssh (not installed) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: openssh Uname: Linux 2.6.31-16-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/505278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 846808] [NEW] gnome-network-admin menu entry does not use gksu
Public bug reported: I want a desktop GUI method to change my hostname. So I apt-get install gnome-network-admin. But now when I go to System > Administration > Network, the program network-admin says "Not authorized to make changes". I must manually launch a shell and run "gksu network-admin". (This is using the admin account created during install, which is a member of the admin and adm groups.) It should just prompt me for my password. I see no way to edit the system hostname without going to a shell. ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/846808 Title: gnome-network-admin menu entry does not use gksu Status in “gnome-system-tools” package in Ubuntu: New Bug description: I want a desktop GUI method to change my hostname. So I apt-get install gnome-network-admin. But now when I go to System > Administration > Network, the program network-admin says "Not authorized to make changes". I must manually launch a shell and run "gksu network-admin". (This is using the admin account created during install, which is a member of the admin and adm groups.) It should just prompt me for my password. I see no way to edit the system hostname without going to a shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/846808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 846808] Re: PolicyKit button doesn't allow authenticating
First: I did not see "Authentication agent" listed when I ran gnome- session-properties on my 11.04 server. I did not see it on my Ubuntu 10.04 workstation, either. Not sure what's up with that. However, you did identify the root of the problem. I did not mention that I am using VNC. When I log in locally (with a physical keyboard and monitor), then I am able to "Click to make changes" and change my hostname. When I log in using a physical keyboard, it looks like this when I run "who" (my username is "ubuntu"): ubuntu tty8 2011-09-11 18:33 (:0) But when I log in with VNC, it looks like this: ubuntu2011-09-11 18:32 (127.0.0.1:1) I am guessing the difference between (:0) and (127.0.0.1:1) is why my VNC session is not authorized to make changes. So I am marking this bug as "invalid". Thank you for your help. I'm off to read the PolicyKit documentation now... but if you could give me a hint as to where I need to add "127.0.0.1:1" it would be much appreciated :) ** Changed in: gnome-system-tools (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/846808 Title: PolicyKit button doesn't allow authenticating Status in “gnome-system-tools” package in Ubuntu: Invalid Bug description: I want a desktop GUI method to change my hostname. So I apt-get install gnome-network-admin. But now when I go to System > Administration > Network, the program network-admin says "Not authorized to make changes". I must manually launch a shell and run "gksu network-admin". (This is using the admin account created during install, which is a member of the admin and adm groups.) It should just prompt me for my password. I see no way to edit the system hostname without going to a shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/846808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 221363] Re: Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
Milan said in #62: Have a look at files in /usr/share/polkit-1/actions/ and try to guess what are the files you need to edit. Then it's probably useful to file bugs so that it's fixed upstream, if applicable. What are the criteria to know what files need to be edited? I saw org.freedesktop.SystemToolsBackends.policy and gdm.policy mentioned above. Are those the only two? Would it be more correct to replace every "allow_active" with "allow_any" in 100% of those files? There are 25 files that say "allow_active" in them. I want to help fix this bug, which means filing a bug report for every package that needs a revised policy file, like gdm and system-tools- backends: root@cst8:/usr/share/polkit-1/actions# dpkg -S gdm.policy gdm: /usr/share/polkit-1/actions/gdm.policy root@cst8:/usr/share/polkit-1/actions# dpkg -S org.freedesktop.SystemToolsBackends.policy system-tools-backends: /usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy root@cst8:/usr/share/polkit-1/actions# I just don't understand what criteria to use to know which other packages should have a bug filed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-tools-backends in Ubuntu. https://bugs.launchpad.net/bugs/221363 Title: Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP Status in FreeNX open source NX Server: Fix Released Status in GDM: The Gnome Display Manager: New Status in PolicyKit: Invalid Status in system-tools-backends: Fix Released Status in “policykit” package in Ubuntu: Invalid Status in “policykit-1” package in Ubuntu: Invalid Status in “system-tools-backends” package in Ubuntu: Triaged Bug description: I installed 8.04 LTS server on a system. Then installed ubuntu- desktop using apt. Installed Nomachine's NX server and connected to it. The unlock buttons on Users and Groups or Network are greyed out and un-accessible. Tried running from a term 'sudo users-admin' with the same results. Works fine with VNC and NX "Shadow" session however this is not really acceptable as it means a session has to be running on console first. I have tried to enable every option in Authorizations to allow the remote session to have privileges to no avail. output of dpkg relevant packages: ii gnome-system-t 2.22.0-0ubuntu Cross-platform configuration utilities for G ii liboobs-1-42.22.0-0ubuntu GObject based interface to system-tools-back ii policykit 0.7-2ubuntu7 framework for managing administrative polici ii system-tools-b 2.6.0-0ubuntu7 System Tools to manage computer configuratio == Workarounds == 1) *Jaunty or older* From https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/238799/comments/16 (the packages from comment 24 are broken links now): I was able to get access via VNC tunneled through SSH by changing the following settings in policykit. You can do it locally via Authorizations, or you can do it remotely using "sudo ck-launch- session polkit-gnome-authorization" in a terminal window in your tunneled VNC session. This worked on Ubuntu 9.04 Server RC running xubuntu-desktop, so as always YMMV. For system configuration, change all implicit authorizations under org -> freedesktop -> systemtoolsbackends -> Manage System Configuration (org.freedesktop.systemtoolsbackends.set) to "Admin Authentication." For user management, change all implicit authorizations under org -> freedesktop -> systemtoolsbackends -> self -> Change User Configuration (org.freedesktop.systemtoolsbackends.self.set) to "Authentication." Reset gdm by rebooting or running "sudo /etc/init.d/gdm restart" from a terminal window, and you should be able to unlock the user settings control panel and other similarly useful things through your tunneled VNC session. 2) *Karmic or newer* Apply this patch: http://launchpadlibrarian.net/39471473/polkit-systemtools-remote-allow.patch # sudo cp -a /usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy /usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy.ori # sudo patch /usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy polkit-systemtools-remote-allow.patch Then kill polkitd, it will be restarted automatically: # sudo pkill polkitd To manage notifications about this bug go to: https://bugs.launchpad.net/freenx-server/+bug/221363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
