I wrote a patch for the put plugin that fixes bounce behavior. Not sure
if it fixes all behavior described in this issue.
See https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1886106
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
This bug is mentioned as a part of
https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-
main/+bug/877443
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886106
Title:
Compiz put plugin window bo
Public bug reported:
If you use the Compiz 'grid' plugin to position a window, then change
the viewport of that window with the Compiz 'put' plugin, the window
moves briefly to the new viewport but then immediately bounces back to
the old viewport.
A workaround is to restore the window before put
This is probably an issue with Put rather than grid, as it also affects
maximized windows:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1316651
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/87
Same problem. Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877443
Title:
Grid plugin incompatible with Put plugin
To manage notifications about this bug go to:
https://bugs.launchpad.
Just to note, this is related to #877443
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316651
Title:
Compiz' Put plugin makes random mistakes in moving maximize windows
between displays
To manag
This bug has plagued me for years. In addition to when the window is
maximized, a window will bounce back if the window was previously placed
by the Compiz Grid plugin. The workaround is to restore the window
before putting it to the next output. However, this is obnoxious. I
can't believe this bug
@Christopher,
Using the following information:
INPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN) DRIVERS
M: Dmitry Torokhov
M: Dmitry Torokhov
L: linux-in...@vger.kernel.org
Q: http://patchwork.kernel.org/project/linux-input/list/
T: git git://git.kernel.org/pub/scm/linux/ke
Christopher,
Thank you for timely response. The best practice you refer to in comment #48
seems to apply to "regression"s. I don't know precisely what "regression"
refers to in this context, but I assumed it meant something along the "a bug
that was introduced after not existing in a previous co
In comment #43, I mentioned that I filed another report (this time to
linux-input). Actually, I just discovered that I had filed a similar report
over a year ago to linux-input. For whatever reason, the old report did not
come up when I searched (which is why I filed the new one),, but was liste
The keycode for the key to the right of the alt key reported by showkey
in kernel 3.17.0-031700rc7-generic is 580.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
045e:0745 [HP TouchSma
Note that one of the keys I reported as not working actually works in
this latest kernel version (3.17.0-031700rc7-generic):. the key to the
right of the right-alt key. Its keycode is 135. Unfortunately, I could
not deduce its role, since I was unable to run any commands
(specifically xev) using a
CORRECTION: the keycode is not 135; that was the key next to it, which
already worked. However, II did find a keycode using the latest kernel.
I will update shortly with the actual keycode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I've sent another report using the contemporary latest upstream kernel:
3.17.0-031700rc7-generic
The report can be found at:
http://www.spinics.net/lists/linux-input/msg33746.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
This bug persists for me in Ubuntu 13.04 with:
unity-greeter: 13.10.3-0ubuntu1
nvidia-319: 319.32-0ubuntu7
I have the Nvidia GTX 295. I also use an SSD like Sapsan, though I don't know
if that is relevant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
The bug still exists in the latest kernel (3.13.0-031300rc3-generic)
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Tags removed: kernel-bug-exists-upstream-v3.11.rc4 kernel-request-3.11.0-7.14
** Tags added: kernel-bug-exists-upstream-v3.13.0-031300rc3-generic
--
You rece
Three things:
1.
That was a typo in comment #36.
I meant to say, "I reposted in linux-input," not, "I reposted in linux-usb."
2.
Per your comment (#38), I have provided below a link to my post in linux-input:
http://www.spinics.net/lists/linux-input/msg27617.html
3.
I will test shortly using the
I tried installing linux version 3.11.0-8 over my precise installation
from the Ubuntu package repositories website. Unfortunately, neither the
keyboard nor mouse responded at all when booting with this verison. I
suppose I could try a true Saucy environment, but I'm not sure exactly
how to use thi
@Christopher per your comment on 2013-08-22:
http://www.spinics.net/lists/linux-input/maillist.html
I originally posted to linux-...@vger.kernel.org, but the response I
received was "Care to explain how this is a usb issue." I was busy with
school and work, and just reposted to linux-...@vger.kern
@Joseph I don't see how to retrieve this kernel version. There isn't an
exact match on at the upstream kernel list Christopher posted above.
There is no linux-image-generic-lts-saucy package available for precise
(I assume this would be 3.11). Is there an alternate version I should
test? Or do I ha
I haven't received any acknowledgment from the kernel team that my
report was received. Is it typical not to receive any response for this
long? I understand that there is nothing for the Ubuntu team to do until
the bug is fixed upstream, but I would like to verify that I've done all
I can on my en
I've submitted the upstream report to the appropriate team. I cc'ed this
bug, but it does not appear to have updated here. Let me know if there
is anything else to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
The results are more or less the same for kernel 3.11.0-031100rc4-generic which
I downloaded from the link you provided.
The only difference is that findkeyboards lists event12 and event14 instead of
event3 and event5 as before (and js0 still appears). The behavior is identical.
The bug persists
None of the troubleshooting steps yielded any response when these buttons were
pressed.
There are three input devices that show up with findkeyboards:
input/event3
input/event5
input/js0
All of the regular keyboard buttons yield a response when I use keymap on
event3. The buttons I am interested
The problem occurs in Saucy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
045e:0745 [HP TouchSmart tm2t-2200] No scancode for several keys of
Microsoft Comfort Desktop 5000
To man
I'm currently downloading it.. do you need the output of lsusb -v as
well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
045e:0745 [HP TouchSmart tm2t-2200] No scancode for several ke
Here is the output AFTER connecting the device.
** Attachment added: "lsusb-v-after.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1168224/+attachment/3759561/+files/lsusb-v-after.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Here is the output BEFORE connecting the device.
** Attachment added: "lsusb-v-before.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1168224/+attachment/3759560/+files/lsusb-v-before.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I tested it with Ubuntu Lucid 10.04.4 Desktop, kernel version 2.6.32-38-generic
The problem occurs in this version as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
[HP TouchSmar
I am having trouble parsing your question. Do you mean "did this problem occur
in a release prior to Precise?" I have no idea. I have only tested this on
Precise.
The keyboard is relatively new (2012ish), so I believe Precise was the
contemporary Ubuntu version during its release. What are the n
The bug persists in the latest upstream kernel.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.11.0-031100rc3-generic
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Let's debug with the laptop to avoid duplicating work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
[HP TouchSmart tm2t-2200] No scancode for several keys of Microsoft
Comfort Desk
(the laptop is the touchsmart)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
[HP TouchSmart tm2t-2200] No scancode for several keys of Microsoft
Comfort Desktop 5000
To manage noti
The information for the computer I WAS using is:
Product: XQ322AV
Model: tm2t-2200
However, this problem persists with my current computer, which was built
from parts. I have not tried with the upstream kernel for this computer,
but I have no reason to believe this bug was fixed. Let me know if yo
I tested with kernel version 3.9.0-030900rc6-generic, and the bug still
exists.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
I wanted to map the key directly to the right of the right ALT key to be
a metakey, but I discovered that this key raises no events whatsoever,
neither via dmesg, xev, nor showkey. I don't even know what to call this
key, and searching the internet did not help. Also, the keys
I should note that it MAY be nvidia related, since it does not happen
when I use the open-source nouveau drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874218
Title:
LightDM restarts after f
I have the exact same problem as the original poster. I am using Ubuntu
12.04 with nvidia proprietary binary drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874218
Title:
LightDM restarts aft
38 matches
Mail list logo
