LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Bodhi
User Name
Password
Bodhi This forum is for the discussion of Bodhi Linux.

Notices


Reply
  Search this Thread
Old 09-03-2019, 08:39 AM   #1
soho
LQ Newbie
 
Registered: Sep 2019
Location: Brazil
Distribution: Ubuntu, Bodhi, Debian
Posts: 4

Rep: Reputation: Disabled
Broken systray in Bodhi 5


Hello,

I use Bodhi Linux 5 as a Virtualbox VM to make L2TP/IPSec VPN connections to different networks. Everything works smoothly and very, very fast.

Yesterday after updating my Bodhi 5 (Ubuntu Bionic updates) using the main repository, the systray gadget broke. My source.list was as below:

Quote:
deb http://us.archive.ubuntu.com/ubuntu/ bionic main restricted
deb http://us.archive.ubuntu.com/ubuntu/ bionic-updates main restricted
deb http://us.archive.ubuntu.com/ubuntu/ bionic universe
deb http://us.archive.ubuntu.com/ubuntu/ bionic-updates universe
deb http://us.archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://us.archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb http://us.archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
deb http://archive.canonical.com/ubuntu bionic partner
deb [trusted=yes] http://packages.bodhilinux.com/bodhi bionic b5main
deb https://dl.winehq.org/wine-builds/ubuntu/ bionic main
Below the message from xsessionerrors

Quote:
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
ERR<1254>:edje lib/edje/edje_calc.c:799 _edje_part_description_apply() Cannot find description "active" in part "knob" from group "e/sys/logout". Fallback to default description.
## Copy & Paste the below (until EOF) into a terminal, then hit Enter
eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fbabbd5fd4c 0x7fbabbd39000
/usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fbabbd60a71 0x7fbabbd39000
/usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fbabbd61e73 0x7fbabbd39000
/usr/lib/x86_64-linux-gnu/libedje.so.1 0x7fbabaad7412 0x7fbabaaa6000
/usr/lib/x86_64-linux-gnu/libedje.so.1 0x7fbabab4fe81 0x7fbabaaa6000
/usr/lib/x86_64-linux-gnu/libedje.so.1 0x7fbabaadf22e 0x7fbabaaa6000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fbab721ab1f 0x7fbab7203000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fbab7214887 0x7fbab7203000
/usr/lib/x86_64-linux-gnu/libevas.so.1 0x7fbabb6b3c9b 0x7fbabb669000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fbab721af3f 0x7fbab7203000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fbab7214797 0x7fbab7203000
/usr/lib/x86_64-linux-gnu/libecore_evas.so.1 0x7fbabb1d3dbd 0x7fbabb1c1000
/usr/lib/x86_64-linux-gnu/libecore_evas.so.1 0x7fbabb1d3f43 0x7fbabb1c1000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb3fe719 0x7fbabb3ea000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb40046d 0x7fbabb3ea000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb444ae9 0x7fbabb3ea000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb3fe172 0x7fbabb3ea000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb440cee 0x7fbabb3ea000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb4414d6 0x7fbabb3ea000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb4078b3 0x7fbabb3ea000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb4081cd 0x7fbabb3ea000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb40ff09 0x7fbabb3ea000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb40f097 0x7fbabb3ea000
/usr/lib/x86_64-linux-gnu/libecore.so.1 0x7fbabb408297 0x7fbabb3ea000
/usr/bin/enlightenment 0x55ae4122241b 0x55ae411eb000
/lib/x86_64-linux-gnu/libc.so.6 0x7fbab8fdcb97 0x7fbab8fbb000
/usr/bin/enlightenment 0x55ae412233da 0x55ae411eb000
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
SYSTRAY: reactivate...
SYSTRAY: activate failure! retrying in 2,0 seconds
SYSTRAY: reactivate...
I changed source.list to the b5testing repository:

Quote:
deb [trusted=yes] http://packages.bodhilinux.com/bodhi bionic b5testing
and I updated Moksha, but the problem persists.

I'm currently using nmcli to connect to VPNs, but nm-applet helps me make these connections on a daily basis.

Any tricks I can implement to get systray back?
 
Old 09-03-2019, 05:16 PM   #2
soho
LQ Newbie
 
Registered: Sep 2019
Location: Brazil
Distribution: Ubuntu, Bodhi, Debian
Posts: 4

Original Poster
Rep: Reputation: Disabled
Solved!

I deleted in my user's home the .e folder and restarted, all environment configuration files were created and systray went back to work.
 
Old 09-03-2019, 06:13 PM   #3
rbtylee
Bodhi Developer
 
Registered: Jun 2018
Location: Ladson, SC US
Distribution: Bodhi
Posts: 204

Rep: Reputation: 207Reputation: 207Reputation: 207
Strange I haven't saw that happen on updating to moksha 3.1. I did see the same error msgs in development tho. Glad you got it sorted out. I will try to duplicate the issue but it may have been something specific to your setup.
 
Old 09-03-2019, 07:19 PM   #4
soho
LQ Newbie
 
Registered: Sep 2019
Location: Brazil
Distribution: Ubuntu, Bodhi, Debian
Posts: 4

Original Poster
Rep: Reputation: Disabled
It was not due to Moksha 3.1 update, the error occurred after the base update (Ubuntu).

I changed the repository to b5testing and updated Moksha after the error, but it still went on.

But it was probably some misconfiguration I had made (and there were several) regarding the themes and graphic environment and it was saved in the .e folder in my user's home. I have no idea what configuration was wrong because I didn't investigate what was in .e, just removed and rebooted as a tip I saw in the thread about upgrading Moksha to the testing repository version.

Regards,

Sergio
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Ubuntu 18.04-Based Bodhi Linux 5.0 Enters Beta with Bodhi Builder Improvements LXer Syndicated Linux News 0 05-30-2018 11:12 AM
LXer: Bodhi Linux 2.4.0 Released, One Year Left Until Bodhi 3.0.0 LXer Syndicated Linux News 0 09-14-2013 05:21 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Bodhi

All times are GMT -5. The time now is 08:44 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration