LinuxQuestions.org - LXDE-Panel

Page 1 of 2

Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - LXDE-Panel (https://www.linuxquestions.org/questions/slackware-14/lxde-panel-4175475478/)

Jeebizz

09-01-2013 12:49 PM

LXDE-Panel

2 Attachment(s)

Every now and again I notice weird things with LXDE, programs in the panel will be acting weird, not sure exactly how to explain it but an example is if I have Firefox running it will 'be flashing' as if I am holding down a key and it is 'pulsing', even though I am not even touching the keyboard and mouse. The main issue though is the icon that lists all programs, sometimes I have to refresh LXDE to get it to list again, or sometimes destroy the local directory and start fresh to get listings back, I managed to at least get a screen of that.

LXDE programs suddenly missing (lower left of the screen):
Attachment 13325

Now it is normal:
Attachment 13326

Anyone who uses LXDE seen this behavior before? :scratch: I am using Ponce's LXDE packages.

TommyC7

09-01-2013 06:02 PM

Hi Jeebizz,

I too am using lxpanel (although I'm using the official releases that LXDE releases). Usually if it's flashing there was some sort of activity in that program that triggers it (e.g. someone messages me on Facebook in Pidgin while it's minimized or when I've got a different program in the foreground).

As for the menu applet not listing all programs/applications available, I don't know about.

Jeebizz

09-01-2013 06:37 PM

Thing is it was just firefox, no addons for facebook or anything. It was really acting erratic - firefox was minimized but the panel was acting like firefox was constantly reloading the page, even though I had it on a blank page... I guess I could try downloading lxde itself, but I'm too lazy to compile it right now.

ponce

09-02-2013 11:56 AM

if you create a fresh new user and so you use lxde with a fresh profile, does the same behaviour show?
are you using these packages (I suppose you have slackware64-14.0)?

Jeebizz

09-02-2013 01:33 PM

Quote:

Originally Posted by ponce (Post 5020376)

if you create a fresh new user and so you use lxde with a fresh profile, does the same behaviour show?
are you using these packages (I suppose you have slackware64-14.0)?

Using these: http://ponce.cc/slackware/slackware64-14.0/lxde/ and yes even after I recreate the profile it happens. I am also running Slackware14.0-64bit with multilib (Alien Bob's multilib). It seems to be random/intermittent - it also usually happens after closing a program like firefox, or any window that is fullscreen. I know that still doesn't sound like a lot of info but thats all I got.

ponce

09-02-2013 11:09 PM

you can edit the file

Code:

~/.config/lxsession/LXDE/autostart

and redirect its output in a file, so you can inspect it

Code:

@lxpanel --profile LXDE >> /tmp/lxpanel.log

Jeebizz

09-02-2013 11:34 PM

That file does not exist:

Code:

slackuser@slackmachine:~$ ls -al .config/lxsession/

total 12

drwx------  3 slackuser users    8 Apr 30 20:02 ./

drwxr-xr-x 31 slackuser users 4096 Jul  1 22:38 ../

drwx------  2 slackuser users 4096 Jun 17 18:41 LXDE/

slackuser@slackmachine:~$ ls -al .config/lxsession/LXDE

total 8

drwx------ 2 slackuser users 4096 Jun 17 18:41 ./

drwx------ 3 slackuser users    8 Apr 30 20:02 ../

-rw-r--r-- 1 slackuser users  491 Jun 17 18:41 desktop.conf

slackuser@slackmachine:~$

ponce

09-02-2013 11:53 PM

should be copied automatically from the xdg folder ( /etc/xdg/lxsession/LXDE/autostart ) if not there when you start lxde: you can also copy it manually into ~/.config/lxsession/LXDE/autostart but that's probably a sign that something is behaving strange... are you running a Slackware full install?

Quote:

Originally Posted by Jeebizz (Post 5020434)

even after I recreate the profile it happens.

if you haven't done it already don't recreate your user profile, please try creating a new different user ( with the default additional groups for desktop use pressing the up arrow during the adduser run, see also http://docs.slackware.com/slackbook:users ) and check if ~/.config/lxsession/LXDE/autostart is there after starting lxde with this new user.

Jeebizz

09-03-2013 11:16 AM

Quote:

Originally Posted by ponce (Post 5020649)

are you running a Slackware full install?

Yes, it is a full install.

Quote:

Originally Posted by ponce (Post 5020649)

Ok I will try that and see.

Jeebizz

09-03-2013 11:21 AM

So I created a new user, and I don't even have ./config/lxsession , this is all I have:

Code:

bash-4.2$ ls -al .config

total 8

drwxr-xr-x  7 testuser users  40 Sep  3 11:16 .

drwx--x--x 12 testuser users 4096 Sep  3 11:16 ..

drwxr-xr-x  2 testuser users    8 Sep  3 11:16 blueman

drwx------  3 testuser users    8 Sep  3 11:16 lxpanel

drwx------  2 testuser users    8 Sep  3 11:16 lxterminal

drwxr-xr-x  2 testuser users    8 Sep  3 11:16 openbox

drwxr-xr-x  3 testuser users    8 Sep  3 11:16 pcmanfm

bash-4.2$ whoami

testuser

bash-4.2$

ponce

09-03-2013 12:00 PM

with testuser do you have still the firefox flashing?

forget about automatic copying, I think I was remembering from the behaviour of a previous lxpanel version or just doing a little confusion, sorry :)
but still you can copy the /etc/xdg/lxsession directory into ~/.config/ and edit as you like (so it will override the original into /etc): for example you can edit ~/.config/lxsession/LXDE/autostart like this

Code:

#@lxpanel --profile LXDE

@pcmanfm --desktop --profile LXDE

@xscreensaver -no-splash

@xterm

and at the next X start lxde will start without panel but with an open xterm: into this launch the panel with this command

Code:

lxpanel --profile LXDE

this way you will be able to see the output of lxpanel into the xterm.
if you launch firefox from the panel you will see the output from it into the xterm too (as it will be a subprocess of the panel itself): watch for which output you got when you see the panel flashing.

Jeebizz

09-03-2013 01:43 PM

That did not work for me. I copied everything to ~/.config , and edited autostart. startx and xterm came up, but as soon as I typed

Code:

lxpanel --profile LXDE

I got an error:

Code:

bash-4.2$ lxpanel --profile LXDE

There is already an instance of LXPanel.  Now to exit

bash-4.2$

This is my autostart, just like yours:

Code:



#@lxpanel --profile LXDE

@pcmanfm --desktop --profile LXDE

@xscreensaver -no-splash

@xterm

I guess LXDE is still defaulting to the /etc/ directory instead of ~. :scratch: Thats another thing I noticed with LXDE, not really much in ~ , all settings, wallpapers, etc, are in /etc/.

ponce

09-03-2013 02:30 PM

you can also exit the running lxpanel with

Code:

lxpanelctl exit

Jeebizz

09-03-2013 02:48 PM

Oh ok, well I started it, and I noticed again the programs disappeared in my 'testuser' profile. This is the output:

Code:

bash-4.2$ lxpanel --profile LXDE



(lxpanel:3819): Gtk-CRITICAL **: IA__gtk_container_set_border_width: assertion `GTK_IS_CONTAINER (container)' failed



(lxpanel:3819): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_BOX (box)' failed



(lxpanel:3819): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_BOX (box)' failed



(lxpanel:3819): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE



(lxpanel:3819): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE



** (process:3821): WARNING **: removed previous socket file /tmp/.menu-cached-:0-testuser



(lxpanel:3819): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE



(lxpanel:3819): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE



(lxpanel:3819): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE



(lxpanel:3819): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE

I don't know if you can replicate it, but as soon as I launched ksnapshot to take a screencap again, the program listing returned.

ponce

09-03-2013 03:29 PM

no, I cannot replicate it.

Code:

(lxpanel:3819): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_BOX (box)' failed

this is maybe related to the gtk theme

Code:

** (process:3821): WARNING **: removed previous socket file /tmp/.menu-cached-:0-testuser

I think the interesting line (but maybe unrelated to the flashing problem) might be this, so the culprit for the disappearing menu seems menu-cache, but being you the only one reporting this behaviour I tend to believe it's some problem related to your installation.

BTW, I'm testing new packages for slackware64-14.0 ATM, if you feel like to try upgrading them (really dunno if they will solve your problems) they're here (be sure to read README.txt)

http://ponce.cc/slackware/testing/lx...ckware64-14.0/

All times are GMT -5. The time now is 06:44 AM.

Page 1 of 2

Show 50 post(s) from this thread on one page