I recently got around to installing Trusty Beta 2 on my Fujitsu LifeBook
alongside Windows 7 after a reimage made it Windows-only again. This bug
still exists.
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
BvL | QORTEC, thank you for your comment. So your hardware and problem may be
tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into a Ubuntu repository kernel (not a
mainline one) via:
ubuntu-bug linux
For more on this, please read
Form what I understand I have a similar issue, I have a Fujitsu T4215
Tablet PC/Laptop, and the stylus wouldn't work after resuming form a
suspended state.
The issue:
- the wacom input gets removed on system suspend or resume (tested by running
“xinput –list” before and after).
The solution:
I have not heard a response back yet. Unfortunately, today is the first
day of my new semester, and I need to get my laptop re-imaged with
Windows at my school's IT help desk so I can use the necessary software
for my courses. I will likely go back to dual-booting with Ubuntu 12.04
LTS unless any
Okay, the email is sent. We'll see what the response is. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251441
Title:
[Fujitsu LIFEBOOK T900] Stylus input stops working after resuming
from
Okay, here is the new email draft with the needed info appended. To whom
should I send it? Thanks!
** Attachment added: Bug1251441UpstreamEmail.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251441/+attachment/3942105/+files/Bug1251441UpstreamEmail.txt
--
You received this bug
Christopher Kyle Horton, I would send it to both linux-input and linux-
pm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251441
Title:
[Fujitsu LIFEBOOK T900] Stylus input stops working after
@Christopher M. Penalver, the instructions note that for regressions, I
should have the commit of when the regression occurred available in my
upstream bug report. Since I could not find the exact commit in my
bisection, how should I handle this? Thanks.
--
You received this bug notification
Christopher Kyle Horton, thank you for your comment. It would be best to
make it clear from what two kernel versions, or commit range if more
specific, you at least bisected it down to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Christopher M. Penalver: Okay, I have a draft of the email I am going
to send attached.
Barring anything I may have missed, who should I send this to? The
Ubuntu Wiki says to refer to the MAINTAINERS list (
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS
), but
Christopher Kyle Horton, the only thing missing is your
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251441/+attachment/3920506/+files/wakeup
and a snip of your dmesg from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251441/+attachment/3920507/+files/dmesg.txt
.
--
You received
Okay, this is interesting. I found that I can confirm this bug on Saucy
using the 3.8.13.12 mainline kernel version, which according to
http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html is
equivalent to the 3.8.0-34.49 kernel I used in my test of updated Raring
(and there was no
Christopher Kyle Horton, thank you for your comment. One thing to keep
in mind that the Ubuntu kernel is based off of the mainline kernel, but
not bit-for-bit the same. So, I would check a few earlier releases of
mainline kernel 3.8.13.12 to see if the regression in the mainline was
a little bit
Okay, I have tested several more versions back, and I can confirm the
bug is present all the way back to at least the 3.8.9-Raring version
(3.8.8-Raring is where I begin to run into problems like those described
in Comment #20, and the stylus stops working altogether).
--
You received this bug
Christopher Kyle Horton, thank you for working on the bisect. Given the
extenuating circumstance surrounding your attempts to bisect, let us put
this on hold for now. Hence, the issue you are reporting is an upstream
one. Could you please report this problem through the appropriate
channel by
@Christopher M. Penalver: I went to bisect the Ubuntu kernel versions
like I mentioned in the last comment, but the problem is present all the
way back in the 3.9.0-0.1 kernel (the earliest published version for
Saucy AFAICT), and attempting to run any earlier kernels from Raring
results in a
Christopher Kyle Horton, thank you for your comments. It would be best
to switch over to bisecting the mainline kernel following
https://wiki.ubuntu.com/Kernel/KernelBisection#Map_Ubuntu_kernel_to_Mainline_kernel_for_mainline_bisection
to see if it let's you continue your bisection.
--
You
Sorry for the delay since the last update. My family's Christmas
excitement had to die down first. :P
I've completed the Bisecting Ubuntu releases section of the linked
wiki page from comment #16, and found that the bug is reproducible in a
fresh install of 13.10 (both before and after updates),
Okay, I'm done with my studies for this semester now. I'll begin the
bisection once all of my data has been backed up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251441
Title:
[Fujitsu
Thank you for the wiki link.
Since this is a school laptop which is dual-booted with a Windows 7
image supplied by my school, and we're entering final exams in a couple
weeks, I will hold off on doing the first step (Bisecting Ubuntu
releases) until after these exams are done and I'm on winter
Christopher Kyle Horton, could you please provide 3 and 4 of
https://wiki.ubuntu.com/DebuggingKernelSuspend#Debugging_information_to_provide_in_your_bug_report
?
** Tags removed: kernel-bug-exists-upstream-v3.11.8
** Tags added: kernel-bug-exists-upstream-v3.13-rc1
** Changed in: linux (Ubuntu)
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251441/+attachment/3920507/+files/dmesg.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Christopher M. Penlaver, here is the requested output.
** Attachment added: wakeup
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251441/+attachment/3920506/+files/wakeup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Christopher Kyle Horton, the next step is to fully commit bisect from
12.04 to 13.10 in order to identify the offending commit. Could you
please do this following https://wiki.ubuntu.com/Kernel/KernelBisection
?
** Tags removed: needs-suspend-logs
** Changed in: linux (Ubuntu)
Status:
Magnus's workaround works for me.
Christopher P., so you are saying that the bug affecting Christopher H.
is different from the one affecting me and Magnus? Why is that clear?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Christopher M. Penalver , I am running the 3.13 mainline kernel now:
chorton@chorton-LIFEBOOK-T900:~$ uname -a
Linux chorton-LIFEBOOK-T900 3.13.0-031300rc1-generic #201311221535 SMP Fri Nov
22 20:36:51 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
I still have the same bug as before.
** Changed in:
Also, the workaround mentioned in comment #8 does not seem to work in my
case. I can use grep to find similar lines in my /var/log/syslog,
however.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
27 matches
Mail list logo
