Feedback on the Lenovo ThinkPad X250 - Wolverine2

Asked by Jont Allen

I bought a new X250 from Lenovo and installed ubuntu 15.04. Everything worked,
except
the mouse button.
1 out of 10 times, when I click the mouse, say to select some text, when I let go of the button, it "doesn't let go"
It stays selected.
To unselect I must return to the place on the screen where I clicked on the mouse, and then click a second time, and
it unselelects.

I believed this was a hardware issue since a USB external mouse did not have this problem.

I sent the computer back 3 times to lenovo (Memphis TN) for repair. Each time it came back and the problem continued.

The last time they reinstalled Windows 8. WHen I boot into Win8, I do not see the problem. But when I boot into 15.04,
I do see the problem.

This then seems to be a problem with the software drivers in 15.04, for the Lenovo X250.

When I use a USB mouse with 15.04, I see no problem.

I received the computer on Aug 3, 2015, and now it is Oct 6. Thus two mons later this issue is still alive.
Three times returned, still not fixed.

Is anyone else having this problem?

Jont Allen
<email address hidden>

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu-Certification Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Po-Hsu Lin (cypressyew) said :
#1

Po-Hsu Lin suggests this article as an answer to your question:
FAQ #2193: “XXXX is broken, I need to file a bug”.

Revision history for this message
Po-Hsu Lin (cypressyew) said :
#2

Hi, from your description, I think there is a bug to the touchpad driver (kernel), you can try it with the long-term-supported 14.04, if the problem still exist, please open a bug for it with `ubuntu-bug linux` command in a terminal, this will be helpful to get it fixed.
Thanks!

https://wiki.ubuntu.com/DebuggingTouchpadDetection

Revision history for this message
Jont Allen (jontalle) said :
#3

First, I was unable to login using my old login/password, so it was necessary to change it. I am the same "Jont Allen."

There are several new updates to my posting of Oct 7, 2015:

I have established that the problem with the mouse must be a software driver issue, as suggested above. The fact that the mouse worked with the USB mouse, was not an adequate test.

At this point I need to know how to redefine the mouse driver. I believe that the default driver has been incorrectly specified.
However I could be wrong, as I dont really understand these fine details about mouse drivers. I'm suspecting I need to
install the synaptic mouse driver.
Here are some things I have tried:
xsetpointer -l | grep Pointer
2: "Virtual core pointer" [XPointer]
4: "Virtual core XTEST pointer" [XExtensionPointer]
11: "TPPS/2 IBM TrackPoint" [XExtensionPointer]

xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Sleep Button id=8 [slave keyboard (3)]
    ↳ Integrated Camera id=9 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
    ↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)]

Some other URLs with possibly related information include:
https://mydevelopedworld.wordpress.com/2013/11/30/how-to-configure-new-lenovo-x240-touchpad-on-ubuntu-13-10/
http://blog.gabrielsaldana.org/debian-on-lenovo-thinkpad-x240/

Config file information is:
/usr/share/X11/xorg.conf.d$ ls
10-evdev.conf 11-evdev-trackpoint.conf 50-wacom.conf
10-quirks.conf 50-synaptics.conf 51-synaptics-quirks.conf
11-evdev-quirks.conf 50-vmmouse.conf 90-evdev.conf

This is about as far as I have gotten on this problem.

Revision history for this message
Po-Hsu Lin (cypressyew) said :
#4

Hello Jont,
for the bug that you linked here, it belongs to an extra package called timekpr, I don't think it related unless you do have this package installed.

And for the touchpad issue, from your xinput log, I think it's not detected at all.
(The TPPS/2 IBM TrackPoint looks like the small red dot track point)

I found a bug for clickpads on X250, but it's already been fixed:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1430846
So I think a new bug report could be helpful.

If you're interested in the driver stuff, please follow the wiki page here to fetch the kernel:
https://wiki.ubuntu.com/Kernel/Dev/KernelGitGuide

Revision history for this message
Jont Allen (jontalle) said :
#5

Dear Po-Hsu,

Because the X250 is not useable, due to the bug, I am still using my
X220i for daily work.
The X220i works fine, but the X250 does not. This makes it difficult for
me to work on the X250
when posting the bug report, I must switch back and forth between the
two computers. It gets a bit
confusing.

I will post a new bug as you suggested, from the X250, with the proper
driver information,
but I cannot do that until I have a clear indication of the exact nature
of the bug.

Preliminary Analysis:
X250
Based on some preliminary investigations, I established yesterday that
the X250 TPP/2 is using
Phys=synaptics-pt/serio0/input0.
  I established this with the command
  cat proc/bus/input/devices
Here I see that the "TPPS/2 IBM TrackPoint" is connected to "mouse1 and
event15"

X220i
  On my working X220i TPPS is connected to
"mouse0 event 4" and Phys=isa0060/serio1/input0

X250 analysis:
Next I used the command on the X250
  evtest /dev/input/event15 | grep EV_KEY

Then I can see the bug show up as follows:
I click on button 1 (left) over and over. When I push the button down,
I see it register as 1,
and when I let go of the key, it registers as a 0.
The bug is that every now and then (once every 20 clicks), when I let go
of the mouse button
(BIN_LEFT), it does not go back to state 0 (it stays in state 1).

X220 analysis:
On the working X220 with the same command I see
# evtest /dev/input/event4 | grep EV_KEY
   Event type 1 (EV_KEY)
Event: time 1444986134.240133, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1444986134.388961, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1444986134.883831, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1444986135.022029, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

In the X220 (working) case there are no button-click (BTN_LEFT) errors.

SUMMARY:
Thus I believe I have isolated the exact problem to the BTN_LEFT and to
the driver
Phys=synaptics-pt/serio0/input0.

Is there anything I have left off, that would help to diagnose this problem?

Jont

more below:

On 10/15/2015 10:32 PM, Po-Hsu Lin wrote:
> Question #272142 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/272142
>
> Po-Hsu Lin posted a new comment:
> Hello Jont,
> for the bug that you linked here, it belongs to an extra package called timekpr, I don't think it related unless you do have this package installed.
I am not totally following this. I dont know anything about "timekpr"
This seems unrelated, as you suggest.
> And for the touchpad issue, from your xinput log, I think it's not detected at all.
> (The TPPS/2 IBM TrackPoint looks like the small red dot track point)
Perhaps I was reporting what the x220i gives, rather than the X250. Very
confusing, and hopefully
clarified in my above detailed report.
> I found a bug for clickpads on X250, but it's already been fixed:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1430846
> So I think a new bug report could be helpful.
 From reading this bug, it looks related to mine. Are you saying that I
need to get a new
kernel or kernel patch, to verify that its fixed? This may start to push
my ability, but I'll
do what ever is necessary, to fix the problem.
> If you're interested in the driver stuff, please follow the wiki page here to fetch the kernel:
> https://wiki.ubuntu.com/Kernel/Dev/KernelGitGuide
Can you please hold my had a bit further here?
1) how do I verify that I'm following a path to the solution, that will
fix the problem?
2) What exactly will I need to do, to fix it, assuming that the kernel
patch solves the problem?

At this point, I'm not sure what to do next. I dont want to randomly try
things, and really screw
up the X250. I have a lot of time invested in setting this system up,
and I dont want to start over.

Jont
>

Revision history for this message
Jont Allen (jontalle) said :
#6

I have submitted an official bug report, as you suggested I do.

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1506817

Jont

On 10/16/2015 04:51 AM, Po-Hsu Lin wrote:
> Question #272142 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/272142
>
> Removed link to bug: #272142
> https://bugs.launchpad.net/bugs/272142
> "Keeps last selected user config, and doesn't clear when selecting next user"
>

Revision history for this message
Po-Hsu Lin (cypressyew) said :
#7

OK, some quick replies and questions here:

1. I will unlink the bug here.
2. Does your trackpoint movement work? (the small red dot, in the middle of your keyboard)
3. How about the corresponding buttons to the trackpoint (the three physical buttons)? From your test result, it looks like the LEFT button won't go back to state 0 after you release it
4. Does your clickpad movement work? (I guess not, as it looks like it's not detected in the xinput)
5. Does your clickpad buttons (the lower left / right part of your clickpad) work?
6. You can cross compare the "xinput list" command output on X220i and X250, you may find that on X220i, there is a trackpoint and a touchpad. But there is only a trackpoint in X250
7. The bug that I linked here, you can try to see if it's fixed by applying updates on your X250, from its "Fix-released" state, it looks like it's already landed in Ubuntu kernel (sudo apt-get update; sudo apt-get dist-upgrade).

I think you will be able to open a well-written bug report with these information.
(Just open a bug with "Bug description", "Step to reproduce", "Expected behaviour", "Actual behaviour" and extra debugging information like your evtest result or something else mentioned in DebuggingTouchpadDetection wiki page in the content)

The kernel tweaking stuff is the last step when the update does not solve your problem, and you still want to fix it by yourself.
What you need to do is to fetch the patch mentioned in that bug, and build a kernel base on that.

Good luck.

Revision history for this message
Jont Allen (jontalle) said :
#8

my answers below

On 10/16/2015 05:27 AM, Po-Hsu Lin wrote:
> Question #272142 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/272142
>
> Po-Hsu Lin posted a new comment:
> OK, some quick replies and questions here:
>
> 1. I will unlink the bug here.
> 2. Does your trackpoint movement work? (the small red dot, in the middle of your keyboard)
yes, 100% ok as best I know
> 3. How about the corresponding buttons to the trackpoint (the three physical buttons)? From your test result, it looks like the LEFT button won't go back to state 0 after you release it
I believe the same problem exists with the other two buttons, but I dont
use them as much. If you wish, I can verify that they are
also broken. Let me know, and I will do that.
> 4. Does your clickpad movement work? (I guess not, as it looks like it's not detected in the xinput)
What is a "clickpad movement"
Dont be confused with my X220 data and my X250 data. You may be looking
at the X220i xinput data.
I cannot use the X250 for email due to this bug, so I used the X220i for
daily work and email.
Here is the xinput output for the X220i (the working computer). This is
very different from the X250.
xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave
pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave
pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
     ↳ Virtual core XTEST keyboard id=5 [slave
keyboard (3)]
     ↳ Power Button id=6 [slave
keyboard (3)]
     ↳ Video Bus id=7 [slave
keyboard (3)]
     ↳ Sleep Button id=8 [slave
keyboard (3)]
     ↳ Integrated Camera id=9 [slave
keyboard (3)]
     ↳ AT Translated Set 2 keyboard id=10 [slave
keyboard (3)]
     ↳ ThinkPad Extra Buttons id=12 [slave
keyboard (3)]

> 5. Does your clickpad buttons (the lower left / right part of your clickpad) work?
everything works, except the left button stays on (=1) after I click it
(fails to release =0), randomly.
> 6. You can cross compare the "xinput list" command output on X220i and X250, you may find that on X220i, there is a trackpoint and a touchpad. But there is only a trackpoint in X250
I dont have an easy way to extract the "xinput list" from the X250 to
the X220i, from which I can send email.
I can tell you that the command 'xinput -list' on the X250 reports
  TPPS/2 id=13
  SynPS/2 Synaptics touchPad id=11,
  ThinkPad Extra Buttons id=12
> 7. The bug that I linked here, you can try to see if it's fixed by applying updates on your X250, from its "Fix-released" state, it looks like it's already landed in Ubuntu kernel (sudo apt-get update; sudo apt-get dist-upgrade).
ok, I did this, and it was successful.
I'll reboot and see if this fixed it.
>
> I think you will be able to open a well-written bug report with these information.
> (Just open a bug with "Bug description", "Step to reproduce", "Expected behaviour", "Actual behaviour" and extra debugging information like your evtest result or something else mentioned in DebuggingTouchpadDetection wiki page in the content)
I submitted a bug report, as you suggested. You will find it at:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1506817
>
> The kernel tweaking stuff is the last step when the update does not solve your problem, and you still want to fix it by yourself.
> What you need to do is to fetch the patch mentioned in that bug, and build a kernel base on that.
I sure hope it doesn't come to this. I'm not much of a C programmer.
>
> Good luck.

Following the sysem upgrade (see above), I rebooted the X250, and:
after 5 mins of testing, I dont see the bug. I need to give it a more
rigorous test.
I'll report back later what the status is, after much more testing.
I dont think its about luck, its about digging down deep and fixing the
code.

Thanks for all your help! I believe I'm on the right track here, thanks
to you.

Jont
>

Revision history for this message
Jont Allen (jontalle) said :
#9

Dear Po-Hsu,
After the suggested upgrade to 15.04, the mouse-click button issue is
still not resolved.
I conclude that the problem has not yet been solved, or at least if it
has, its not propagated to the latest release.

Thus bug #272142 is still an open issue
And it renders my new X250 Lenovo unuseable.
I would say that suggests a high priority. I paid more than $1K for a
piece of "junk,"
becasue of a malfunctioning mouse button driver.
The machine with Ubuntu 15.04+ is not useable.

I doubt I can return it, given that its a linux driver issue.

What to do? Is this fixable?
Is the source code for the synaptics driver open-source?
Or is it propitiatory and we patch into it?

Jont

On 10/16/2015 04:20 AM, Jont Allen wrote:
> Dear Po-Hsu,
>
> Because the X250 is not useable, due to the bug, I am still using my
> X220i for daily work.
> The X220i works fine, but the X250 does not. This makes it difficult for
> me to work on the X250
> when posting the bug report, I must switch back and forth between the
> two computers. It gets a bit
> confusing.
>
> I will post a new bug as you suggested, from the X250, with the proper
> driver information,
> but I cannot do that until I have a clear indication of the exact nature
> of the bug.
>
> Preliminary Analysis:
> X250
> Based on some preliminary investigations, I established yesterday that
> the X250 TPP/2 is using
> Phys=synaptics-pt/serio0/input0.
> I established this with the command
> cat proc/bus/input/devices
> Here I see that the "TPPS/2 IBM TrackPoint" is connected to "mouse1 and
> event15"
>
> X220i
> On my working X220i TPPS is connected to
> "mouse0 event 4" and Phys=isa0060/serio1/input0
>
> X250 analysis:
> Next I used the command on the X250
> evtest /dev/input/event15 | grep EV_KEY
>
> Then I can see the bug show up as follows:
> I click on button 1 (left) over and over. When I push the button down,
> I see it register as 1,
> and when I let go of the key, it registers as a 0.
> The bug is that every now and then (once every 20 clicks), when I let go
> of the mouse button
> (BIN_LEFT), it does not go back to state 0 (it stays in state 1).
>
> X220 analysis:
> On the working X220 with the same command I see
> # evtest /dev/input/event4 | grep EV_KEY
> Event type 1 (EV_KEY)
> Event: time 1444986134.240133, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
> Event: time 1444986134.388961, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
> Event: time 1444986134.883831, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
> Event: time 1444986135.022029, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
>
> In the X220 (working) case there are no button-click (BTN_LEFT) errors.
>
> SUMMARY:
> Thus I believe I have isolated the exact problem to the BTN_LEFT and to
> the driver
> Phys=synaptics-pt/serio0/input0.
>
> Is there anything I have left off, that would help to diagnose this problem?
>
> Jont
>
>
> more below:
>
>
> On 10/15/2015 10:32 PM, Po-Hsu Lin wrote:
>> Question #272142 on Ubuntu-Certification changed:
>> https://answers.launchpad.net/ubuntu-certification/+question/272142
>>
>> Po-Hsu Lin posted a new comment:
>> Hello Jont,
>> for the bug that you linked here, it belongs to an extra package called timekpr, I don't think it related unless you do have this package installed.
> I am not totally following this. I dont know anything about "timekpr"
> This seems unrelated, as you suggest.
>> And for the touchpad issue, from your xinput log, I think it's not detected at all.
>> (The TPPS/2 IBM TrackPoint looks like the small red dot track point)
> Perhaps I was reporting what the x220i gives, rather than the X250. Very
> confusing, and hopefully
> clarified in my above detailed report.
>> I found a bug for clickpads on X250, but it's already been fixed:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1430846
>> So I think a new bug report could be helpful.
> From reading this bug, it looks related to mine. Are you saying that I
> need to get a new
> kernel or kernel patch, to verify that its fixed? This may start to push
> my ability, but I'll
> do what ever is necessary, to fix the problem.
>> If you're interested in the driver stuff, please follow the wiki page here to fetch the kernel:
>> https://wiki.ubuntu.com/Kernel/Dev/KernelGitGuide
> Can you please hold my had a bit further here?
> 1) how do I verify that I'm following a path to the solution, that will
> fix the problem?
> 2) What exactly will I need to do, to fix it, assuming that the kernel
> patch solves the problem?
>
> At this point, I'm not sure what to do next. I dont want to randomly try
> things, and really screw
> up the X250. I have a lot of time invested in setting this system up,
> and I dont want to start over.
>
> Jont

Revision history for this message
Po-Hsu Lin (cypressyew) said :
#10

Hello,
I think we can ignore the "Clickpad movement" verificaton (move your cursor with the clickpad). I mixed up the xinput result from your X220i.

From the bug attachment, your X250 xinput result is:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=13 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]

So there is no doubt that there could be a bug to the driver.
(And I think you're referring to bug 1506817 in your comment #9)

I am unable to answer your questions in comment #9, but I will target this bug to the kernel, you might be asked to do some upstream testing, that's what we can do now.

Cheers.

Revision history for this message
Jont Allen (jontalle) said :
#11

see comment below

On 10/18/2015 09:27 PM, Po-Hsu Lin wrote:
> Your question #272142 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/272142
>
> Po-Hsu Lin posted a new comment:
> Hello,
> I think we can ignore the "Clickpad movement" verificaton (move your cursor with the clickpad). I mixed up the xinput result from your X220i.
>
> >From the bug attachment, your X250 xinput result is:
> ⎡ Virtual core pointer id=2 [master pointer (3)]
> ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
> ⎜ ↳ TPPS/2 IBM TrackPoint id=13 [slave pointer (2)]
> ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]
>
> So there is no doubt that there could be a bug to the driver.
> (And I think you're referring to bug 1506817 in your comment #9)
>
> I am unable to answer your questions in comment #9, but I will target
> this bug to the kernel, you might be asked to do some upstream testing,
> that's what we can do now.
If there is any further questions to me, or any test you would like me
to confirm. just ask.
I have a brand new Lenovo X250 that is totally unusable, sitting on my
dining room table, due to this bug.
Please find this bug and squash it.

Thanks for all your help.

J Allen
>
> Cheers.
>

Revision history for this message
Jont Allen (jontalle) said :
#12

Dear Chris,
I did what you requested, to upgrade to 4.6.0-rc2
Following that, the left-mouse button remained, but worse it also
returned when I boot 4.5-rc3,
which had been working up to this point, as I described in y report # 21.

Another development: I cannot login to bugs.launchpad.net. When I try to
login, it hangs.

I have no idea why.

I hope this email gets to you, and is posted.

j

On 04/10/2016 11:32 AM, Christopher M. Penalver wrote:
> Bug #1506817 status changed in linux in Ubuntu:
>
> Confirmed => Incomplete
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506817
> "left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)"
>
> This bug is linked to #272142.
> Feedback on the Lenovo ThinkPad X250 - Wolverine2
> https://answers.launchpad.net/ubuntu-certification/+question/272142
>

Revision history for this message
Jont Allen (jontalle) said :
#13

I have a question, that make me worry:
I installed the amd64 kernel.
My CPU is an intel 64bit cpu.
On the ubuntu website, it suggests the 32 bit kernel i386.deb for intel
computers, and the amd64 only for AMD computers.

My CPU is Intel not AMD.

Have I been using the wrong kernel??

Jont

On 04/10/2016 11:32 AM, Christopher M. Penalver wrote:
> Bug #1506817 status changed in linux in Ubuntu:
>
> Confirmed => Incomplete
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506817
> "left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)"
>
> This bug is linked to #272142.
> Feedback on the Lenovo ThinkPad X250 - Wolverine2
> https://answers.launchpad.net/ubuntu-certification/+question/272142
>

Revision history for this message
Po-Hsu Lin (cypressyew) said :
#14

Hello Allen,
the amd64 here is for 64bit architecture, regardless it's an AMD or an Intel CPU, don't worry about it.

x86-64 (also known as x64, x86_64 and AMD64) is the 64-bit version of the x86 instruction set.
(https://en.wikipedia.org/wiki/X86-64)

Revision history for this message
Jont Allen (jontalle) said :
#15

Dear Po-Hsu
Thank you for this information. I will continue to use the AMD64 kernel

Do you know how I can get access to my ubuntu login?
As of last night I now cannot login. I go to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506817
and click the login icon, and the system hangs up, and I'm not given a
login prompt.

I did what Chris requested re trying the very latest kernel, and that
make no difference.

At this point the X250 seems to be in a state where the synaptics driver
is not working, and the left mouse button sticks randomly.
Before yesterday, I was able to turn it off using the BIOS. Now that
option is gone.

As a result, it looks like the X250 goes in the "trash." It is not
useable with this trackpad turned on, as then the left mouse button
sticks on, randomly.

Very serious problem.

And now I cant even login to launchpad.net for some unknown reason.

Jont
On 04/10/2016 08:32 PM, Po-Hsu Lin wrote:
> Question #272142 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/272142
>
> Po-Hsu Lin posted a new comment:
> Hello Allen,
> the amd64 here is for 64bit architecture, regardless it's an AMD or an Intel CPU, don't worry about it.
>
> x86-64 (also known as x64, x86_64 and AMD64) is the 64-bit version of the x86 instruction set.
> (https://en.wikipedia.org/wiki/X86-64)
>

Revision history for this message
Po-Hsu Lin (cypressyew) said :
#16

Hello,
for the login issue, I think it's relate to some Internet connection issue. (Unless the "system hangs up"[1] refer to a system freeze.) And it can be caused by many reasons, like the DNS server problem, network node connection issue and etc. You can try to access launchpad.net with the IP address: 91.189.95.83 or try use another network to login.

For requests from Chris, I think he's not monitoring this place, it will be better to reply on the bug report directly.

For information about where to get tech support, please check this article: https://answers.launchpad.net/ubuntu-certification/+faq/1945

[1] "click the login icon, and the system hangs up, and I'm not given a login prompt." quoted from comment 15

Revision history for this message
Jont Allen (jontalle) said :
#17

Dear Po-Hsu
Thank you, this is helpful. I'll work on the login issue, as you
suggest. This is very helpful information. I can try the IP address
directly.
I'll get back to you on this.

Obviously I cannot pursue the issue without access to launchpad. Chris
will assume I simply gave up.

I have switched my daily computer to a Thinkpad (Lenovo) X201, which is
a few years old, but sill working just fine.
This computer may have been the first to hav a touchpad, and the BIOS
allows you to turn it off, just like the X250.
So far, after a few hours of use, there is no indication of the left
mouse button sticking.

I'll work on the login to launchpad.net issue further.

Jont

On 04/12/2016 05:08 AM, Po-Hsu Lin wrote:
> Your question #272142 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/272142
>
> Po-Hsu Lin posted a new comment:
> Hello,
> for the login issue, I think it's relate to some Internet connection issue. (Unless the "system hangs up"[1] refer to a system freeze.) And it can be caused by many reasons, like the DNS server problem, network node connection issue and etc. You can try to access launchpad.net with the IP address: 91.189.95.83 or try use another network to login.
>
> For requests from Chris, I think he's not monitoring this place, it will
> be better to reply on the bug report directly.
>
> For information about where to get tech support, please check this
> article: https://answers.launchpad.net/ubuntu-certification/+faq/1945
>
> [1] "click the login icon, and the system hangs up, and I'm not given a
> login prompt." quoted from comment 15
>

Revision history for this message
Jont Allen (jontalle) said :
#18

Not sure why, but now launchpad.net is working. I posted my comments.
Thank you VERY much for your bridge of help.
Jont

On 04/12/2016 05:08 AM, Po-Hsu Lin wrote:
> Your question #272142 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/272142
>
> Po-Hsu Lin posted a new comment:
> Hello,
> for the login issue, I think it's relate to some Internet connection issue. (Unless the "system hangs up"[1] refer to a system freeze.) And it can be caused by many reasons, like the DNS server problem, network node connection issue and etc. You can try to access launchpad.net with the IP address: 91.189.95.83 or try use another network to login.
>
> For requests from Chris, I think he's not monitoring this place, it will
> be better to reply on the bug report directly.
>
> For information about where to get tech support, please check this
> article: https://answers.launchpad.net/ubuntu-certification/+faq/1945
>
> [1] "click the login icon, and the system hangs up, and I'm not given a
> login prompt." quoted from comment 15
>

Revision history for this message
Jont Allen (jontalle) said :
#19

I am now able to login to launchpad.net, so that issue is resolved. Continue to read this thread if you want more information about the left-mouse-button-sticking issue on the X250, which is still unresolved, even with Ubuntu 16.04 beta2.

Continued at:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1506817

Revision history for this message
Jont Allen (jontalle) said :
#20

Hi Po-Hsu,

Please, ck out the present status of this bug.

The issue has not been resolve, and the X250 thinkpad is not working
with linux.

Please read the latest summary, comment #42

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506817

Here is a quote from my last comment:

"Chris, I appreciate your attention to this, but I think we need to get
to a new level re this problem. If the community wishes to continue to
use X series thinkpads (I'm sure they do), then this problem needs a
resolution.

What will Lenovo come up with next? Is the beginning of the end of
Thinkpads and Linux?

I have more than 10 of these X-series laptops lying around my office.
I've been using X hardware for many years. I see this as the end of the
line, all due to a stupid mouse driver bug."

In summary:

I appreciate your input as well, but this has been going on for a long
time, with no resolution.

The Lenovo X-series thinkpad is at stake here. At least that is my view.

Jont

On 04/12/2016 04:57 AM, Po-Hsu Lin wrote:
> Bug #1506817 status changed in linux in Ubuntu:
>
> Incomplete => Confirmed
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506817
> "left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)"
>
> This bug is linked to #272142.
> Feedback on the Lenovo ThinkPad X250 - Wolverine2
> https://answers.launchpad.net/ubuntu-certification/+question/272142
>

Can you help with this problem?

Provide an answer of your own, or ask Jont Allen for more information if necessary.

To post a message you must log in.