@jsalisbury
Current trusty 3.13.0-34 is affected.
I then tested latest 3.13.0-35 from trusty proposed repository and the bug is
still there.
Even 3.13.0-35.62 from trusty git repo suffers from the same bug.
Unsurprisingly, mainline 3.13.11.6 is not affected by this bug at all.
--
You received
I took some more time to research and I wrote a proper patch this time.
It's just six lines of code.
What this patch does is basically restore hid_get_raw_report field in struct
hid_device.
All the lines that are added by this patch were previously removed by this
commit:
commit
@mdeguzis
Thank you and yes: you read that wrong :)
A patch like this is meant to be applied to current ubuntu 14.04 kernel (3.13).
When I wrote using the new kernel i meant using the new kernel image that
you just built yourself with the commands above.
Writing this patch is all I can do for
@em4n3m
Awesome, thank you for confirming this.
@straximus
My bad: I should have mentioned that, to compile your own kernel, you need some
packages installed first and maybe some other requirements to meet.
I can't see the actual compilation error in that output but, if it's the first
time you
I confirm that kernel 3.13.0-36 from -proposed also solves the issues
regarding Sixaxis/Dualshock3 controller described in duplicate bug
#1326725.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353021
@jsalisbury
I can confirm that the controller is indeed working with that kernel.
It seems that the fix is already there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326725
Title:
PS3 Sixaxis
...or much more likely that the bug was never there in the first
place... :(
Looking into /usr/src/linux-headers-3.13.11-03131105/include/linux/hid.h
shows that the changes that caused the regression that I pointed out in
comment #55 might not have been applied to this kernel at all.
To be more
I did a manual bisect of the ubuntu trusty kernel tree and the last
good (controller working) commit is:
commit 73ffcac5867519fa4b6a54e734ded0fed5b403cc
Author: Jiri Kosina
HID: hidraw: make comment more accurate and nicer
The first sure bad (controller not working) commit I found is:
Thanks for the directions!
I just sent the patch to the ubuntu kernel mailing list.
I hope git send-email formatted it right :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326725
Title:
PS3
@jsalisbury
Not only I forgot to subscribe to the mailing list but I even forgot to ask if
it's required in order to send emails to it.
Wanted to ask because I didn't know if that was implied. Must be because of it
I wonder?
Anyway I tried git send-email multiple times before sending it and it
I sent it again and now it got through without issues.
Thank you for your patience.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326725
Title:
PS3 Sixaxis controller/joystick usb stopped working,
@james-hughes
Thank you for pointing out mainline commit 975a68327.
I tested it for a while and I can confirm that applying that patch solves all
of trusty's Sixaxis/Dualshock3 issues.
If it solves Oculus Rift's issues too I hope that the mainline patch is
accepted.
--
You received this bug
*** This bug is a duplicate of bug 1353021 ***
https://bugs.launchpad.net/bugs/1353021
@laurence
Nope. Everything is working fine for me on 3.13.0-45.74
With the controller connected via USB, did you try pressing the central PS
button before testing it with a program like jstest-gtk?
Does
I found a more viable workaround based on comment #18 by Anthony that
still lets you use your headphone jack provided you have an unused front
microphone jack.
Install alsa-tools-gui
Run hdajackretask
Override "Green Headphone, Front side" to "Not connected"
Override "Pink Mic, Front side" to
The latest pulseaudio update fixed this for me on 16.04.
After the update, just to see if something changed, I reverted the
changes made by my workaround in comment #20, rebooted, tested it for a
day and I didn't encounter this bug ever since.
My current pulseaudio version is 1:8.0-0ubuntu3.3
@vanvugt
I tested 17.04 in a live USB environment all day. This bug never showed up.
In 16.04 LTS this annoying bug pops up at least once in a couple of minutes so
I assume it's fixed in Zesty at least.
Thanks for looking into it.
--
You received this bug notification because you are a member
So... I previously reported that this bug got fixed for me in 16.04. I
was wrong.
The bug is still present and now only shows up once or twice a day
causing a small skip when reproducing audio. Headphones weren't plugged
in. Previously it popped up at least once in a couple of minutes so I
I just found out yesterday that, if you enable auto-login, gdm never
hangs like this anymore.
This is kinda bad for security and debugging/testing but hopefully it
can still be of use to someone until this bug gets fixed.
Also this is not related to bad gnome extensions as, on my machine, gdm
A whole year later I'm still affected by this bug with Kubuntu 18.04.
No volume notification shows up in kde but audio playback still skips about
once or twice in in a couple of minutes like headphones just got plugged in and
then immediately taken out.
No headphones were plugged in at any time
Can confirm that the newest patches from the Debian package fix this
issue on my 20.04 machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857810
Title:
osspd no longer works: ERR: failed to
20 matches
Mail list logo
