You are not logged in.
Hallo !
I had never have to have a look into details after I setup XFCE4. This time, many things look
bad, at least, I do not understand them - probably a crash of the settings daemon may be
the cause.
I installed debian jessie from a chroot environment, because I need ZFS on root. Some
small things went bad, which were probably corrected. At least, before installing XFCE4
I do'nt recognize strange problems.
I just saying, I am using XFCE4 over XRDP, because my box is outside and I have to
have unique access to all of them. This might be a reason too, but I have never seen
such behavior before.
The most ugly thing might be this:
grid kernel: xfsettingsd[2088]: segfault at 20 ip 00007fa29e33f6b7 sp 00007fff8d8a0b90 error 4 in libxfce4kbd-private-2.so.0.0.0[7fa29e33a000+9000]
The other things are:
- scrollbar: missing small icons on top and bottom end of the scrollbar leads to ugly behavior in long
documents/synaptic/wirshark bufferlists
- cannot change location of notifications display
- some (a lot of) keyboard shortcuts do not work; some, related to desktop, switches TABs in the current app
- one workspace is missing (4 visible in panel, config shows 5)
- cannot keep one window on all desktops, the check is set, but doesnt work;
so, what is "the visible workspace", where a window can always be placed?
- the output of xmodemap is completely different from all examples
I saw, it contains only one name after the equel sign
- all icons missing in thunar [have had another question about this already]
These might be related to the daemon crash - I am just no expert on this.
Any help would be great - I'll just understand where to start and I could shwo logs.
Thanks anyway,
Manfred
uname-a:
Linux grid 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64 GNU/Linux
lsb_release -a:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.3 (jessie)
Release: 8.3
Codename: jessie
XFCE4.10
mobo:
SuperMicro A1SAM-2750F with Aspeed AST 2400 VGA Controller
Offline
This sounds like the old xfsettingsd/vnc bug that existed in Xfce 4.10 when connecting over vnc. The symptoms you list are all indicative of a non-functional xfsettingsd daemon. To confirm, check to see if xfsettingsd is running:
ps -ef | grep xfsettingsd
...and if not, try manually starting it:
xfsettingsd
If you get a message about a missing XI protocol, then this is the bug. It was fixed post 4.10.
As a workaround, aside from upgrading to 4.12, some people had success running xfsettingsd with the --sync option:
xfsettingsd --sync
I recall with 4.10 having to install xrdp on the system and connect using rdesktop (sesman session) to get Xfce to work properly.
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
Hi !
Many thanks for your investigation. This starts to help me, to make my own homeworks ...
If I am running xcfe via startx at the console, there is a warning about gtk, 'cannot open display'
but everything else, even shortcuts etc. is ok and the daemon is running.
If I login via xrdp, using 'sesman-Xvnc' the drama takes it's route ...
I am seeing, the daemon is not running and I tried to start it manually,
but, anyway, if I start it without params or with your mention of '--sync', I get:
(xfsettingsd:29563): xfsettingsd-CRITICAL **: RANDR extension is too old, version 1.1. Display settings won't be applied.
Xlib: extension "XInputExtension" missing on display ":10.0".
(xfsettingsd:29563): xfsettingsd-CRITICAL **: XI is not present.
(xfsettingsd:29563): xfsettingsd-CRITICAL **: Failed to initialize the Xkb extension.
(xfsettingsd:29563): xfsettingsd-CRITICAL **: Failed to initialize the Accessibility extension.
the terminal then hungs here and, using another one, 'ps' does not see the daemon running.
Probably, you'll have a hint?
Much thanks anyway,
Manfred
Offline
If I am running xcfe via startx at the console, there is a warning about gtk, 'cannot open display'
but everything else, even shortcuts etc. is ok and the daemon is running.
What is the contents of your ~/.xinitrc file?
If I login via xrdp
Exactly how are you doing this? What program and parameters are you using to connect?
I am seeing, the daemon is not running and I tried to start it manually,
but, anyway, if I start it without params or with your mention of '--sync', I get:(xfsettingsd:29563): xfsettingsd-CRITICAL **: RANDR extension is too old, version 1.1. Display settings won't be applied.
Xlib: extension "XInputExtension" missing on display ":10.0".
(xfsettingsd:29563): xfsettingsd-CRITICAL **: XI is not present.
(xfsettingsd:29563): xfsettingsd-CRITICAL **: Failed to initialize the Xkb extension.
(xfsettingsd:29563): xfsettingsd-CRITICAL **: Failed to initialize the Accessibility extension.the terminal then hungs here and, using another one, 'ps' does not see the daemon running.
xfsettingsd is crashing and causing the effects that you are seeing. This was a known bug in Xfce 4.10.
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 believe this was the bug report and this the commit that fixed it. This patch was included in xfce4-settings version 4.11.0.
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
mabra wrote:If I am running xcfe via startx at the console, there is a warning about gtk, 'cannot open display'
but everything else, even shortcuts etc. is ok and the daemon is running.What is the contents of your ~/.xinitrc file?
NONE of my users have such a file.
If I login via xrdp
Exactly how are you doing this? What program and parameters are you using to connect?
1 - I am using "Royal-TS from Windows", does it usually
starts displaying a login-dialog, where I specify (Module) "Sesman-Xvnc" and type user/pass
2 - (ubunut) rdesktop -a 16 -4 grid -u root -p -The result for this ways is the same - the daemon is not present.
I am seeing, the daemon is not running and I tried to start it manually,
but, anyway, if I start it without params or with your mention of '--sync', I get:(xfsettingsd:29563): xfsettingsd-CRITICAL **: RANDR extension is too old, version 1.1. Display settings won't be applied.
Xlib: extension "XInputExtension" missing on display ":10.0".
(xfsettingsd:29563): xfsettingsd-CRITICAL **: XI is not present.
(xfsettingsd:29563): xfsettingsd-CRITICAL **: Failed to initialize the Xkb extension.
(xfsettingsd:29563): xfsettingsd-CRITICAL **: Failed to initialize the Accessibility extension.the terminal then hungs here and, using another one, 'ps' does not see the daemon running.
xfsettingsd is crashing and causing the effects that you are seeing. This was a known bug in Xfce 4.10.
Offline
Looks like you need to be running xfce4-settings version 4.11.0 or above to get vnc/rdp to work with Xfce. Unfortunately, Debian Jessie only comes with 4.10.
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
As an alternative, you can use XDMCP and it seems to work fine. xfsettingsd doesn't crash in this scenario.
To set up the server, make sure you are running a compatible display manager (e.g. lightdm) and configure it allow xdmcp. Also open the firewall to ports 177 and 6000:6005/tcp.
On the client, you'll need to have a local X server app running on Windows, or Xephyr on linux. Also open up the same ports through the firewall and with linux, connect via:
Xephyr -query 192.168.1.254 -screen 1200x700 -br -reset -terminate :1
...adjust parameters to suit.
One downside though is that you can't re-connect to existing sessions using XDMCP.
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
Hi !
Thanks for the hints and pointers.
Sorry to say that an alternative to use XRDP would destroy my usual environment and I do not have an Xserver for windows.
Anyway, with a lucky moment, I remembered apt-pinning.
**NOTE - DO NOT FOLLOW MY NOOB(Y) INSTRUCTIONS **
Add debian 'testing' to your repository. Use apt-pinning to force stabil to be the default.
>apt-get install -t testing xfce4
will bring you xfce 4.12 to your box.
Now, the settings daemon is running and some shortcuts work, and Thunar has icons.
This was the main problem. More on the new minir errors after some hours of sleep ;-)
Regards,
Manfred
Offline
[ Generated in 0.009 seconds, 8 queries executed - Memory usage: 585.57 KiB (Peak: 602.41 KiB) ]