Package: lxpanel Version: 0.7.0-1 Severity: normal Dear maintainer,
The taskbar part of lxpanel works as intended when clicking the program fields (to switch between them), but LXPanel crahe when clicking in the empty pace on the right of the last open program field (left of the clock etc.). In this case, LXPanel gets restarted about a half second later and is fully usable again, the only notable effect (until now) is the half-second-invisibility. This can repeated infinitely, it crashes/restarts with every click in the empty space. If pkill'ed and started out of XTerm manually, the only output at click time is "Speicherzugriffsfehler", the usual german translation of segmentation fault (not quite an accurate translation, but common). Setting the log level parameter changes nothing. (It won't restart again in this case, started from XTerm) The current Testing-build works well. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lxpanel depends on: ii libasound2 1.0.28-1 ii libatk1.0-0 2.12.0-1 ii libc6 2.19-10 ii libcairo2 1.12.16-3 ii libfm-gtk4 1.2.1-1 ii libfm-modules 1.2.1-1 ii libfm4 1.2.1-1 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-1.1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-4 ii libgtk2.0-0 2.24.24-1 ii libiw30 30~pre9-8 ii libmenu-cache3 0.6.1-1 ii libpango-1.0-0 1.36.6-1 ii libpangocairo-1.0-0 1.36.6-1 ii libpangoft2-1.0-0 1.36.6-1 ii libwnck22 2.30.7-1 ii libx11-6 2:1.6.2-3 ii libxml2 2.9.1+dfsg1-4 ii lxmenu-data 0.1.2-2 ii lxpanel-data 0.7.0-1 Versions of packages lxpanel recommends: ii xkb-data 2.12-1 Versions of packages lxpanel suggests: ii iceweasel [www-browser] 31.0-3 ii lxsession 0.4.9.2-1 ii menu 2.1.47 -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
