Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


aFriend last won the day on May 19 2016

aFriend had the most liked content!

Community Reputation

2 Neutral

About aFriend

  • Rank

Profile Information

  • Gender
    Not Telling
  • Location
    England, Uk
  • Interests
    Psychology, Spirituality and Computing
  1. I am trying to clarify how to launch programs in Bodhi/Moksha as root when I need to. There are 2 related issues: 1. The issue of when it is appropriate/inappropriate for applications to use sudo to gain root priveleges as outlined in article titled: Running Sudo Graphically: http://www.psychocats.net/ubuntu/graphicalsudo 2. How to use Run Everything for a graphical launch of an application as root in Moksha. The psycocats article linked above essentially says that should one launch a graphical program in the terminal with sudo (thus leading to root privilege) this use of sudo uses the user’s configuration file. In most cases this will not cause problems – but it may cause severe issues when it matters. On the other hand the advisable way to gain root priveleges is to ensure that the configuration file used in the process is the application’s root configuration file. For gnome this requires the use of gksudo (rather than sudo), and for KDE one would use kdesudo when launching for root priveleges. Summary at psychocats (quoting the article): Bottom line: most of the time when you use sudo for graphical applications, it's fine. Some of the time, though, it is not fine, and is, in fact, extremely bad... good practice: gksudo and kdesudo for graphical applications. sudo for command-line applications... Running graphical applications with sudo also has the downside of always having to be run from the terminal. If the argument at psychocats has validity, and also for my own convenience, I would like, when I need root priveleges for a graphical application, to launch it from a menu entry (for example as gparted/synaptic launches from the menu in presenting the eSudo dialogue for the password). I assume I am to use Run Everything to set the parameters to launch as root. At the simplest level I am having problems setting up as a menu item a New Application Entry for pcmanfm so that I may launch it as root. I have followed the instructions at http://www.bodhilinux.com/w/personal-application-launchers/ for Example 2: Launching a command-line application. My entries in the Desktop Entry Editor for Basic are, Name: File Manager PCManFM(root); Application: esudo pcmanfm %U (also tried: esudo pcmanfm and esudo pcmanfm-gtk). Entry under General is for Categories: System (also tried System Tools). All other entries are unchanged. No new entry appears in my System/System Tools menu after the changes; when I go back into Run Everything the New Application Entry I made for pcmanfm does not show. I can launch eSudo independently and fill in command (pcmanfm) and password manually, and this works. Am I overlooking something obvious in setting up my personal application launcher for pcmanfm as root. If it is simple to explain, could someone please explain the different circumstances calling for different type Application entries in the Desktop Entry Editor for launching graphical applications as root. For example the following different types of Application entries (in italics) now show for applications in my Desktop Entry Editor: Synaptic: esudo synaptic – works perfectly (i.e. launches the eSudo dialogue specifying the program synaptic Back in Time: su-to-root –X –c backintime-gnome (works perfectly, as above) Back in time: backintime-gnome (launces correctly as needed, without root priveleges). Logical Volume Management (system-config-lvm): /usr/bin/system-config-lvm. This launches the program – but with error message: No D-Bus daemon running. If these differences are too complex to explain because of the different ways programs are configured I would appreciate an overall view. I would certainly be grateful to know how to launch pcmanfm with root priveleges through a menu entry. Thank you.
  2. aFriend

    Nepomuk Cleaner?

    Came across this thread when doing a google search on Nepomuk Cleaner after I noticed it in my System Tools menu in Bodhi 3.2. In Virtualbox, going to a recent previous snapshot of the Bodhi installation I can see it wasn't there before. I am almost certain it appeared after installing my first KDE application (KVPM - an LVM frontend). Reading this thread has confirmed for me that it was pulled in as a dependency. Thank you.
  3. I have been studying your indications of my problem; thanks specially for indirectly pointing out the df command to me in a previous post of yours. Its a very useful command for me to know - because the LVM oriented display commands I was using were not giving me clear information on used/available disk space. So I have studied up on LVM stuff some more. Yes, I had extended the logical volume for /home from its very small size of 380MB to above 8GB - and all my LVM display commands confirmed this. I thought this was all that was needed to expand space for /home. BUT, I find, I had neglected to then do another needed step: resize (resize2fs) and expand the ext4 file system within the logical volume! Well, problem solved. Thank you, sef, for bearing with me . Bodhibuilder ran fine after this. I have tested the output iso in Virtualbox - and its working well. In the next few days I will attempt an install on the PC. That will, for me, be the first time with Linux directly on hardware. Another adventure awaits.
  4. <-sef>, on 17 May 2016 - 5:05 PM, said: Your home dir is only 380Mb total. Thanks sef, for pointing that out; still getting used to lvm! So I extended the lv for home to above 8GiB. Unfortunately, this didn't handle the problem: still getting same error message re squashfs. If you still have your /home/bodhibuilder/bodhibuilder directory report the output of these commands: $ cd /home/bodhibuilder/bodhibuilder/ $ sudo du -s ./* $ df So I am uploading the terminal output for the above, and also the log file from latest run of bodhibuilder: https://drive.google.com/file/d/0B5WReHwtypzCWWtabDc1bVREYWM/view?usp=sharing https://drive.google.com/file/d/0B5WReHwtypzCOEcxU2NkbUFRWG8/view?usp=sharing Another thing, did you do your install to VirtualBox as a UEFI install, or not? No, I do not have EFI enabled in Virtualbox settings. Another thing I like to do, to keep it simple for the sake of just making an ISO, is to just let /home sit on the root of the drive. Not something I have got round to do. I really thought extending the space for /home, which was an anomaly I obviously overlooked, would solve the problem.
  5. Thanks sef. I am attaching the log file (btw, correcting for spaces in my file/folder names didn't resolve the problem - got same error message). Perusing the log file I noticed, at line 256, FATAL ERROR: Failed to write to output filesystem. My / and /home are set up with lvm2/ext4 - each has a volume group and a single logical volume; neither has snapshot volumes. Log file is at: https://drive.google.com/file/d/0B5WReHwtypzCTWJzUU9wTTJYcUU/view?usp=sharing
  6. I have followed through on the above helpful guidance on using bodhibuilder, using Bodhi 3.2x64 in Virtualbox as a base; also transferred my user settings/data from /home/bodhi (only about 55Mb) to /etc/skel, after deleting what was in /etc/skel. I chose the 'dist' option (for the creation of both cdfs and iso) - but after a short time of staring the program I got the message: The process was interrupted. Last output from the program was: Found 'usr/bin/xorriso' Currently planning to use 'xorriso' to create the iso The filesystem.squashfs filesystem is missing. Either there was a problem creating the compressed filesystem or you are trying to run sudo bodhibuilder 'dist' before sudo bodhibuilder dist cdfs I assume the error relates to the 'squasfs options' under 'Settings' in bodhibuilder - which I left blank according to guidance in the tooltip. In Synaptic I can see that a package called 'squashfs-tools' is already installed on my system. Any help would be appreciated. Thank you. P.S. Just did a google on the above problem: 2 possible suggested solutions I will look at: 1. Not enough space on 'working directory', i.e. /home. I have 8.35GiB unused on /home - with the system on / being only 3.3GiB. 2. Another solution suggested is: check your root folder if there is any file or folder with space in its name and remove it. I will try out solution 2 since some of my personal files in etc/skel are likely to have spaces.
  7. Thank you, sef and Charles, for the feedback. If I decide on the 'mimic copy' route, your responses help me to plan a strategy towards moving Bodhi directly onto the PC.
  8. Hello, Following on from the OP's question, would a bodhibuilder iso work in my situation. I have now installed Bodhi 3.2 in Virtualbox 4.2.12 for Windows. For the moment I am simply playing around a bit - but I will start setting it up soon. In the context of this thread: bodhibuilder 2.1.0 - which includes user data in the 'Backup', and allows for exclusions - seems to be available in Bodhi 3.2. I accessed it today. Will a bodhibuilder iso created within my Bodhi Virtualbox guest be suitable for installation on a PC - or will the fact of creating the image within a virtual machine (or/and a Windows host), rather than on PC hardware, prevent the installation?I have looked up Chapter 6 of the book "Bodhi Linux 3 for Beginners", with its instructions on using Remastersys. [A thank you here to Jolly Roger for wonderful clear and coherent guidance]. The guide for Remastersys appears to apply perfectly for Bodhibuilder. Bodhibuilder seems to me, in its usage (and discounting internal changes for uefi) , to be the same as Remastersys. If I am wrong please let me know; otherwise, I simply wanted to add this information about instructions on using bodhibuilder/remastersys to the thread.
  9. aFriend

    Hello from England

    Hello, Thank you for the wonderfulness of Bodhi, and the forum to help us (currently Window 7 users) get there. I have already been reading some of the posts and guides, and that is helping me think about the factors and steps in this time of transition from Windows to Bodhi Linux. I write this as I download Bodhi 3.2. I have been here on this forum in a previous incarnation! What's different this time is that my wife (who is, in the nitty gritty sense, tech averse) is now committed to our move to Bodhi Linux. This happened after we read about Windows 10 recently: essentially about a loss of control over our operating system and desktop (even hardware, given that Microsoft are now placing limits on what hardware certain versions of Windows will support). We were taken a back to discover that we would have no control over updates, the addition or withdrawal of features etc. - and there are great concerns about privacy. To indicate our commitment (to ourselves) towards moving away from an absolute dependence on Windows to using Bodhi Linux as our main operating system, we also decided to become Bodhi members - as much for ourselves, and also of course for the community. Thanks once again for being here. I am gladdened to join you.