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 Kernel
Packages, which is subscribed to linux in
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 f
Okay, the email is sent. We'll see what the response is. :)
--
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/1251441
Title:
[Fujitsu LIFEBOOK T900] Stylus input stops working after resumi
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 n
@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 I'm
@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 beca
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 no
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 bug
@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 stret
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1251441
Title:
[Fuji
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 b
** 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 Kernel
Packages, 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 Kernel
Packages, which is subscribed to linux
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
@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:
Okay, I installed the mainline kernel and can confirm I'm running it
after a reboot:
chorton@chorton-LIFEBOOK-T900:~$ uname -a
Linux chorton-LIFEBOOK-T900 3.11.8-031108-generic #201311122252 SMP Wed Nov 13
03:53:29 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Unfortunately, after suspending and resum
Thanks Joseph. I'll look into it.
Since I reported this, a friend suggested that I try logging out and back in to
see if that changes anything. That does seem to make the stylus start working
again when I do that, in case that changes anything. I'll add this workaround
to the bug summary.
** De
Public bug reported:
I'm filing this bug here as per a suggestion on Ask Ubuntu:
http://askubuntu.com/questions/377047/which-package-should-i-file-a-bug-
against-for-pen-input
I have a Fujitsu LifeBook T900 which accepts touchscreen input via a
stylus which comes with the machine. It works fine u
19 matches
Mail list logo
