[Bug 371236] Re: Underlying /tmp directory has wrong permissions when hidden by mount point
That last line should have read: Changing the permissions on the client /tmp to 1777 fixed the issue temporarily, as at the next boot the permissions on the client image were back to 755. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371236 Title: Underlying /tmp directory has wrong permissions when hidden by mount point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/371236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371236] Re: Underlying /tmp directory has wrong permissions when hidden by mount point
I also had this issue. I recently installed Ubuntu 14.04.4 using LVM. /tmp was on its own logical volume. I am using this computer as as LTSP server. When the client image is built it used the permissions of /tmp prior to being mounted drwxr-xr-x (755). /tmp should have a permission of drwxrwxrwt (1777) even if it gets mounted over. This wrong permission allowed the LTSP clients to boot but after a successful login, the client would never see the desktop but were sent back to the login screen. Changing the permissions of the client /tmp to 1777 fixed this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371236 Title: Underlying /tmp directory has wrong permissions when hidden by mount point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/371236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491940] Re: Patch for LTSP clients to properly reboot/shutdown
I forgot to add in my last comment during the countdown open the menu in the bottom left corner called Prefrences and select Shutdown. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/491940 Title: Patch for LTSP clients to properly reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/491940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491940] Re: Patch for LTSP clients to properly reboot/shutdown
I have a LTSP client that functions as a photo frame running gphotoframe. I have the following in lts.conf for that client #Laptop ethernet [00:0*:**:**:**:**] LIKE=Atoms # Used to allow auto login of clients LDM_AUTOLOGIN=false LDM_LOGIN_TIMEOUT=7 # Needed for LDM_LOGIN_TIMEOUT to work properly LDM_GUESTLOGIN=true LDM_USERNAME=media LDM_PASSWORD=*** #SOUND=N #Auto Shut down SHUTDOWN_TIME=20:00:00 I believe the lines that will solve the problem of the endless loop are: LDM_AUTOLOGIN=false LDM_LOGIN_TIMEOUT=7 LDM_GUESTLOGIN=true The LDM_LOGIN_TIMEOUT parameter makes it wait that many seconds before automatically login in. Adjust it as you like. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/491940 Title: Patch for LTSP clients to properly reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/491940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 602744] Re: LTSP client can not run local apps after server is shutdown before client logs out when /tmp is not cleared on next boot.
Just wondering if this has been fixed or if no one else has experienced it that it has not been changed in priority. Would be nice to at least see its status changed to confirmed even if it does no get assigned to someone to fix right away. Admittedly this would be low priority as it should rarely occur, but it could be a frustrating experience for a LTSP administrator that does not know about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/602744 Title: LTSP client can not run local apps after server is shutdown before client logs out when /tmp is not cleared on next boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/602744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 602744] Re: LTSP client can not run local apps after server is shutdown before client logs out when /tmp is not cleared on next boot.
Hi Stéphane Graber! Yes I rebooted all the LTSP cilents. The problem is related to the temporary files that are stored on the server for local apps. If the server was shut down improperly, say as in my case with the clients connected(because of the other bug) the temporary files are not removed. This causes local apps that were running to not start if they are set to only allow one instance as they find their old lock file in the /tmp directory. Other problems may occur with programs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/602744 Title: LTSP client can not run local apps after server is shutdown before client logs out when /tmp is not cleared on next boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/602744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523587] Re: /etc/init/mounted-tmp.conf uses find, which is in /usr/bin
No, confirmation for Maverick, but I think it would be wise to have a Lucid update. I have fixed my machine with the solution above. Hopefully if this is too hard to implement in an update or against some rules because it is an LTS release, that folks can at least find the answer here. -- /etc/init/mounted-tmp.conf uses find, which is in /usr/bin https://bugs.launchpad.net/bugs/523587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523587] Re: /etc/init/mounted-tmp.conf uses find, which is in /usr/bin
I took another look at my duplicate bug and there is a solution to this included that is quite simple. Not sure why it is such a hard thing to change one item (start on mounted MOUNTPOINT=/tmp ==> start on local- filesystems) in the /etc/init/mounted-tmp.conf upstart job to fix this. https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/602723 Quote from duplicate bug: "The problem seems to happen using a separate /usr partition. According to /etc/init/mounted-tmp.conf, cleaning starts when /tmp is mounted: start on mounted MOUNTPOINT=/tmp However, the script needs /usr/bin/find to cleanup /tmp. Cleanup is failing since /usr is not there (is not mounted) when cleaning starts. Therefor, /tmp is never cleaned Changing it to: start on local-filesystems solved the problem. The cleanup is only started when all local file systems are mounted. I can confirm that this change does work." -- /etc/init/mounted-tmp.conf uses find, which is in /usr/bin https://bugs.launchpad.net/bugs/523587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523587] Re: /etc/init/mounted-tmp.conf uses find, which is in /usr/bin
Sorry, I am bit new to this bug filing game what does *move back to tracking in "head"* mean? -- /etc/init/mounted-tmp.conf uses find, which is in /usr/bin https://bugs.launchpad.net/bugs/523587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556333] Re: Shutdown/Restart from gdm fails silently with 2+ users logged in
I added the affects LTSP to this bug. If you think it is bad to shut the machine down with 2 users logged in how would it be with a computer lab of 25 or 50 users? I think that for LTSP this should have a much higher priority than low. After having this happen to me another 2 bugs https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/602723 cause local applications not to run on the clients that were still running and not logged out at server shutdown. I bug report has been filed with LTSP for this too. https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/602744 -- Shutdown/Restart from gdm fails silently with 2+ users logged in https://bugs.launchpad.net/bugs/556333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556333] Re: Shutdown/Restart from gdm fails silently with 2+ users logged in
** Also affects: ltsp Importance: Undecided Status: New -- Shutdown/Restart from gdm fails silently with 2+ users logged in https://bugs.launchpad.net/bugs/556333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 602744] Re: LTSP client can not run local apps after server is shutdown before client logs out when /tmp is not cleared on next boot.
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/51511056/Dependencies.txt -- LTSP client can not run local apps after server is shutdown before client logs out when /tmp is not cleared on next boot. https://bugs.launchpad.net/bugs/602744 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 602744] [NEW] LTSP client can not run local apps after server is shutdown before client logs out when /tmp is not cleared on next boot.
Public bug reported: Hi! I discovered this bug because of another bug that did not clean /tmp out on each boot. https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/602723 I accidentally shut the server down while on client was still logged in and working. This is possible from the Gnome server login by selecting shutdown. It is not possible if I am logged in and try to shutdown there in tells me I need to give a root password as the system policy prevents shutdown while other users are logged in. That however is another bug report for me to file. Upon the next boot the only the client that was logged in was no longer able to run some local applications. Other terminal were functioning normally. Other users logging on the client that was not shut down properly had the same problem. For example opera would start but the gui interface would never show. If you try to start Opera twice it pops up a window telling you. Running ltsp-localapps xterm would start an xterm window, but running either of the commands ps or ls would cause the xterm window to freeze. I could however run top and pwd. Using Ctrl-Alt-F1 to go to the root terminal and I got the same results. I used the fix in the bug report above so that the /tmp folder would be cleared. Rebooted and everything works as it should. This is a problem that should be fixed as it is possible for a user to set their /tmp folder to only clear files older that a certain age. LTSP needs a way to cleanup its temp files on reboot if they exist in /tmp. I can only image how much grief this would cause a LTSP admin on Lucid when someone accidentally shuts the server down with say 25 client connected and now 25 machine will not run local apps. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: ltsp-server 5.2.1-0ubuntu9 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic i686 Architecture: i386 Date: Wed Jul 7 15:17:00 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ltsp ** Affects: ltsp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- LTSP client can not run local apps after server is shutdown before client logs out when /tmp is not cleared on next boot. https://bugs.launchpad.net/bugs/602744 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 602723] Re: Upstart job to clean /tmp does not run when /usr is on a seperate partion
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/51510113/Dependencies.txt -- Upstart job to clean /tmp does not run when /usr is on a seperate partion https://bugs.launchpad.net/bugs/602723 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 602723] [NEW] Upstart job to clean /tmp does not run when /usr is on a seperate partion
Public bug reported: Binary package hint: mountall Hi! I discovered this problem when an improper shut down of the server before all clients had shutdown on an LTSP system. It seems that the client when it logs out deletes files in /tmp that confuse it when booting again(that is another bug report). However, this can cause problems with /tmp filling up the hard drive with unneeded files that should otherwise be deleted on boot. Ubuntu forum user tall-male also discovered this. See his post here: http://ubuntuforums.org/showthread.php?p=9558012#post9558012 Here is a summary and fix: The automatic cleanup of /tmp at boot time is not working. It wasn't working in Ubuntu 9.10, neither in the new 10.04. The problem seems to happen using a separate /usr partition. According to /etc/init/mounted-tmp.conf, cleaning starts when /tmp is mounted: start on mounted MOUNTPOINT=/tmp However, the script needs /usr/bin/find to cleanup /tmp. Cleanup is failing since /usr is not there (is not mounted) when cleaning starts. Therefor, /tmp is never cleaned Changing it to: start on local-filesystems solved the problem. The cleanup is only started when all local file systems are mounted. I can confirm that this change does work. I filed this report first against upstart itself not knowing what package it should be filed against. https://bugs.launchpad.net/upstart/+bug/602659 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: mountall 2.15 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic i686 Architecture: i386 Date: Wed Jul 7 14:52:26 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mountall ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- Upstart job to clean /tmp does not run when /usr is on a seperate partion https://bugs.launchpad.net/bugs/602723 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176278] Re: [needs-packaging] Rivendell - radio station suite (radio broadcast automation)
*** This bug is a duplicate of bug 258917 *** https://bugs.launchpad.net/bugs/258917 ** This bug has been marked a duplicate of bug 258917 [needs-packaging] rivendell -- [needs-packaging] Rivendell - radio station suite (radio broadcast automation) https://bugs.launchpad.net/bugs/176278 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 249657] Re: [needs-packaging] Rivendell - Radio Station full suite
*** This bug is a duplicate of bug 258917 *** https://bugs.launchpad.net/bugs/258917 ** This bug is no longer a duplicate of bug 176278 [needs-packaging] Rivendell - radio station suite (radio broadcast automation) ** This bug has been marked a duplicate of bug 258917 [needs-packaging] rivendell -- [needs-packaging] Rivendell - Radio Station full suite https://bugs.launchpad.net/bugs/249657 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 249657] Re: [needs-packaging] Rivendell - Radio Station full suite
*** This bug is a duplicate of bug 176278 *** https://bugs.launchpad.net/bugs/176278 ** Also affects: rivendell Importance: Undecided Status: New -- [needs-packaging] Rivendell - Radio Station full suite https://bugs.launchpad.net/bugs/249657 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176278] Re: [needs-packaging] Rivendell - radio station suite (radio broadcast automation)
** Also affects: rivendell Importance: Undecided Status: New -- [needs-packaging] Rivendell - radio station suite (radio broadcast automation) https://bugs.launchpad.net/bugs/176278 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258917] Re: [needs-packaging] rivendell
** Also affects: rivendell Importance: Undecided Status: New -- [needs-packaging] rivendell https://bugs.launchpad.net/bugs/258917 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
