[Desktop-packages] [Bug 1449795] Re: keys not showing up after creation
*** This bug is a duplicate of bug 1299747 *** https://bugs.launchpad.net/bugs/1299747 ** This bug has been marked a duplicate of bug 1299747 Cannot create PGP key in Ubuntu 14.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1449795 Title: keys not showing up after creation Status in seahorse package in Ubuntu: Confirmed Bug description: Hit "+" button -> PGP key -> details: test1 test2 t...@ohmbase.org -> hit create button -> test/test (username/password) -> ok nothing happens. no error message, no 'seahorse/gpg is working' ...nothing ubuntu 15.04 seahorse: Installed: 3.15.90-0ubuntu1 Candidate: 3.15.90-0ubuntu1 gnupg: Installed: 1.4.18-7ubuntu1 Candidate: 1.4.18-7ubuntu1 *once* the key showed up when I was on another window. what should have happened: if it was possible to create the key ...the key should be displayed if not...an error message. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: seahorse 3.15.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 28 20:09:50 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-24 (4 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1449795/+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 1278381] Re: pgp key generation window not present
*** This bug is a duplicate of bug 1299747 *** https://bugs.launchpad.net/bugs/1299747 ** This bug has been marked a duplicate of bug 1299747 Cannot create PGP key in Ubuntu 14.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1278381 Title: pgp key generation window not present Status in seahorse package in Ubuntu: Confirmed Bug description: In the current version (today) of ubuntu 14.04: seahorse does not show a key generation window when creating a new pgp key, therefore giving no feedback at all about key generation. There also should be a process indicator showing how much of the can has been generated, as it takes several minutes leving unexperienced users to think it might have crased. seahorse version 3.10.2 gpg version 1.4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1278381/+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 1299747] Re: Cannot create PGP key in Ubuntu 14.04
** Bug watch added: GNOME Bug Tracker #734080 https://bugzilla.gnome.org/show_bug.cgi?id=734080 ** Also affects: seahorse via https://bugzilla.gnome.org/show_bug.cgi?id=734080 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1299747 Title: Cannot create PGP key in Ubuntu 14.04 Status in seahorse: Unknown Status in seahorse package in Ubuntu: Confirmed Bug description: When I try to create a PGP key, enter my informations, passphrase and click ok, nothing happens. I am using Ubuntu 14.04 beta. I don't know if this is related to security. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: seahorse 3.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sun Mar 30 17:49:49 2014 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2014-03-20 (10 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1299747/+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 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
I fully agree that rebuilding only a few packages is no suitable general solution. But so is the recommendation to upgrade to 14.04. There is a reason that corporate environments do not upgrade so often, and even 2 years is a very short time in this context. I have only recently upgraded a few smaller networks from Windows XP to Windows 7, and I am pretty sure these will stick with it until 2020. Thats why we highly appreciated the announcement that Ubuntu 12.04 would get 5 years of LTS support, so we decided to skip 14.04 entirely and target 16.04 as the next upgrade. We cannot change that plan just because of this bug. It took us several hundreds of hours of manpower to evaluate and test the upgrade from 10.04 to 12.04, and it took the complete lifespan of 10.04 until it was done. We worked out around 50 fixes and workarounds for all sorts of weird bugs and shortcomings which are still not fixed, and I cannot count how often I have read that this and that bug will not be fixed in the current version, despite it being an LTS release. Just two recent examples, #949468 and #886327. They're both not as critical as this one, but still annoying. We are a non-profit and as such cannot afford paid support like RHEL or SuSE Enterprise. We decided to try and contribute back instead, wherever we can. I still feel comfortable with that. But sometimes I get frustrated because it seems that some people behind Ubuntu think a shiny new tablet running Ubuntu is more important than people being able to get their work done. I would be happy to help testing if you decided to go the hard way and rebuild the rdeps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Fix Released Status in The G Library - GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: [Impact] * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). * LibreOffice is very important software. Modern versions are more functional. Without them Ubuntu is nothing, it is a toy. [Test Case] 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. 2a.2. Double click on 'test.odt' 2b. Launch terminal and send 'libreoffice smb://server_name/share_name/test.odt' command. 3. Get error message from LibreOffice: The file 'test.odt' is corrupt and therefore cannot be opened. LibreOffice can try to repair the file. The corruption could be the result of document manipulation or of structural document damage due to data transmission. We recommend that you do not trust the content of the repaired document. Execution of macros is disabled for this document. Should LibreOffice repair the file? Yes No 4a. If I click 'Yes', the file is opened, but the title of the document is Untitled 1 (repaired document), not original name. 4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text: The file 'test.odt' could not be repaired and therefore cannot be opened. OK I click 'OK' here, the next window LibreOffice 4.4.1.2 is opened with text: General Error. General input/output error. OK If I click OK here - no files are opened. While step 3 gvfsd-smb process eats CPU then terminates with error. This error is caused by bug in Glib (wrong type conversion in macros). [Regression Potential] * This functionality is essential. Please fix this bug. I (and you) can't tell Windows users, that they should not open office files from network shares in GNU/Linux. * The patch has two lines (https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4) and well-tested at upstream. * This bug may cause potential loss of data. [Other Info] * Corresponding links to LibO bugs are: https://bugs.freedesktop.org/show_bug.cgi?id=67527 https://bugs.documentfoundation.org/show_bug.cgi?id=72337 [Original description] On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see:
[Desktop-packages] [Bug 1214352] Re: GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
I can finally confirm that the patch from gnome bug 695925 above actually fixes the problem with Ubuntu 12.04.4 and LO 4.2.4 from the PPA. I have applied the patch to the glib source package and rebuilt and installed it, and then rebuilt libreoffice, gtk+3.0, dbus-glib and gvfs against the patched glib. This now finally seems to work. Unfortunately, this whole rebuilding is a PITA and takes a long time, especially for libreoffice. I'm not sure if everything is needed, but anyway I have a bad feeling with this. Now there are still lots of packages on my system which were built against the unpatched glib, so I really think this needs to be fixed in Ubuntu 12.04 with *ALL* packages which depend on glib being rebuilt against a patched version. How can we achieve this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Confirmed Status in The G Library - GLib: Fix Released Status in “glib2.0” package in Ubuntu: Confirmed Bug description: On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+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 1253620] Re: Can't open a LibreOffice native file via CIFS share
I finally found a solution by patching glib-2.0 and rebuilding libreoffice, gvfs, dbus-glib and gtk-3.0 against it. This works. Now this really needs to be fixed in Ubuntu by rebuilding *all* packages depending on glib, I think. I added a comment to bug 1214352 and wrote to canonical using the contact form from the URL you provided. I really hope this gets fixed soon... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1253620 Title: Can't open a LibreOffice native file via CIFS share Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Fix Released Bug description: Problem description: Can't open only native LibreOffice files from remote (CIFS) share with Ubuntu 12.04 and LibreOffice 4.1.3.2 (from ppa). System informations: Distributor ID: Ubuntu Description: Ubuntu 12.04.3 LTS Release: 12.04 Codename: precise LibreOffice package from ppa:libreoffice/ppa: 1:4.1.3~rc2-0ubuntu1~precise1~ppa1 Steps to reproduce: 1. Open LibreOffice 2. Select Open File from file menu 3. Select the remote share folder 4. Click to open the file Current behavior: LibreOffice trys to recover the remote file and fails. Expected behavior: LibreOffice opens the remote file correctly. Alternatives steps: 1. Open the remote path via Nautilus 2. Double click on remote LibreOffice native files Current behavior2: LibreOffice trys to recover the remote file and fails. Expected behavior2: LibreOffice opens the remote file correctly. Notes: * Remote and local MS files are opened correctly. * The problems with LibreOffice native files disappear if copying the remote files in a local path Here a workaround: sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/' /usr/share/applications/libreoffice-* No problem present on: Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy with LibreOffice: 1:4.1.3~rc2-0ubuntu1~saucy1~ppa3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1253620/+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 1253620] Re: Can't open a LibreOffice native file via CIFS share
@Ritesh I already took a look at bug 1214352, and I am pretty sure this has something to do with it. But I did not quite understand what would be the fix? I applied the attached patch to the glib-2.0 source package, rebuilt and installed all resulting libglib... packages, but that did not change anything regarding this bug. What else would need a rebuild? I will try testing with trusty, but that won't help me solve my problem. For various reasons, we will need to stick with 12.04LTS for at least another year or maybe two. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1253620 Title: Can't open a LibreOffice native file via CIFS share Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Fix Released Bug description: Problem description: Can't open only native LibreOffice files from remote (CIFS) share with Ubuntu 12.04 and LibreOffice 4.1.3.2 (from ppa). System informations: Distributor ID: Ubuntu Description: Ubuntu 12.04.3 LTS Release: 12.04 Codename: precise LibreOffice package from ppa:libreoffice/ppa: 1:4.1.3~rc2-0ubuntu1~precise1~ppa1 Steps to reproduce: 1. Open LibreOffice 2. Select Open File from file menu 3. Select the remote share folder 4. Click to open the file Current behavior: LibreOffice trys to recover the remote file and fails. Expected behavior: LibreOffice opens the remote file correctly. Alternatives steps: 1. Open the remote path via Nautilus 2. Double click on remote LibreOffice native files Current behavior2: LibreOffice trys to recover the remote file and fails. Expected behavior2: LibreOffice opens the remote file correctly. Notes: * Remote and local MS files are opened correctly. * The problems with LibreOffice native files disappear if copying the remote files in a local path Here a workaround: sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/' /usr/share/applications/libreoffice-* No problem present on: Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy with LibreOffice: 1:4.1.3~rc2-0ubuntu1~saucy1~ppa3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1253620/+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 1253620] Re: Can't open a LibreOffice native file via CIFS share
That version still sometimes crashes, sometimes gives Generic I/O Error. Not sure if this is still related to this bug, perhaps you can point me at some way to find this out. I might add that we had to symlink the usual mount point of GVFS mounts from ~/.gvfs to /tmp/.gvfs-username since home resides on an NFS mount with root squashing enabled. Not sure if this makes any difference here, but it is hard to test. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1253620 Title: Can't open a LibreOffice native file via CIFS share Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Fix Released Bug description: Problem description: Can't open only native LibreOffice files from remote (CIFS) share with Ubuntu 12.04 and LibreOffice 4.1.3.2 (from ppa). System informations: Distributor ID: Ubuntu Description: Ubuntu 12.04.3 LTS Release: 12.04 Codename: precise LibreOffice package from ppa:libreoffice/ppa: 1:4.1.3~rc2-0ubuntu1~precise1~ppa1 Steps to reproduce: 1. Open LibreOffice 2. Select Open File from file menu 3. Select the remote share folder 4. Click to open the file Current behavior: LibreOffice trys to recover the remote file and fails. Expected behavior: LibreOffice opens the remote file correctly. Alternatives steps: 1. Open the remote path via Nautilus 2. Double click on remote LibreOffice native files Current behavior2: LibreOffice trys to recover the remote file and fails. Expected behavior2: LibreOffice opens the remote file correctly. Notes: * Remote and local MS files are opened correctly. * The problems with LibreOffice native files disappear if copying the remote files in a local path Here a workaround: sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/' /usr/share/applications/libreoffice-* No problem present on: Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy with LibreOffice: 1:4.1.3~rc2-0ubuntu1~saucy1~ppa3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1253620/+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 1253620] Re: Can't open a LibreOffice native file via CIFS share
@ritesh Thanks for the answer. * GVFS is not used/needed for NFS, NFS mounts are all static (i.e. /home and /opt). I can exclude multiple logins, I know this is problematic. * The GIO fuse workaround has been removed from /usr/share/applications/libreoffice-* * gEdit works just fine with files from SMB over GVFS, as does evince. * I also verified the problem does not occur with static SMB mounts * I adopted the solution you suggested using XDG_RUNTIME_DIR by removing the symlink and backporting pam-xdg-support to precise, which seemed to work without problems. GVFS mounts now are in /run/user/username/gvfs/... Still, the problem persists. I will give the debugging help you provided a try and will report back tomorrow. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1253620 Title: Can't open a LibreOffice native file via CIFS share Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Fix Released Bug description: Problem description: Can't open only native LibreOffice files from remote (CIFS) share with Ubuntu 12.04 and LibreOffice 4.1.3.2 (from ppa). System informations: Distributor ID: Ubuntu Description: Ubuntu 12.04.3 LTS Release: 12.04 Codename: precise LibreOffice package from ppa:libreoffice/ppa: 1:4.1.3~rc2-0ubuntu1~precise1~ppa1 Steps to reproduce: 1. Open LibreOffice 2. Select Open File from file menu 3. Select the remote share folder 4. Click to open the file Current behavior: LibreOffice trys to recover the remote file and fails. Expected behavior: LibreOffice opens the remote file correctly. Alternatives steps: 1. Open the remote path via Nautilus 2. Double click on remote LibreOffice native files Current behavior2: LibreOffice trys to recover the remote file and fails. Expected behavior2: LibreOffice opens the remote file correctly. Notes: * Remote and local MS files are opened correctly. * The problems with LibreOffice native files disappear if copying the remote files in a local path Here a workaround: sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/' /usr/share/applications/libreoffice-* No problem present on: Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy with LibreOffice: 1:4.1.3~rc2-0ubuntu1~saucy1~ppa3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1253620/+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 1253620] Re: Can't open a LibreOffice native file via CIFS share
I have the same problem here, with Nautilus-mounted (i.e. over gvfs) SMB shares. I am using Ubuntu 12.04.4 and GNOME Classic. Using LO 4.1.5 from the PPA, I get the repair dialog. Using LO 4.2.2 from the PPA, LO crashes with SIGSEGV. The suggested workaround above regarding X-GIO-NoFuse does not help in either case. I have gvfs- backends-extra installed, as well as libreoffice-gnome etc. Would be glad to help, as this is causing real problems here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1253620 Title: Can't open a LibreOffice native file via CIFS share Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Problem description: Can't open only native LibreOffice files from remote (CIFS) share with Ubuntu 12.04 and LibreOffice 4.1.3.2 (from ppa). System informations: Distributor ID: Ubuntu Description: Ubuntu 12.04.3 LTS Release: 12.04 Codename: precise LibreOffice package from ppa:libreoffice/ppa: 1:4.1.3~rc2-0ubuntu1~precise1~ppa1 Steps to reproduce: 1. Open LibreOffice 2. Select Open File from file menu 3. Select the remote share folder 4. Click to open the file Current behavior: LibreOffice trys to recover the remote file and fails. Expected behavior: LibreOffice opens the remote file correctly. Alternatives steps: 1. Open the remote path via Nautilus 2. Double click on remote LibreOffice native files Current behavior2: LibreOffice trys to recover the remote file and fails. Expected behavior2: LibreOffice opens the remote file correctly. Notes: * Remote and local MS files are opened correctly. * The problems with LibreOffice native files disappear if copying the remote files in a local path Here a workaround: sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/' /usr/share/applications/libreoffice-* No problem present on: Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy with LibreOffice: 1:4.1.3~rc2-0ubuntu1~saucy1~ppa3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1253620/+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 844103] Re: GDM 3.0 and higher ignores /etc/environment
A workaround without rebuilding gdm is to create a new file /etc/profile.d/gdm-fix.sh and copy the PATH definition from /etc/environment there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/844103 Title: GDM 3.0 and higher ignores /etc/environment Status in GDM: The Gnome Display Manager: Fix Released Status in “gdm” package in Ubuntu: Fix Released Bug description: When I login in via gdm /sbin is not in my $PATH. 10:07:37 - flash:[~] echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/games:/home/bdmurray/bin/:/home/bdmurray/bin/ However, if I ssh to my system it is set: 10:13:38 - flash:[~] ssh localhost bdmurray@localhost's password: bdmurray@flash:[~] echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/home/bdmurray/bin/ ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gdm 3.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 CheckboxSubmission: fee5e196cb921cbd36888f428b38b488 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Wed Sep 7 10:06:24 2011 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: gdm UpgradeStatus: Upgraded to oneiric on 2011-09-06 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/844103/+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
