Jump to content

Rene Malmgren

  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Rene Malmgren

  • Rank
  1. Rene Malmgren

    Moksha not so stable.

    Hi, I have been using Bodhi now for several years, and I do it more or less on all my three workstations. Recently I have had really annoying stability problems with Moksha. After a while, ( can be betweend 1-2 days to two weeks ) the windows system crashes. Usually it stars by preforming badly ( slowly ) and then after a while it stops updating the screen at all. The only knows antidote that I have found so far is to switch to console and then kill all the enlightenment processes, and to log in again. the interesting thing is that both my home computer, running a Intel i7 with internal GFX and my Intel i5 here at work seem to have the same problem. While my old old computer that runs om AMD and Bodhi 3 does not. I realize that this is not a very good bugreport, but it would be cool if we could track down the bug. So what am I looking 4. Well for starters, is there any way we could get logs out from E / M so that we can try to narrow down the bug? I suspect that the problem could be related to Chrome / Firefox and E / M. /Rene
  2. Rene Malmgren

    Signing keys

    Hi! I ( once again ) noticed that my bodhi packages are unsigned and therefor not trusted by the system. Is there an official Bodhi GPG key that I have not manage to find, and if not ans was indicated on other parts of the forum, then why not /Rene
  3. Rene Malmgren

    Manual upgrade from Bodhi 3x to 4.0

    :Update: Upgrading Bodhi 3x -> 4.0 with this method works well for me, with a few noticable problems that I have over looked. They will lead to problems with the packager if they are not fixed. This is how you detect and fix it. There are three files of concern. /etc/lsb-release /etc/issue /etc/os-release These files are part of http://packages.ubuntu.com/sv/xenial/base-files This file tell the system what release you are running. For a bodhi 3.x system it is trusy, for a 4.0 its xenial. Make sure that these files are updated. After this has happend you should update all PPA:s that run on a dist based system. in my case I have a PPA videolan-master-daily-trusty.list should be updated to videolan-master-daily-xenial.list #remove it sudo add-apt-repository -r ppa:videolan/master-daily #add it again sudo add-apt-repository ppa:videolan/master-daily
  4. Rene Malmgren

    Skype and Bodhi Linux

    I have been running debian for about 20 years now . As far as I can see, things went well. System boots, encrypted harddrives unlocks as expected. I think we should get a post up how you can try and "unsupported" upgrade path from 3.x to 4.0. Its actually not that hard. Just do a search and replace in /etc/apt/sources.list, change trusty -> xenial, and on the bodhi lines change main -> mainb4 ( why mainb4? ) And then do a manual upgrade of all the packages. apt-get update apt-get upgrade apt-get dist-upgrade this has to be repeated several times, and some times you will have to do dpkg -i --force-overwrite <debfile> When you get some conflicts of files in multiple packages, mostly in /var/share/doc ( these can safely be overwritten ). Yes you might be right, I was mixing in debian/testing a while back and I might have gotten in too new packages. Although my impression was that some of the problem was the result of packages ending with +b3 or +b4 or +b1, witch indicated bodhi versions of ubuntu packages, so building the packaged from source worked. Anyway thanks for the help, if I find out more, I will update this thread
  5. Rene Malmgren

    Skype and Bodhi Linux

    It might have been that I was a bit too agressive with my manual upgrade. I have managed to install skype now, with a bit of tweeking.
  6. Rene Malmgren

    Skype and Bodhi Linux

    I have upgraded a Bodhi 3.0 by modifing sources.list. As far as I can tell, this is bodhi packages in conflict with skype packages
  7. Rene Malmgren

    Skype and Bodhi Linux

    Hi all, I have just managed to upgrade to 4.0, in a sort of a hack upgrade. And many things are working fine now. Unfortunatly, and I am not sure if I have messed something up, but Skype will not install. It seems like there are special Bodhi packages that conflict with the dependencies. Anybodt that has managed? # sudo apt-get install libqtwebkit4:i386Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libqtwebkit4:i386 : Depends: libqt4-opengl:i386 (>= 4:4.5.3) but it is not going to be installed Depends: libqtgui4:i386 (>= 4:4.8.0) but it is not going to be installed Depends: libsqlite3-0:i386 (>= 3.5.9) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Trasing things down the package liblcms2-2:i386 seems to conflict with the entire bodhi universe . What would be the best way forard? /Rene
  8. Rene Malmgren


    Hi I was trying out virtualisation, on my Bodhi last night. As far as I can see we have not enabled some flags in the kernel. When I run lxc-checkconfig --- Control groups --- Cgroup: enabled Cgroup namespace: required Cgroup device: enabled Cgroup sched: enabled Cgroup cpu account: enabled Cgroup memory controller: enabled Cgroup cpuset: enabled
  9. Rene Malmgren

    Manual upgrade from Bodhi 3x to 4.0

    Yes, I have read the release notes . But my 20 years of knowledge in Linux ( yes I started with it 1996 ) tells me that this is not the entire story. And for my system, doing a upgrade rather than a reinstall would be really really great. As far as I understand, the base of Bodhi is Ubnuntu, TT in case of 3.x and XX in case of 4.0. So I guess in theory, the big difference is the sources.list file in apt? If you would simply just add the XX repos to an 3.x the path upgrade should be there? Or is there some thing else that I am horrebly missing?
  10. Rene Malmgren

    Switching workspaces with dual monitors

    Thats not true, but its disabled by default. And you cant use an *randr. You will mess upp your E-setup.
  11. Rene Malmgren

    Bodhi does not set the correct language when booting the USB stick

    Let call it an quite essential feature . Anyway I thought the drawback should atleast be documented. Becase the effects are very severe. You wind up with a system that you cant get into.
  12. As many people have found out. E and mulitmonitor setup is not smooth sailing. The problem is based around the fact that X and E do have there own ideer of how the desktop is setup, and they can get out of sync. The only way to configure E is to use the ScreenSetup module. While you can configure X using xrandr, lxrandr and so on. In theory, ScreenSetup should be used because this will configure E aswell as X. Unfortunately its buggy. But still disabling the module makes things worse
  13. When installing Bodhi, you usually use a USB stick that you prepare. Unfortunately, this does not configure the correct keyboard map. Now in many instances this does not matter, but unfortunately there is one instance where it matters a great deal, and that is when you are entering passwords, because here you don't see the charachers, and this becomes very bad if you select a encrypted harddrive password with the wrong keymap, so the password enterd is not the password you where expecting.
  14. Rene Malmgren


    It would be cool if we could work harder to make the community bigger and more easy to get into. A few things i would love is 1. An issues tracker. 2. User Accounts so the we can update wiki and stuff. 3. Make it easy to report a bug on a bodhi installation.
  15. Rene Malmgren

    [BUG/s] xrandr extended desktop

    Hi. I know your pain. I have been running quite a complex setup for a few years, and sorting this mess up is something that is really high on my agenda. Spent about 3h yesterday because I had to reinstall my comp configuring the screen. So I post my knowledge on the subject. The problem is not only about bodhi, its a generic E problem, and its based on the fact that E needs to understand the setup of the screens, so there is cone configuration for X ( controlled by lxrand ) and one for E ( controlled by the Screen Setup module ) it self. Unfortunately, Screen Setup is buggy and for some reason disabled in bodhi by default. So my first advice is to enable it ( Menu -> Settings -> Modules, select Settings, load Screen Setup ) and see if it works for you and do not touch lxrandr. In theory, Screen Setup will call randr when you modify stuff. Report any bugs you find . In my case, I run a rather complex setup with two FullHD monitors on either side of an UltraHD monitor ( in the ceter ), this was not enough. So I had to use xrandr first to setup X in a corrrect way. Then use Screen Setup, and then save the lxrandr config aswell. I guess Jeff knows more about the interior mecanisms