You are not logged in.
Pages: 1
I'm not sure exactly when this problem began, but I've noticed it happens quite frequently as of late.
For ref:
Arch 4.6.4-1
xfdesktop 4.12.3-2
xfwm4 4.12.3-2
xfce4-panel 4.12.0-2
firefox 47.0.1-1
Panel settings are to always show panel and no hiding.
Regardless of the number of FF windows opened, at some point with frequent tab switching or reloading the panel will disappear. I will restart the panel but receive a warning about the panel being in "Kiosk Mode".
There are no indications of errors in dmesg.
Last entry in .xfce4-session.verbose-log
TRACE[sm-layer.c:213] sm_register_client(): ICE connection fd = 16, received REGISTER CLIENT [Previous Id = None]
TRACE[xfsm-properties.c:489] xfsm_properties_set_string(): -> Set string (Program, xfce4-terminal)
TRACE[xfsm-properties.c:489] xfsm_properties_set_string(): -> Set string (UserID, myusername)
TRACE[xfsm-properties.c:555] xfsm_properties_set_uchar(): -> Set uchar (RestartStyleHint, 0)
TRACE[xfsm-properties.c:489] xfsm_properties_set_string(): -> Set string (ProcessID, 1632)
TRACE[xfsm-properties.c:489] xfsm_properties_set_string(): -> Set string (CurrentDirectory, /home/myusername)
TRACE[xfsm-properties.c:555] xfsm_properties_set_uchar(): -> Set uchar (_GSM_Priority, 50)
TRACE[xfsm-properties.c:489] xfsm_properties_set_string(): -> Set string (_GSM_DesktopFile, /usr/share/applications/xfce4-terminal.desktop)
TRACE[xfsm-properties.c:629] xfsm_properties_set_from_smprop(): -> Set strv (CloneCommand)
TRACE[sm-layer.c:304] sm_save_yourself_done(): Client Id = 280fcc8e2-b6df-4613-86b9-b9f655fd8438, received SAVE YOURSELF DONE [Success = True]
Why is panel going into kiosk mode?
What else can be done to diagnose this problem.
Offline
Hello and welcome.
Assuming you have the Window Buttons plugin enabled, it looks similar to https://bbs.archlinux.org/viewtopic.php?id=169075. Adding ttf-droid and/or ttf-dejavu fonts will help if it is.
The other thing you can do to troubleshoot is run xfce4-panel in debug mode. First quit xfce4-panel:
xfce4-panel -q
...then run it in debug mode in a terminal window:
PANEL_DEBUG=1 xfce4-panel
When the crash happens, look to see what is printed in the terminal window.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
ToZ,
I'll try this suggestion and report back details.
Thanks for the feedback.
PANEL_DEBUG=1 xfce4-panel >~/panel.log 2>&1
because scroll back may disappear...
Last edited by digifuzzy (2016-07-29 18:36:06)
Offline
Funny, a day or so of doing this and I'm not seeing the same symptoms.
A few thoughts:
1) killing the panel made the re-occurring symptoms disappear?
2) putting the panel into debug mode causing different results?
3) starting the panel from the command line, not w/ session startup changing environment?
The only thing of note in logging debug output is a handful of lines like...
xfce4-panel(application): saving /panels/panel-1: ids=false, providers=true
These were reported fairly early on during panel usage.
Panel is still present on desktop and working as expected.
Offline
reactivate the post
the same thing happens here
bash-4.3$ The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 230 error_code 3 request_code 10 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 138 error_code 3 request_code 18 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
bash-4.3$ xfce4-panel
xfce4-panel: cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed.
Aborted
Offline
its a gtk-murrine thing, some turn around?
Offline
@specialized, I think you are experiencing this issue. I'm not sure if the fix is to install the ttf-droid package or the fact that at the end of the package install the font cache is rebuilt. Perhaps you can give that a try.
There are a number of bug reports referenced in that link,
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
i've installed the droid fonts and its the same ,i have to change the theme , one without murrine, and works
i found this workaround with a murrine theme.
just comment out the engine "murrine" {} blocks inside gtk-2.0/apps/xfce-panel.rc
Last edited by specialized (2017-08-10 22:44:15)
Offline
Pages: 1
[ Generated in 0.010 seconds, 7 queries executed - Memory usage: 547.56 KiB (Peak: 548.41 KiB) ]