thanks.
Regarding lightdm itself, do you intend to also release a newer package
for the 1.6 "stable" branch as well ? The current bug is in fact a 1.6
regression there as well (and this is how I noticed it). It's a bit
counter-intuitive that the fix for a regression found in the "stable"
branch is
Hi,
Pardon me if I'm misunderstanding, but it very much seems to me that the
gdm/lightdm configuration scripts are unconditionally setting the
default value of the debconf choice to gdm, irrespective of the previous
value of the setting.
Is that normal behaviour ?
In the transcript below I would
Fine by me.
Thanks all for tidying this up. Nice work.
E.
On Mon, Feb 11, 2013 at 6:41 PM, Dave Turvene wrote:
> I need to work on several projects so will not have time to look at this
> again this week. I rebased our work on Kevin Cernekee's 14-part
> submission to linux-input. His patchset
@Kevin (#305)
> Are you seeing incorrect readings when using MT, or is your comment
just based on the code? It would not be too surprising if > different
initialization sequences altered the data format (ala Dolphin's 8-byte
vs. 9-byte setting).
Just inspecting the packets traveling through. Some
Hi all,
In reply to #302:
> Where did you get the device names ("Dolphin", "Pinnacle", "Mercury",
etc.) and how did you figure out the protocols?
Seconded.
> Can people test Kevin's patch?
I tried it on my dell e6230, it works.
Kevin's patch do not properly take into account the fact that the
You are well right posting a new bug. Bug 606238 was really too crowded.
As far as I am aware, no, there is nothing in the current ubuntu kernel
for having this issue fixed.
I hacked a dklm replacement, building on top of Dave Turvene's and Ben
Gamari's work. Code is here.
git://github.com/emman
In reply to #276-#277.
I was mistaken on this one. Apparently the driver does nothing regarding
enabling or disabling multitouch features on the trackpad. It's only a
matter of the software down the line which interprets the packet data.
Nothing, in fact, recognizes more than two finger in the alp
Cool.
I suspected there was some clutter in there, but not to that point.
I am a bit surprised though that there is no ENABLE command in your
short init sequence. Looks quite odd.
I factored the e6x30 init sequences into a common sequence (tested,
works), and later ambitiously tested a merge of
Sure. Not today, though.
All these features are configurable with the windows touchpad software.
Assuming they map to visible config orders sent to the device upon init,
I can reverse-engineer them and enable them from the driver.
I wonder, though, what is the usual choice done for touchpad hardw
Hi,
I succeeded in reproducing the reverse engineering steps for the Dell
E6230 touchpad.
Here is an updated version of Dave's dkms module which is **ONLY** for
the E6230. Starting from the init sequenced captured via qemu, I have
tried to make some sense out of the commands. It seems that this i
Misbehaviour still present in quantal
I'm using gnome-fallback session. Seems that keybooard settings are
under gsettings now. The magic to get this annoyance fixed is now:
gsettings set org.gnome.desktop.wm.keybindings switch-group
"['disabled']"
(dconf-editor to the same spot works as well)
(
up.
Problem still occurs in quantal, fresh install.
info gcc directs me to the gccgo info page.
E.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778796
Title:
‘info gcc’ broke. The package gcc-do
Public bug reported:
(assigning to lightdm, although it's broader than that. Not clear which
component is to blame exactly).
Let X be a laptop running ubuntu 12.10. It's an x86-64 cpu for that
matter, but no one cares.
Assume an ssh server is running on X, and someone is logged in via ssh
from a
Public bug reported:
By comparing this:
http://packages.ubuntu.com/quantal/all/openmpi-doc/filelist
and that:
http://packages.ubuntu.com/quantal/all/openmpi1.5-doc/filelist
it is pretty obvious that the MPI_* man pages have been dropped from
openmpi1.5-doc
(same deal for precise, for that mat
Just re-tested this one. It's still broken.
/usr/share/info/gcc.info.gz points to gcc-4.6.info.gz (don't know whether that
was the case before), but that is of no use for providing correct `info gcc',
because:
(1) update-info-dir does not look at symlinks.
(2) the info-dir section in gcc-4.6.i
Quite annoying indeed. Still observed in oneiric beta2.
I never installed, nor cared or heard about gccgo, yet I'm served with
the gccgo info page in lieu of the gcc one.
I'll go for manual removing of /usr/share/info/gccgo.info.gz and redo
update-info-dir in the meantime.
Is the comment to be t
It's not really a fix. Merely a paper wrap.
The bug seems to reside elsewhere, and might possibly affect other apps.
IMO it's important to do more work. I will not personally have time to
devote to this, however (despite the fact that I can reproduce the bug).
--
You received this bug notificati
There still seems to be something quite fishy going on with XRecord and
async events. I don't know much of it underneath, so my understanding
might be quite bad. Here are some random thoughts.
The problem is that there is an event queue which fills up and is never
drained by the application. Here,
No it's not, unfortunately. The current xcb_io.c matches the one in the
git repository, which has the relevant patch applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/754470
Title:
syndaemon co
This bug annoys me greatly.
Tried your package as well. It remains silent. No debug output at all.
I don't know which changes you tried, but I've tried putting some
printf() hooks within xrecord_callback(), e.g.:
cbres = (struct xrecord_callback_results *)closure;
int check = recorded_d
20 matches
Mail list logo
