Jump to content

Photo

Moksha problems on Bodhi 3.2.1


  • Please log in to reply
6 replies to this topic

#1 TJMcK

TJMcK

    Member

  • Members
  • 18 posts
  • LocationCanada

Posted 31 December 2016 - 01:43 AM

The past few weeks I've had problems with Bodhi, most likely caused by Moksha.  This occurs almost every day (normally I like to leave my laptop on 24/7).

 

I've not reported the problem sooner because I wanted to associate it with an event or app, but I can't make any correlation. I realize that there is a problem when starting an app and I get a Moksha error dialog: "Miksha settings write problem".  From that point on I can't logout or poweroff in any way (with keystrokes or via terminal).  As well, no apps will open/start.  The Moksha dialog box does not show any details and after doing a hard-reboot I cannot find any file reporting the failure.

 

I have read as much as I could find regarding this issue: for instance, my drive has enough space (although it is an external SSD) - but this has not been a problem earlier. I also read that the network manager has been associated with Moksha problems... I installed the Private Internet Access deb package around the time that the issues started -- but I also installed Wine and the NVidia/Radeon proprietary driver with Catalyst at this time.

 

Do you have suggestions on what I could try/do to fix this?  I noticed there has been a Moksha v.0.2.1 released -- should I try installing this? (it appears that I'm using 0.2.0)

  

  - Tim





A big thank you to everyone who contributes to Bodhi Linux


#2 Jeff

Jeff

    Lead Developer

  • Developer
  • 12333 posts
  • LocationBloomington, IL

Posted 31 December 2016 - 03:22 AM

Can you please post the output of the command:

 

df -h


#3 TJMcK

TJMcK

    Member

  • Members
  • 18 posts
  • LocationCanada

Posted 31 December 2016 - 04:36 AM

Filesystem      Size  Used Avail Use% Mounted on
udev            2.7G  4.0K  2.7G   1% /dev
tmpfs           554M  1.5M  553M   1% /run
/dev/sdb2       112G   12G   94G  12% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
none            5.0M     0  5.0M   0% /run/lock
none            2.8G   12M  2.7G   1% /run/shm
none            100M  8.0K  100M   1% /run/user
/dev/sdb1       511M  6.9M  505M   2% /boot/efi

Edited by Charles@Bodhi, 31 December 2016 - 12:19 PM.
added codetags for readablity


#4 The waiter

The waiter

    Module Master

  • Developer
  • 1457 posts
  • LocationBanska Bystrica, Slovakia

Posted 31 December 2016 - 03:38 PM

Can you perform some hdd checks to confirm your disc is in good condition?

sudo smartctl -a /dev/sdb | less

This command should be a good start...

Anyway follow this link with Jeff's advices same as here with solution where home folder was full:
http://forums.bodhil...nt-write-error/

#5 TJMcK

TJMcK

    Member

  • Members
  • 18 posts
  • LocationCanada

Posted 31 December 2016 - 05:14 PM

Can you perform some hdd checks to confirm your disc is in good condition?

sudo smartctl -a /dev/sdb | less

This command should be a good start...

Anyway follow this link with Jeff's advices same as here with solution where home folder was full:
http://forums.bodhil...nt-write-error/

 

I perform a short-test and extended-test with smartctl -- both didn't show any errors.

 

And there should be plenty in the /home folder (found in /) -- I checked trash and there was <1Gb.

 

/dev/sdb2       112G   12G   94G  12% /


#6 The waiter

The waiter

    Module Master

  • Developer
  • 1457 posts
  • LocationBanska Bystrica, Slovakia

Posted 31 December 2016 - 05:21 PM

Hmm. Is it a big issue for you to backup .e folder, erase it, logout and reconfigure all settings? In case it won't help just take backup back.

#7 TJMcK

TJMcK

    Member

  • Members
  • 18 posts
  • LocationCanada

Posted 31 December 2016 - 11:16 PM

Hmm. Is it a big issue for you to backup .e folder, erase it, logout and reconfigure all settings? In case it won't help just take backup back.

I've tried a few things in the past few hours...  if these changes don't solve the problem, I will do as you suggest and reconfigure .e settings.  Thanks.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users