[Bug 44277] Re: nothing on ctrl alt F# (Dapper)

2006-07-01 Thread 89c51
everything OK now the problem was related to the nvidia driver (not being able to show 640x400 resolution on screen) solved by adding vga=... on my kernel line on menu.lst -- nothing on ctrl alt F# (Dapper) https://launchpad.net/bugs/44277 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.c

[Bug 532633] Re: [Master] Window Control buttons: position/order/alignment

2010-04-03 Thread 89c51
someday the ubuntu people (Mark and the design team mostly) must understand that innovation is not copying the Mac themes and styles especially in a way that makes the copy look cheap FFS stop using ubuntu and go buy yourself a shiny new Mac people if thats what you always wanted so far people us

[Bug 958174] Re: Wireless Mouse not registered on Startup or Reboot

2012-06-27 Thread 89c51
I am not on ubuntu but this seems to be a general problem with 3.2+ kernels (its the kernel where hid_logitech_dj module was introduced) There is a bug in the kernel bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=43631 and the hid_logitech_dj module author has been notified and is aware of t

[Bug 958174] Re: Wireless Mouse not registered on Startup or Reboot

2012-06-28 Thread 89c51
If anyone could boot their system with hid.debug=1 log_buf_len=2097152 as a parameter and log dmesg messages when this happens and when it doesn't would be helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad

[Bug 958174] Re: Wireless Mouse not registered on Startup or Reboot

2012-06-30 Thread 89c51
An update from the author of the hid_logitech_module i got this morning: "A quick update: We are able to reproduce the issue on our side. After plugging/unplugging several times, I am able to get the same behaviour you observe. This is good. We are missing one notification from the Unifying rec

[Bug 958174] Re: Wireless Mouse not registered on Startup or Reboot

2012-07-04 Thread 89c51
Ok. This is an update from the author of the hid_logitech_dj module: "We've found the root cause and we have a patch that we would like you to try. The culprit is a modification introduced by commit 4ea5454203d991ec that added a new semaphore to each hid_device. This commit came after the hid_log