[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-08-15 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-06-16 Thread Eero Torri
Hello, I'm quite new here, so excuse if this is stupid question but would this https://github.com/torvalds/linux/commit/47c1ffb2b6b630894e9a16442611c056ab21c057 be backported to the 14.04 kernel? Looks like it is the cause of problems with E544 and E554 touchpad -- You received this bug

[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-04-26 Thread bwallum
learning git -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1446732 Title: Fujitsu Lifebook E544 touchpad doesn't work Status in linux package in Ubuntu: Incomplete Bug description:

[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-04-26 Thread bwallum
Kernel 3.19 as shipped with Vivid gave usable functionality to the Fujitsu E544 touchpad but the left touchpad button did not operate as a left click. It did operate as a hold down and move cursor for drag and drop. Kernel 4 (linux-image-4.0.0-04-generic_4.0.0-04.201504121935_amd64)

[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-04-25 Thread bwallum
apologies for delay, busy week, engaged with bugzilla gnucash (gnucash not working in Vivid) but hope to get back to the bisect tomorrow -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-04-21 Thread bwallum
Is thjis what you would like me try?:- linux-headers-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb If so how do I do that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-04-21 Thread bwallum
Upgraded to 15.04 AMD64 using update-manager -d, now stable for me. Happy to report touchpad cursor now works. Right button works. Left button on touchpad does not function Kernel is 3.19.0.15 How do I check for greater detail kernel version number? -- You received this bug notification

[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-04-21 Thread bwallum
OK, found this, (you told me earlier I know, just slapped myself) https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=showredirect=KernelMainlineBuilds -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-04-21 Thread bwallum
Left touchpad button works for drag using press and then move cursor to drag and drop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1446732 Title: Fujitsu Lifebook E544 touchpad

[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-04-21 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0

[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work

2015-04-21 Thread Christopher M. Penalver
bwallum, the next step is to fully commit bisect from kernel 3.19 to 4.0 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following