Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


ylee last won the day on April 8

ylee had the most liked content!

Community Reputation

425 Excellent

About ylee

  • Rank
    King of the Software Page
  • Birthday 06/19/1960

Profile Information

  • Gender
  • Location
    South Carolina, USA
  • Interests
    Programming, Mathematics, Linux, Philosophy, Vegetarianism, Science Fiction

Recent Profile Visitors

16671 profile views
  1. ylee

    Moksha repository for Debian?

    Yes in source, moksha-modules-extra. Also since any module that works with e17 should in theory work with Moksha, there are a few additional modules if one hunts for them. As to this point some modules that worked with older versions of e17 may fail to compile but only minor changes are usually required to make them work.
  2. ylee

    Moksha repository for Debian?

    Glad you got it sorted out, perhaps not the route I would have taken but if it works it works Yes there have been a few minor changes to systray. It should work better now. I must be used to the problem of moving gadgets because that never bothered me. And we all agree the settings panel needs an overhaul but again I am used to it and know where to find everything I am likely to look for. As to modules believe it or not there are actually more modules available than are found in Bodhi's repo.
  3. ylee

    [solved] 'e_dbus dependancy / Install on arch

    Ok it seems you are right moksha is using /legacy/eldbus and not e_dbus in elementary. /legacy/eldbus should compile ok with the latest efl.
  4. ylee

    [solved] 'e_dbus dependancy / Install on arch

    Ok yes edbus is needed and checked for but as you have noted it is merged into elementary these days so that test in configure.ac is met. It seems the moksha package in aur.archlinux.org is dated and no longer installs with broken dependencies. Whoever packages it there needs to fix that. Aside from that if you wish to install moksha you are going to have to do so manually. Perhaps some Arch users will chime in here.
  5. ylee

    How to install Moksha on Arch Linux and derivatives

    I am not an Arch user but Moksha compiles file using efl 1.20.7. I have been actively working on Moskha dev branch and using the latest efl for a weeks now. Compiling it every day. So no need to change anything in Moksha. How are you trying to install Moksha?
  6. ylee

    Moksha repository for Debian?

    You have said you are reluctant to try to compile the code, but truthfully the only way you are going to be able to make a bodhi clone on debian right now is to compile code. For example, you say: But really this is wrong. You are going to need to compile moksha itself. And for moksha to work you are going to need to have a functioning EFL installed. Moreover you are going to need to compile mokshas modules: Places, pulsemixer, clipboard (x_clip branch) and so on. This is a non trivial task. There is currently no easy way to do this. It should be noted however you can compile the code to deb files to make installing and uninstalling easier. I could probably get something like this functioning in a week or less if I didn't have to work or do the work I am currently doing on the Moksha source code. Maybe in the future we can set something up to make all this easier.
  7. ylee

    Moksha repository for Debian?

    I don't recall Bodhi even being debian based. I remember when Me and a former Team member Otterman were working on a Debian version of Bodhi, but we never released an ISO. Maybe it was before me using bodhi but that was Bodhi 1.x unsure exactly which version. As to your question lupin-casper is not needed for Moksha or Bodhi really except for the usb image to work.
  8. ylee

    [Solved] No network devices available

    The forums have changed so anyways I did it for you But I think you could have edited your first post and changed the title.
  9. ylee

    Forum Login Issue

    works in my tests
  10. OK this is my mistake The problematic deb files are now fixed. Thanks for reporting But these are not new backgrounds per se. All of the bodhi-background deb files except one were broken in a subtle way in our repos. They installed ok but they broke another program which indexes the information in the deb files mainly used by synaptic if it is installed, namely apt-xapian-index. I rebuilt 53 of them yesterday to fix the broken control file they contained. Only the control file should have been changed the images contained are the same. I did a few by hand and then wrote a simple and simple minded bash script to do the rest, because doing it by hand would have taken forever it seemed. By simple minded I mean the script did no error checking and required me to use it correctly. Evidently the using it correctly part I failed to do so on these 4 particular deb files. Not bad out of 53 but still. I was going to redo the rest of the bodhi-background deb files soon, maybe latter today before I tested them. Build and test build and test for each deb file would have slowed the process down dramatically I thought. Of course I also thought if anything failed to work it would not be noticed immediately. But then you noticed, lol. Oh well life goes on ... And for the record hopefully the rest install ok. I just installed the bodhi-backgrounds-pack successfully, which in theory should install them all. After I am done I will double check everything
  11. ylee

    Submenus missing after software installation

    Ok I added all of these and Bodhis menu works fine. I can not duplicate your issue. Also the menu worked fine with my modified version. You can try the update-menus command to see if that helps: sudo update-menus You can also try to reinstall the debian science stuff you suspect broke the menu.
  12. ylee

    Submenus missing after software installation

    @PeterP did you try the new menu? Note to use this menu you must install moksha-menu. EDIT: Also restart moksha or log out and log in or reboot, to see changes.
  13. ylee

    Submenus missing after software installation

    The menu system on modern linux desktops is rather complex. For all the geeky complex details see the xdg standard. I am not going to try to simplify and explain this standard as it is about as simple as it can be on the freedesktop.org website. But lets clear up a few confusions first. On bodhi the list found in the window menu-settings-Settings Panel-Menus tab->Menu settings is simply the list of files found on your machines /etc/xdg/menus folder. These are xml files which describe a menus structure. You can only select one. Well the e-devs are NOT the authors of this idea, this idea came about because early linux windows managers had various ways of dealing with menus and this standard came about as well as the update-menus command to make things simpler for the end user. So the e-devs are responsible for the code in enlightenment and moksha which IMPLEMENTS this standard but they are not responsible for the standard itself. As to why these profiles are there every file in /etc/xdg/menus is something the user has added. Unless it was manually added it was added by installing something. The E applications and the LXDE applications are preinstalled in Bodhi 4.x. e-applications.menu is installed by Moksha itself and lxde-applications.menu is installed by the lxmenu-data package. If other menus are showing up there, gnome, kde xfce, unity or whatnot they all have came from something the user installed. Any of these files can be edited by the user (as root) but I would advise against it unless you are sure you know what you are doing. Moksha and other window managers/desktop environments will not function correctly if the menu file they are using is broken or absent. Maybe this clears things up for yall or maybe it just confuses you more. If confused by it just ignore it and care on, lol
  14. ylee

    Submenus missing after software installation

    I have made some changes to mokshas menu for our next release. Please give the new menu a try to see if ti helps with this issue: From Bodhi Linux Forums → Bodhi Team → Development (only viewable by Team members) Ordinarily I would test this to ensure it works first but there are alot of debian science packages and my testing is on a VM and installing all this on a VM would error out as the hard drive became full. BUT if this does not help with your issue, I will look at it further. If this is the case which debian science packages did you install. Give me a complete list and I will try to duplicate this issue.
  15. ylee

    wierd UI behaviour with eepDater

    Yep shoving an xterm into the window certainly sounds like the easiest solution, perhaps not the 'prettiest' tho It would add a dependency on xterm to the application but that is not a big deal. Well thanks on the $DESKTOP variable, should be easy enough to modify, The About Bodhi dialog is weird and prob some subtle bug in EFL. The oddest thing is About Moksha works and the code implement each is sorta the same, with the exception About Moksha is split into two functions and the use of defines by About Bodhi. Anyways I am very thankful of all you have did for Bodhi and for EFL. We all struggle with time and RW pressures.