[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#679786: e16: Root-window menus don't work, on first virtual desktop only

Package: e16
Version: 1.0.0-4
Severity: important

Dear Maintainer,

In E16, clicking on the root window normally brings up one of three
menus, depending on whether it was a left-, middle-, or right-click.
To the best of my awareness, this is the primary means of launching
applications in that window manager.

In my current configuration, on the first virtual desktop (as defined
by the 'desktops.num' setting in the e16 config file), clicking on
the root window does nothing. However, in the second - and, to the
limits of my testing thus far, any subsequent - virtual desktop,
clicking on the root window brings up menus as normal.

This behavior means that anyone running E16 with only one virtual
desktop has no way to launch applications in X, unless they either have
launch shortcuts configured in the E16 keybindings or go through the
trouble of switching to console, launching eesh with an appropriate
DISPLAY setting, and running an 'exec' command.

I have reproduced this problem in multiple versions of E16, including
1.0.0-3.1 and a self-compiled version of 1.0.10 (which has never been
packaged by Debian). I have not thus far been able to find a copy of the
.deb for 1.0.0-3, or any previous version which would not be
incompatible with the system changes made in -3.1, so I have not been
able to test it in versions before that point.

This behavior occurs even in the default configuration generated by
removing ~/.e16/ and re-launching X (to re-initialize E16).

I suspect that this is a bug being triggered by some change elsewhere in
the system, rather than in E16 itself, but I cannot be completely
certain of that.

This problem first manifested after a forced reboot due to a power
outage. During the uptime prior to that reboot, I had dist-upgrade'd a
relatively wide selection of packages. I am fairly certain that e16 was
held and thus should not have been one of them, but I am also fairly
certain that I had previously been running 1.0.0-3, not 1.0.0-4.

I would like to try to identify exactly where in the system
configuration this problem is being triggered, and how to fix it.
However, due to the lack of logs or console output from E16, I have
nothing to go on. Where should I be looking to diagnose this?

-- System Information:
Debian Release: wheezy/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages e16 depends on:
ii  e16-data        1.0.0-4
ii  libaudiofile0   0.2.7-0.1
ii  libc6           2.13-33
ii  libdbus-1-3     1.6.0-1
ii  libesd0         0.2.41-8
ii  libglib2.0-0    2.32.3-1
ii  libice6         2:1.0.8-2
ii  libimlib2       1.4.5-1
ii  libpango1.0-0   1.30.0-1
ii  libsm6          2:1.2.1-2
ii  libx11-6        2:1.5.0-1
ii  libxcomposite1  1:0.4.3-2
ii  libxdamage1     1:1.1.3-2
ii  libxext6        2:1.3.1-2
ii  libxfixes3      1:5.0-4
ii  libxft2         2.3.1-1
ii  libxinerama1    2:1.1.2-1
ii  libxrandr2      2:1.3.2-2
ii  libxrender1     1:0.9.7-1
ii  libxxf86vm1     1:1.1.2-1

Versions of packages e16 recommends:
pn  esound  <none>
ii  menu    2.1.46

Versions of packages e16 suggests:
pn  e16keyedit                   <none>
pn  e16menuedit2                 <none>
ii  kterm [x-terminal-emulator]  6.2.0-46
ii  xterm [x-terminal-emulator]  278-1

-- no debconf information

Reply to: